Compose Multiplatform
Specific best practices and architectural patterns when working with Compose Multiplatform.
Details
Language / Topic
KotlinCategory
framework
Rules
balanced
Compose Multiplatform
- Use `@Composable` functions for UI — keep them pure and stateless where possible. Use `remember` and `mutableStateOf()` for local state. Share business logic in `commonMain` and platform-specific code in `androidMain`/`iosMain`/`desktopMain`.
Compose Multiplatform
- Use `@Composable` functions for UI — keep them pure and stateless where possible. Use `remember` and `mutableStateOf()` for local state. Share business logic in `commonMain` and platform-specific code in `androidMain`/`iosMain`/`desktopMain`.
- Use `expect`/`actual` declarations for platform-specific implementations. Use `MutableState<T>` for observable state and `derivedStateOf` for computed values. Use `LazyColumn`/`LazyRow` for performant scrollable lists. Use `Modifier` chaining for layout and styling. Navigate with a shared navigation library (Decompose, Voyager). Use `LaunchedEffect` and `rememberCoroutineScope()` for side effects.