Killed by Google VS rowy

Your response is so apropos. Anyone who has a history with Google or Android knows that Google eats its own and cannibalizes at will.

Or the other 280 products in the Google graveyard.

It seems nothing was ever said as to why it was shelved, but given google's track record. I would lean heavy to the side of them just being done with it.

Google has a reputation for killing off applications at will, and it's no suprise it would do the same for hardware.

Yeah, something similar to "Killed by Google". Maybe we need a template on Github for such sites to catalog bullshit, lord knows there's a lot of categories of bullshit we can catalog...

Oh actually they do have their source available: https://github.com/codyogden/killedbygoogle

Google kills another thing? Shocking! https://killedbygoogle.com/

I didn’t even know YouTube had stories, still add this to the Google Graveyard.

Just thought will put it out here as it seems like a pain point we also faced when trying to use Firestore console UI...trying to manage the data/find it etc was a pain :( So we built an open-source spreadsheet-like UI to manage your Firestore data as easily. Hope you find it useful :) Website: https://rowy.io/ Github: https://github.com/rowyio/rowy

Github: https://github.com/rowyio/rowy

Website: https://rowy.io

Also from the same makers, there is rowy.io however that is completely different beast in its own :)

Tables I would image when it is released, should be a great Airtable alternative. With Rowy, we are building an Airtable like experience but your actual database on Firestore. So that developers can continue to build their apps. https://github.com/rowyio/rowy

What scale have you tested the UI at? Do you have any demo / benchmarks for over 1M rows?

Reading through the infinite scrolling PR [1] it looks like scrolling isn’t virtualized (like Airtable’s) so the browser will start choking when it has too many elements in the DOM.

[1] https://github.com/rowyio/rowy/pull/29