Best practices for firestore streams #10596
Unanswered
greenc0102
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
I'm working with firebase Firestore on a flutter web and mobile application. It's great to work with but I just want to make sure I'm implementing everything correctly early in development to avoid issues down the line.
For context my application has users receiving a schedule from Firestore. This schedule is set and can be modified from an admin dashboard. The schedule is displayed on cards with data from a streambuilder. Each schedule item is stored as a document in a single collection, and linked to the user by their UID.
So is it most effective for me to do
It is important that the app updates in real-time and doesn't require the user to refresh in order to get data, but with that said I want to be as efficient as I can be with keeping reads and writes down. I'm not sure how smart Firestore is (if I used option 1 for instance, would a change in one schedule item result in additional reads from every other schedule item document)
Thanks for any help in advance. Don't need any code snippets etc, just looking for the best option
Beta Was this translation helpful? Give feedback.
All reactions