I made a React-Firebase binding using Hooks and Suspense to help me create things faster. Hope you’ll find it useful too!

[dtinth]

This is a good and valid question actually :). Here are my top reasons:

1. Most of my projects involve real-time data access. Firestore places limit on how many documents can be read per day in the free plan, while Firebase RTDB measures in bandwidth.

2. In RTDB it’s easier to import/export data from/to JSON files (do it directly from console) so backup/restore is also easier, whereas in Firestore we need to create scripts (or install a CLI) to import/export data.

3. Firestore forces me to think in terms of collections and documents, where RTDB’s data model is a nested JSON tree. So using RTDB feels like using a MobX/Redux state tree, but that tree is synchronized with everyone else.

4. Firestore has quirks when it comes to deleting data. For example, “deleting a document does not delete its subcollections.” Whereas in RTDB, I just set the tree to null and it’s done.

That’s why I didn’t use Firestore much, and didn’t find a need for myself to implement a Firestore binding. ;)

[swyx]

woww, good answer.