compose-architecture

Prevent excessive recompositions in Jetpack Compose by using stable, all-val UiState models with ImmutableList, deferring state reads to Layout/Drawing via lambda-based Modifiers, and applying atomic state updates with update { }.

collectAsState causes lifecycle leaks in Compose Multiplatform because it collects state without lifecycle awareness. You must use collectAsStateWithLifecycle instead to pause collection when the app moves to the background.

The best way to structure MVVM screens in Jetpack Compose is using a Screen/Content split. The Screen layer bridges the ViewModel and navigation, while the Content composable remains stateless, previewable, and testable.

In Compose MVI architecture, you should avoid one-shot Channels or SharedFlow for events. Instead, model events as state using stable UiAction models to ensure UI updates are handled safely during recomposition.

This Compose architecture guidance applies to both Jetpack Compose and Compose Multiplatform. It specifically addresses lifecycle-aware state collection and stable UI modeling practices required for cross-platform production screens.

You should hoist state in a Compose MVVM feature to ensure the Content composable remains stateless and previewable. The Screen layer handles ViewModel scoping and state hoisting, reading collected StateFlow as low as possible in the tree.