Coupling Compose- Interoperability in a Legacy Codebase
summary
Starts Compose with a low-risk Wear OS app, then ports a Peloton tablet settings/profile screen by breaking UI into atomic components, reusing existing XML styles via a ContextThemeWrapper inside AndroidView, and handling mutable state in the factory vs update callbacks (e.g., date picker ranges set in update). Results: faster frontend iteration, more QA feedback, and a Google IO shoutout; operational advice: pick modular screens, add snapshot tests and benchmarking early, lift accessibility context into the composable tree, and run internal workgroups and hackathons to build adoption.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 3:50Why adopt Compose in legacy code
- 6:18Starting with low-risk Compose projects
- 9:31Interoperability challenges and solutions
- 17:14AndroidView vs ComposeView interop
- 23:55Adding Compose to legacy screens
- 27:23Socializing Compose across teams
- 31:57Key takeaways from Compose adoption
- 35:48Q&A and acknowledgments
related talks
32mDeveloping Wear OS Apps with Jetpack Compose
34mBeyond the UI: Compose as a Foundation for Multiplatform Apps
22mModern Android Development #AskAndroid
46mMultiplatform UI with Compose
33mThe Evolution of Android UI Development. A Journey From XML to Compose. What’s next ?
35mSomething old, something new: Adding Jetpack Compose to a large open source Android app
37mSomething old, something new: Adding Jetpack Compose to a large open source Android app
18mCompose Adoption at Pinterest: A Postmortem