compose-multiplatform-patterns

Topics in the source

• Compose Multiplatform Patterns
• When to Activate
• State Management
• ViewModel + Single State Object
• Collecting State in Compose
• Event Sink Pattern
• Navigation
• Type-Safe Navigation (Compose Navigation 2.8+)

Patterns for building shared UI across Android, iOS, Desktop, and Web using Compose Multiplatform and Jetpack Compose. Covers state management, navigation, theming, and performance. 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 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: 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 LaunchedE

This is an excerpt. Refer to the complete source and its current requirements.