4 ms·

To be a Firebase alternative, you would expect a full-stack solution; DB, Auth, Cloud Functions, Analytics...etc. That's the main selling point of Firebase. Th

by gitgud 6y ago

To be a Firebase alternative, you would expect a full-stack solution; DB, Auth, Cloud Functions, Analytics...etc. That's the main selling point of Firebase. This just seems to be an Open-Source implementation of Firebase's "Realtime Database", which is kind of superseded by the new "Firestore", which is much more popular. However it's a smart business move, as many products are locked into the "Realtime Database", so this could provide an easy exit door to Open-Source software.

kiwicopple 6y ago
That's true. See my comments here: https://news.ycombinator.com/item?id=23320443 https://news.ycombinator.com/item?id=23320443 tldr: > We've been building furiously since January but (not surprisingly) we haven't yet reached feature parity. But we will :)
- rdslw 6y ago
  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 :)
- julianeon 6y ago
  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 6y ago
    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

by gitgud 6y ago

kiwicopple 6y ago

That's true. See my comments here: https://news.ycombinator.com/item?id=23320443 https://news.ycombinator.com/item?id=23320443 tldr: > We've been building furiously since January but (not surprisingly) we haven't yet reached feature parity. But we will :)

rdslw 6y ago
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 :)
julianeon 6y ago
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 6y ago
  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