Compose for existing apps
summary
Jetpack Compose is in alpha and you can incrementally add it to apps using ComposeView to host Compose inside XML, AndroidView or AndroidViewBinding to embed existing Views (maps, WebView, Lottie), and lifecycle observers plus lifecycleOwner ambient to keep View lifecycles correct. viewModel() and observeAsState bridge existing architecture and LiveData; savedInstanceState + Saver preserve UI state. Testing uses createComposeRule with Espresso interop. Navigation via navHost exists only in snapshots and is work in progress. Samples: Crane, JetNews, TD.
AI-written summary · about
chapters (12)
- 0:00Introduction to Compose
- 2:15Migration strategies for Compose
- 5:07Adding Compose to Android Views
- 8:18Embedding Views in Compose
- 11:04Architecture with ViewModel
- 14:13Testing Compose and Views
- 15:39Navigation in Compose
- 17:32Using app resources in Compose
- 26:21Theming and styling in Compose
- 33:45Edge-to-edge UI with Compose
- 37:16Image loading in Compose
- 38:48Q&A
related talks
33mThe dark sides of Jetpack Compose
43mSwitching to Compose? Don’t Rush!
06mFrom Views to Compose: Where can I start?
38metpack Compose Q&A
22mModern Android Development #AskAndroid
01h 09mJetpack Compose for consistency of your apps' UI
37mAdopting Jetpack Compose Safely
48mLearning Jetpack Compose By Example