We have a Chat app (Android) developed based on firebase (Real time database) cloud. Currently chat history was coming only when we are in online, when we don't have internet it was showing blank. For getting the chat history in offline did we have develop any additional code in android app or simply we have to enable the offline mode option.
But still people are not preferring firebase for production apps and enterprise level apps. I don't understand why people are asking me to go with AWS or Azure for production ready apps or enterprise level apps but not firebase. I think it's a great topic you should have some articles.
I've used Firebase one 2 enterprise apps (1 was governmental) and it performed really well. One of the mistakes I can say our Lead did in one of the apps was to make us use Firestore; things got expensive real quick. However, Firebase worked really well in all ends, including Cloud Firestore. Tools we used: Firestore, Realtime DB, Cloud Functions, Auth, Remote Config. It worked well and didn't fail in anything. Comparing how cheaper it was to GCP, I'd say it's enterprise-ready; most of the tools are.
@@EdwardQuixote Man I already have a dating app with over 33k plus users. I'm not talking about performance or anything. I'm talking about still many people are not recommending.
We actually just today had some discussion about this, and the user experience in our Wavers app. We used Flight mode to be offline, and for the UI things would stay open until some reply comes from Cloud Firestore. This means disabled buttons and something looking like slow response times, which is essentially correct, but might yield a poor user experience. I'm still undecided, maybe you can help. Currently we wait for a response, this is to be able to show the user an error or just something not real time. However you advocate just letting it seem like everything went well. How do you tell the user, possibly at a way later time, that their action didn't work?
I'm late but, You can change the firestore calls to be always made to either cache or online. So I'd switch it to online only and then catch the exception. That way you can let the user know.
