Android Fireside Chat
summary
Panel lays out concrete guidance: start greenfield apps 100% Compose with a single-activity and Navigation Compose; use state hoisting and ViewModel-backed StateFlow (LiveData only for legacy Java), extract long modifier chains into extensions, and prefer property drilling over CompositionLocal for required data. Compose adds manual accessibility traversal and is testing K2 experimental support and KSP (replacing kapt); accompanist acts as an incubator for APIs like pager and modal bottom sheets while shadow/blur support remains complex and under study.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:11Panelist introductions
- 3:55Multiplatform development future
- 5:21Focus management in Compose
- 7:30Design system handover challenges
- 10:00Fuchsia and Kotlin future
- 12:28Fragments vs Compose in new apps
- 13:53State hoisting and modifiers
- 19:12Future of Compose features
- 23:25Composition locals vs property drilling
- 25:32LiveData vs State/Flow in Compose
- 27:41Box shadows and blur effects
- 30:06Navigation improvements
- 32:13Complex state management
- 35:46Accompanist library future
- 37:56Kotlin Multiplatform trends
- 40:47Compose issue tracking
- 46:48Q&A wrap-up
related talks
22mModern Android Development #AskAndroid
45mOn the road to Jetpack Compose
38metpack Compose Q&A
36mCoupling Compose- Interoperability in a Legacy Codebase
34mBeyond the UI: Compose as a Foundation for Multiplatform Apps
35mNext Generation Android UI with Jetpack Compose
43mBuilding Accessible Apps with Jetpack Compose
49mBuilding an Android UI using declarative programming in Jetpack Compose
