compose-multiplatform-patterns

Use a single immutable data class for screen state exposed as StateFlow from the ViewModel, and collect it in Compose with collectAsStateWithLifecycle. Update state via MutableStateFlow.update with copy operations rather than mutableStateOf.

Define routes as @Serializable objects or data classes and register them with composable<Route> in a NavHost using Navigation 2.8+. Retrieve arguments with backStackEntry.toRoute<Route>() and navigate by passing route instances to navController.navigate.

Yes, Compose Multiplatform supports shared UI across Android, iOS, Desktop, and Web from commonMain. Platform-specific behavior like status bar handling is implemented with expect/actual composable declarations per source set.

Excessive recomposition usually comes from unstable parameter types, new object instances created in composable parameters, or reading state eagerly. Mark classes @Immutable or @Stable, wrap derived values in derivedStateOf, and hoist computations into remember or the ViewModel.

No, passing NavController deep into composables couples them to navigation and harms previewability and testing. Pass lambda callbacks or a single event sink function instead, and keep navigation calls at the NavHost or screen entry level.