Can Compose Multiplatform for iOS kill Flutter?
summary
Talk examines Compose Multiplatform for iOS, explaining its architecture and how rendering backends skia, impeller and skiko work, and how to prepare a shared UI. The presenter implements several screens from a real KMM app where the iOS side is in SwiftUI to demonstrate benefits and challenges of using Compose Multiplatform for iOS, and compares that approach to using Flutter for a shared UI on KMM.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:19Cross-platform stack choice
- 5:49Kotlin Multiplatform architecture
- 9:20Flutter architecture
- 13:39Skia graphics engine
- 17:48Impller engine
- 21:53Compose for iOS: current limits
- 24:28Compose vs Flutter
- 28:08Compose for iOS use cases
- 33:55Compose for iOS problems
- 36:03Summary and outlook
- 38:29Main question answer
- 39:19Recommendations
- 40:03Q&A
related talks
42mComposing All The Things with Kotlin Multiplatform
21mBridging, Compiling, and Rendering: How Cross-Platform Frameworks Work
49mFirst Flutter, then Fly: Build Reactive & Performant Cross-Platform Apps
22mHOW FLUTTER INTEGRATES with apple frameworks and tooling
58mBuilding cross-platform mobile apps with Flutter.io
28mHow Flutter works under the hood
33mShould We Flutter?
24mKeynote: Flutter