Jetpack Compose is Swift (UI).
summary
Argues that Jetpack Compose maps directly to SwiftUI and that knowing Android gets you most of iOS: Jetpack Compose ≈ SwiftUI. Compares Kotlin and Swift (coroutines/StateFlow vs structured concurrency/Combine), points out key difference that everything in Swift is a value type while Kotlin data classes live on the heap, and contrasts Room vs Swift Data and Kotlin Multiplatform adoption. Demos and product stories include an AI F1 simulator, Hummingbird Fuel, drunk-watch safety, Lego self-driving-phone car, and sensor ML pipelines; claims these run and drive design/architecture choices.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:49Why Android devs care about iOS
- 3:16Kotlin Multiplatform limits
- 5:00Direct platform access
- 8:28Kotlin vs Swift features
- 10:34Value types comparison
- 14:11Higher-order functions
- 16:36Null safety differences
- 18:45Error handling
- 20:51Structured concurrency
- 23:46Flows vs Combine
- 26:36Swift concurrency evolution
- 29:27Actors and thread safety
- 31:15Room vs SwiftData
- 32:19Compose vs SwiftUI patterns
- 33:42Layout and rendering
- 34:48State management
- 35:30Material Design versus Apple Human Interface Guidelines
- 38:43Android vs iOS architecture
- 40:12Conclusion
related talks
40mSwiftUI vs Jetpack Compose by an Android Engineer
45mCompose vs SwiftUI: Spot 10 Differences
40mDevelopers Without Borders: Jetpack Compose for Android and iOS
32mJetpack Compose — Next Gen Kotlin UI Toolkit for Android
25mWhat can we learn from Jetpack Compose?
01h 12mJetpack Compose over inheritance
33mJetpack Compose: A New Hope
01h 00mJetpack Compose - Next Gen Kotlin UI Toolkit for Android