Going 100%* Compose Multiplatform
summary
Practical rundown for adopting Compose Multiplatform: project setup recommends JetBrains web wizard not the Android Studio plugin; Compose Multiplatform 1.6.11 is current with 1.7 alpha landing (expect API churn). Navigation is experimental with no deep links or back handler; alternatives: Voyager, Decompose, Appyx. Resources use compose-resources with three qualifiers. Image loading works via Coil and Kamel (core 3.0+ alpha). VoiceOver on iOS works on real devices. Previews are limited; Fleet enables Swift debugging. Mapbox/SwiftUI and CocoaPods native UI integrations are implemented and functional.
AI-written summary · about
chapters (19)
- 0:00Compose Multiplatform journey
- 1:34Setting up project
- 2:38Navigation limitations
- 3:43ViewModel and lifecycle
- 5:27Handling resources
- 7:32Image loading solutions
- 8:17Accessibility support
- 11:09Keyboard input challenges
- 12:52Window size classes
- 13:39IDE for Compose
- 15:29Debugging limitations
- 18:22Debugging iOS apps
- 19:23Native UI integration
- 23:20Mapbox with SwiftUI
- 27:19Native iOS styling
- 28:02State and future
- 30:09Staying updated
- 31:35Resources and libraries
- 32:19Q&A
related talks
58mMultiplatform UI: Compose outside Android
40mCompose Multiplatform: Better Shared UI for iOS and Beyond
43mCompose Multiplatform for iOS: Ready for Production Use
45mShared mobile UIs with Compose Multiplatform
42mCompose Multiplatform on iOS: On the Road to Stable
45mCompose Multiplatform on iOS
38mViews, Compose, Multiplatform - Oh My!
46mGoing Multiplatform with Your Android App