What problem does it solve? Writing one Compose codebase that runs correctly on Android, iOS, Desktop, and Web requires navigating expect/actual declarations, platform interop, density differences, and target-specific quirks that are easy to get wrong. ## Core Features & Use Cases - expect/actual Patterns: Declare shared contracts in commonMain and implement platform-specific composables and functions per target. - Native Interop Recipes: Embed SwiftUI/UIKit views via UIKitView, host Compose inside SwiftUI with UIViewControllerRepresentable, and bridge Android Views, Swing, and Wasm JS. - Platform Quirk Catalog: Reference guides covering safe-area insets, keyboard handling, gesture conflicts, Skia/Skiko rendering differences, and build packaging per target. - Use Case: You are building a KMP app and need a native MapKit map inside a Compose screen on iOS while keeping an Android fallback; the interop reference provides the full Swift bridge, cinterop configuration, and actual implementations. ## Quick Start Ask the assistant to apply the compose-multiplatform skill to set up an expect/actual composable that renders a native map on iOS and a fallback on Android.