Description
Well-designed ViewModels should completely decouple Views from Model classes. In such way, by strictly adhering to the MVVM pattern, Models and Views can evolve independently and be tested with ease. Additionally, by applying the inversion of control principle and implementing ViewModels decoupled from the Android framework, it is possible to test ViewModels via unit tests. In contrast, if the binding between the MVVM components is too complex and intertwined, testing and debugging Android apps can become a cumbersome challenge.
Example
We created a simple MVVM example.
This is our current model:
We evolve this model, by adding a new feature:
Since Room cannot convert Date value, we need to write our own converter.
The @TypeConverters(DateConverter.class) has been added to the top of the Note model.
We change the version of our database from 1 to 2. And we need to write a migration.
We can now restart the app, and the database has been updated. Maybe this is a bad example, but when we create a new feature for our model. We can evolve our model and test it without creating a new view.
Check this page to view the complete repository.