Android Arch Components handle configuration changes / lifecycle

you said

> At implementation level, in our example, MVVM is accomplished by the usage of Architecture Components, which its main advantage is to handle configuration changes when the screen rotates, something that has given us many headaches as android developers (I guess you know what I’m talking about).
>
> **Disclaimer: that does not mean we have to no longer care about lifecycles, but it is way easier.**

ViewModel was created to handle the configuration / lifecycle for you.

[viewModel](https://developer.android.com/topic/libraries/architecture/viewmodel)
[viewModel Lifecycle](https://developer.android.com/reference/android/arch/lifecycle/ViewModel)