compose-expert

To optimize Compose Multiplatform recomposition, apply state hoisting patterns, use remember and derivedStateOf for stable parameters, and control recomposition scope within shared commonMain composables to reduce unnecessary UI rebuilds.

The best way to structure state management in Kotlin Compose commonMain is by applying state hoisting patterns, utilizing produceState for asynchronous data, and ensuring platform-specific logic is isolated while sharing UI components across Android and Desktop.

To create custom ImageVector icons with Material3 theming in Compose, define your vector paths in commonMain and apply consistent Material3 styling tokens to ensure visual coherence across Android and Desktop platforms.

Compose Multiplatform supports sharing UI components between Android and Desktop, but requires careful platform sharing decisions to separate commonMain architecture from platform-specific implementations for optimal performance and native behavior.

Excessive recomposition in Compose Multiplatform components usually stems from unstable parameters, missing remember blocks, or improper derivedStateOf usage, which can be fixed by applying recomposition control techniques and state hoisting.

You can use Material3 theming for cross-platform Compose UI in commonMain to establish consistent styling, though specific platform sharing decisions may still require isolated overrides for Android and Desktop scenarios.