You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something I had to develop myself when working with Firebase is a small cache API so that users going back to previous views would not have to wait for data.
I implemented a in memory cache with a persistent on() connection in the background completely decoupled from my views. After the initial data download from a database path, this memory cache is only updated with value events so even for large datasets it works great. My users always see the updated data when returning to previous views instantly.
In any case, the Firebase SDK needs to provide a way to cache the data somehow. Maybe this would go hand in hand with the offline functionality, or not.
The text was updated successfully, but these errors were encountered:
Something I had to develop myself when working with Firebase is a small cache API so that users going back to previous views would not have to wait for data.
I implemented a in memory cache with a persistent
on()
connection in the background completely decoupled from my views. After the initial data download from a database path, this memory cache is only updated withvalue
events so even for large datasets it works great. My users always see the updated data when returning to previous views instantly.In any case, the Firebase SDK needs to provide a way to cache the data somehow. Maybe this would go hand in hand with the offline functionality, or not.
The text was updated successfully, but these errors were encountered: