This is a sample movie list Android application built to demonstrate use of Clean Architecture tools. Dedicated to all Android Developers - (Kotlin, MVVM, Clean Architecture, Rx-Java, Dagger, OkHttp, Unit Testing, SOLID principles, Code Coverage)
As you implemented the clean code architecture along with MVVM,
Android architecture pattern which is based on repository classes is similar to the clean code interactors or use case classes. Because the repository implementation classes contains all the remote or local database handling, why we can't just call the repository classes in the view model instead of creating an extra layer of use cases and just calling those repository functions from use cases and putting that use cases into the view model.
If we worry about the separation of concerns then we can make separate repositories for one view model if a different data model is needed for a single UI.
A repo. instance deals with single source of data as per google recommendation so I assume that creating use cases is an extra layer. Please share your thoughts on it.