etpack Compose Q&A
summary
Live Q&A about Jetpack Compose that sticks to specifics: how tooling is still being built but preview is fast, migration paths that let Compose live inside existing XML via the androidView API or generated view wrappers (generate-view annotation is planned but delayed), accessibility via a semantics system modeled on Flutter, an animate API that returns animated values, saved-instance-state support, and recommendations to prefer immutable data and small reusable composables. Answers point to samples and Kotlin Slack for follow-up.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:04First impressions of Jetpack Compose
- 2:50IDE integration in Jetpack Compose
- 4:52Building Android apps with Compose
- 7:39Accessibility in Jetpack Compose
- 9:06Feedback and reusable components
- 13:00Unidirectional data flow in Compose
- 15:10Handling config changes
- 18:16Migrating legacy apps to Compose
- 24:37SwiftUI comparison and Compose evolution
- 26:43Underrated Compose features
- 28:49Minimizing recomposition
- 32:41Semantics and accessibility
- 34:46Tooling and designers' future
- 36:10Closing remarks
related talks
48mLearning Jetpack Compose By Example
45mFirst look at Jetpack Compose
55mRoundtable Discussion: Ask Googlers About Android Jetpack
01h 12mJetpack Compose over inheritance
32mJetpack Compose — Next Gen Kotlin UI Toolkit for Android
35mNext Generation Android UI with Jetpack Compose
38mFrom Android View to Jetpack Compose — A Guide to Migrating to Jetpack Compose
01h 00mJetpack Compose - Next Gen Kotlin UI Toolkit for Android