Migrating to Jetpack Compose - an interop love story
summary
Migrating a view‑based app to Jetpack Compose works incrementally: the demo refactors a Reply sample by converting three small shared components (account item, recipient chip, search suggestion) to composables, swapping RecyclerView lists for Lazy layouts to remove adapters and view holders, and keeping existing navigation while using ComposeView with the right ViewCompositionStrategy. WindowSizeClasses plus accompanist two‑pane implement a responsive list‑detail layout, screenshot testing catches regressions, and scroll coupling uses rememberNestedScrollConnection to preserve the collapsing bottom bar—showing interop actually works.
AI-written summary · about
chapters (10)
- 0:00Introduction to migration
- 1:56Goals and migration strategy
- 4:04Preparation and planning
- 8:44Migrating small UI components
- 13:00Adding previews and hooks
- 15:26Interop with complex components
- 17:52Migrating low-risk screens
- 21:00Complex screen migration
- 28:48Large screen support
- 30:11Non-technical tips and summary
related talks
38mFrom Android View to Jetpack Compose — A Guide to Migrating to Jetpack Compose
43mSwitching to Compose? Don’t Rush!
19mUsing Jetpack libraries in Compose
37mAdopting Jetpack Compose Safely
38mViews, Compose, Multiplatform - Oh My!
44mComposables in Views: Interoperability and the Clash of Lifecycles
37mMigrating your app to compose, step 1, live coding
33mBuild adaptive apps with Jetpack Compose