compose-multiplatform-patterns

Patterns for building shared UI across Android, iOS, Desktop, and Web using Compose Multiplatform and Jetpack Compose. Covers state management, navigation, theming, and performance. Use a single data class for screen state. Expose it as StateFlow and collect in Compose: For complex screens, use a sealed interface for events instead of multiple callback lambdas: Define routes as @Serializable objects: Use dialog() and overlay patterns instead of imperative show/hide: Design composables with slot parameters for flexibility: Modifier order matters — apply in this sequence: Mark classes as @Stable or @Immutable when all properties are stable: See skill: android-clean-architecture for module structure and layering. See skill: kotlin-coroutines-flows for coroutine and Flow patterns. - Building Compose UI (Jetpack Compose or Compose Multiplatform) - Managing UI state with ViewModels and Compose state - Implementing navigation in KMP or Android projects - Designing reusable composables and design systems - Optimizing recomposition and rendering performance - Using mutableStateOf in ViewModels when MutableStateFlow with collectAsStateWithLifecycle is safer for lifecycle - Passing NavController deep into composables — pass lambda callbacks instead - Heavy computation inside @Composable functions — move to ViewModel or remember {} - Using LaunchedEffect(Unit) as a substitute for...