Kotlin Android application demonstrating the MVVM pattern with Android Architecture ViewModels and data binding.
Developed using Test Driven Development process for faster development cycle, simpler debugging and high test coverage.
MVVM
Android Arch ViewModel (1.1.1)
Junit (4.12)
Mockito (2.11.0)
Espresso (3.0.2)
The following docs were auto generated with the Dokka plugin
- The use of AndroidViewModel means that state persistence on config change is handled for us.
- A ViewModel must never reference a view, Lifecycle, or any class that may hold a reference to the activity context.source. This is solved by using AndroidViewModel as a base ViewModel class as it provides easy access to the application context.
