4 ms·
If I understand correctly currently the data is per user and not shared. If you have a todo app, the user can log in and see and modify their todos but there w
by guu 7y ago
If I understand correctly currently the data is per user and not shared.
If you have a todo app, the user can log in and see and modify their todos but there would be no way for them to share their todos.
There is no shared access to a modifiable store which I believe would be necessary for the view counter, comment, and signup use cases.
- j-berman 7y agoThis is correct for right now, but data sharing is a feature we're currently in the process of wrapping up and getting reviewed by an independent security team. So this will be possible in the near future
- guu 7y agoAre you thinking of user-to-user sharing (ex: daniel shares his list with justin) or something more global? To give an example: The indiehackers website uses firebase as its data store. It's a blog/forum, so posts and comments made by individual users can be seen by people who don't have accounts. Is this a use case you plan to support in the future? If not, the potential use cases are much narrower than firebase. Not necessarily a bad thing but I'm just trying to understand the product.
- j-berman 7y agoUser-to-user sharing (because data created using Userbase is private) Edit: technically you could do something hacky like share the database with a user who broadcasts the data somewhere. But I don't think you'd want to use Userbase if you want to store lots of data that anyone would be able to see
- j-berman 7y agoAdding on to this, Firebase isn't structured to support end-to-end encryption by default. Our client-server architecture is built and optimized for that intention. I don't think you could build a performant end-to-end encrypted application with Firebase very easily. Userbase fills that role with a super simple SDK