compose-multiplatform-patterns

Manage state in Compose Multiplatform by exposing a single immutable state object via StateFlow in a shared ViewModel, then collect it in your composable using collectAsStateWithLifecycle for predictable UI updates across platforms.

The best way to handle navigation in Compose Multiplatform is using type-safe route objects combined with dialog and bottom-sheet overlay patterns to maintain clear navigation flows across Android, iOS, Desktop, and Web.

Use expect/actual composables in KMP by declaring expected composable signatures in commonMain and providing actual implementations for platform-specific UI needs, keeping shared logic centralized while enabling native integration.

Unnecessary recompositions in Compose Multiplatform often occur due to missing stability annotations, incorrect keys in lazy lists, or improper allocation handling. Apply stability annotations, use derivedStateOf to defer reads, and avoid allocations to optimize recomposition performance.

You can build a shared cross-platform item list screen for Android and iOS using Compose Multiplatform by implementing a shared ViewModel, platform-specific status bar handling via expect/actual, and consistent Material 3 theming.

Compose Multiplatform supports Material 3 dynamic theming across Android, iOS, Desktop, and Web, enabling consistent design systems and reusable composables through slot-based APIs and proper modifier ordering.