preserve app data during configuration changes

• using rememberSaveable or saving the instance state

But you don’t want to keep logic in or near Composables.

• taking advantage of the Android Jetpack library, ViewModel and Android app architecture guidelines.

Android app architecture

<aside> 💡 The most common architectural principles are separation of concerns and driving UI from a model.

</aside>

• UI layer: a layer that displays the app data on the screen but is independent of the data.
• Data layer: a layer that stores, retrieves, and exposes the app data.
• the domain layer, to simplify and reuse the interactions between the UI and data layers. This layer is optional.
• UI layer ← { UI elements ( render the data on screen )by Jetpack & State holders ( hold the data. expose it to UI, and handle the app logic) by VIewModel }

Navigation