Earlier quoted context omitted.
I'm curious what Firebase users do in real life. Do people realize this is a problem? I can imagine making an app like that where all mutations go through my server and reads go through Firebase. How would this interact with the offline persistence feature though? I suppose you could allow the client to do some simple mutations like editing text fields. For the mutations that must go through the server, though, perha…
The latency compensation through the sdk is optimistic writes. If you shortcut to server, you have to reimplement that so that's not a good solution for many cases. It would confuse the offline persistence too. Instead, your server should listen to the Firebase, rather than have writes go a separate path (which loses lots of useful features). I think the term now is a client-database-server architecture. it's not act…
I would be surprised to find that 90% of apps don't have this kind of requirement. Pokemon is easy because that data is static.