What can we learn from Jetpack Compose?
summary
A codebase migrating to Circuit and Compose shows concrete tradeoffs: both are declarative UI systems with rich previews and modifier chains, but Compose is Kotlin‑first with annotations and recomposition and fits incremental migration and open source extension, while SwiftUI is Swift‑only with property wrappers and a more polished, opaque diffing model. Examples include converting XML/fragments to composable functions, using previews as lightweight integration tests, and creating custom modifiers; adoption in large apps proves Compose integration works smoothly.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker intro
- 0:25Speaker background and journey
- 3:40Learning Jetpack Compose at Slack
- 5:23Swift UI overview and benefits
- 7:10Declarative vs imperative UI
- 10:21Jetpack Compose introduction
- 12:29Similarities between Swift UI and Compose
- 13:54Previews and development experience
- 15:58Learning curve and syntax differences
- 17:01Swift UI vs Compose syntax
- 18:25Implicit vs explicit styling
- 19:28State management approaches
- 20:11Strengths of Swift UI
- 21:37Strengths of Jetpack Compose
- 23:03Lessons from Compose and future outlook
- 24:34Q&A and closing remarks
related talks
01h 00mJetpack Compose - Next Gen Kotlin UI Toolkit for Android
01h 12mJetpack Compose over inheritance
32mJetpack Compose — Next Gen Kotlin UI Toolkit for Android
45mOn the road to Jetpack Compose
40mSwiftUI vs Jetpack Compose by an Android Engineer
35mCompose Yourself: Designing a Kotlin First UI Toolkit
37mAdopting Jetpack Compose Safely
19mJumping into Jetpack Compose way too early to see what's inside