From Views to Compose: Where can I start?
summary
Recommendation: adopt Compose incrementally by building new features in Compose while keeping the rest of the app, using ComposeView in fragment onCreateView for full-screen composables or embedding ComposeViews in existing layouts for partial screens, create a shared module of reusable UI components (buttons, app bars, dialogs) to avoid duplication, migrate simple screens first and then mixed screens piece‑by‑piece, preserve state by giving ComposeViews unique IDs, rely on UI tests to catch regressions, and remove fragments once all screen contents move to Navigation Compose.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:28What is Compose
- 0:49Strategy Overview
- 1:36Compose in New Features
- 2:35Reuse Components
- 3:22Incremental Migration
- 4:21Fragments
- 4:52Conclusion
related talks
38mFrom Android View to Jetpack Compose — A Guide to Migrating to Jetpack Compose
43mSwitching to Compose? Don’t Rush!
22mCompose Migration Side Effects - What Can Go Wrong?
44mComposables in Views: Interoperability and the Clash of Lifecycles
37mAdopting Jetpack Compose Safely
38mViews, Compose, Multiplatform - Oh My!
33mMigrating to Jetpack Compose - an interop love story
34mArchitectures in the Compose World