compose-multiplatform-patterns

Use a single immutable data class for screen state exposed as StateFlow from the ViewModel, and collect it with collectAsStateWithLifecycle in the composable. For complex screens, route user actions through a sealed interface event sink instead of multiple callback lambdas.

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

Yes, Compose Multiplatform shares UI across Android, iOS, Desktop, and Web from commonMain. For platform-specific behavior like status bar styling, declare an expect composable in commonMain and provide actual implementations per platform source set.

Excessive recomposition usually comes from unstable parameter types, new object instances created in composable parameters, or heavy computation inside composables. Mark UI models @Immutable or @Stable, wrap derived values in remember or derivedStateOf, and move computation to the ViewModel.

No, passing NavController deep into composables is an anti-pattern that couples UI to navigation. Pass lambda callbacks like onNavigateToDetail instead, keeping composables stateless, previewable, and easy to test.