3 ms·
> Honestly I think the Firebase comparison may be throwing some people off here because this is a SQL-based system You're correct - we're building on top of Po
by kiwicopple 6y ago
> Honestly I think the Firebase comparison may be throwing some people off here because this is a SQL-based system
You're correct - we're building on top of Postgres so it's not a perfect comparison. And we're a bit early to even make it a fair claim.
I'm glad the crowd here has been so receptive. We were planning of launching in September, but it must have been picked up somewhere on the internet (thanks @habosa)
- dandare 6y agoHi, do you plan to be a full BaaS? With Authentication, email confirmations, push notification etc?
- kiwicopple 6y agoYes! We'll let the customers drive the priorities. Right now Authentication is our #1 focus
- pier25 6y agoWill you provide a Postgres instance too? If not what provider would you recommend?
- kiwicopple 6y agoYes, we already provide a Postgres instance (https://app.supabase.io https://app.supabase.io)
- hermit85 6y agoWill you provide or are looking into passwordless logins? I currently deal with a lot of support tickets with most of them being for reseting of passwords.
- kiwicopple 6y agoWe are still planning our auth system, but this passwordless logins is something that is technically simpler than third-party logins, so I imagine we will. Feel free to create a github issue if you want to track our progress on this one.
- gbourne 6y agoThis looks awesome. Realtime and easy access to Postgres. However, I'm not sure where the Firebase comparison comes in. You can't really even say it is a Realtime DB or Firestore comp since those are no-sql. You might want to take off the Firebase comp until ready otherwise it distracts from the cool offering.
- narrationbox 6y agoIf you are adding Auth the Firebase way, remember to add an UI for JWT claims. Right now Firebase does not explicitly expose the list of claims UI through the dashboard so everytime you change permissions you have to programmatically iterate through everything if you want a holistic overview.
- kiwicopple 6y agoThat's something I didn't know about. I'll save this comment for later and will have a think how we can give a better experience. Thanks for the tip!
- fwoty 6y agoJust a counter datapoint, the Firebase comparison is what got me to click on the link and check it out. I'm a huge Firestore fan... here's what would get me to try something new: - Better user permissions, ability to actually see my users and user permissions in a UI - Better ability to choose conflict resolution logic - Tied to that, ability to get "patches" from the server... right now if a change happens in my Firestore document, the server sends the entire document to the client. I'd love to be able to get a patch with just the changed data (and of course send patches to the server too, which it looks like you would support). - Join queries to save me from needing to do multiple client -> server trips. If it's SQL I'm guessing you would support this. Very interesting project! I'll be following your progress.
- LunaSea 6y agoCould you expand on what you mean by "conflict resolution"?
- fwoty 6y agoJust that if two people make changes at the same time on different clients, I don't have much control over merging those changes together with Firebase (that I know of). I think it's just a "last change wins" type system.