ui-layer

To prevent Android ViewModel state loss during configuration changes, enforce Unidirectional Data Flow by separating state holders and using lifecycle-aware state collection like collectAsStateWithLifecycle in Compose to maintain state persistence and eliminate untraceable bugs from tight coupling.

The best way to implement Unidirectional Data Flow in Android Jetpack Compose is to ensure state flows down from the ViewModel to the UI while events flow up from the UI to the ViewModel. This pattern eliminates state inconsistencies and guarantees user interactions are never lost.

To use repeatOnLifecycle for lifecycle-aware state collection in Android Views, execute your state collection flow inside the repeatOnLifecycle block. This pauses and resumes collection based on the lifecycle state, preventing unnecessary background work and memory leaks when the UI is backgrounded.

Yes, this Android UI layer architecture guidance works with both Jetpack Compose and View-based UIs. It provides specific rules for lifecycle-aware state collection using collectAsStateWithLifecycle for Compose and repeatOnLifecycle for View-based implementations to prevent leaks.

Reusable Jetpack Compose components should not depend on screen-level ViewModels because it creates tight coupling and makes components untestable. Proper state holder separation ensures reusable UI components like task chips remain independent of screen-level business logic.