This is the approach I usually follow when using firestore. Is there any better approach to implement MVVM architecture when our primary database is Firestore? My main decision was using a single repository object for any firestore related tasks. The viewmodel can then use it just like it uses any other data repository.
“Android MVVM pattern with Firebase Firestore” by Yashovardhan Dhanania https://medium.com/@yashovardhan99/android-mvvm-firestore-37c3a8d65404
08/11/2020, 6:43 AM
this seems ok for me, as the firestore would act as the repository