That's true. See my comments here: https://news.ycombinator.com/item?id=23320443...

julianeon · on May 27, 2020

I'm a consultant and I love the idea of having Postgres instead of NoSQL on the backend, coming from Amplify.

For me the MVP, before I could use it for my commercial projects, would be: DB+auth. At that point, I could switch - and probably would.

Also, kudos to you for being the diametric opposite of a 'useless' startup. Not only would I use this once I could, I'd talk it up to everyone in my space.

kiwicopple · on May 28, 2020

Thanks for your feedback. We hope to have a proper Auth system in place before our official launch in September.

We like building things that people will use. The number of features that Firebase offer is vast so it might take us some time, but we will get there and we’ll make sure we do it in a way that benefits the opensource community

rdslw · on May 27, 2020

Feature parity with Amazon Firebase?

Let me assess this, with the tip of my napkin:

1. linkedin 'firebase' + amazon (current employer) -> 695 people.

2. 10% of above = 70 FTE

3. They started (googled): They founded Firebase as a separate company in September 2011 and it launched to the public in April 2012.

1+2+3 = It's impossible you will have feature parity in next 10 years.

BUT it's possible you can achieve pareto parity, leaving off the table most complicated 20%. Good luck :)