Compose Migration Side Effects - What Can Go Wrong?
summary
Large apps that add Compose without preparation often split into mixed UI worlds, harder tests, and weird theming gaps. Create new feature modules for Compose instead of rewriting everything; expect to bridge navigation and testing (Espresso -> ComposeTestRule) and to fix performance when ComposeView creates a separate composition — many ComposeViews or composables-as-RecyclerView items can hurt frame times. Implement a custom design system via CompositionLocals for spacings and tokens and keep composables small and previewed.
AI-written summary · about
chapters (7)
- 0:00Compose migration risks
- 2:13Codebase fragmentation
- 6:49Views and Compose interop
- 10:06Theming challenges
- 15:48Navigation in Compose
- 17:36Compose previews best practices
- 19:26Q&A
related talks
45mMigrating a large-scale banking app to Compose
38mViews, Compose, Multiplatform - Oh My!
43mSwitching to Compose? Don’t Rush!
33mMigrating to Jetpack Compose - an interop love story
44mComposables in Views: Interoperability and the Clash of Lifecycles
36mCoupling Compose- Interoperability in a Legacy Codebase
06mFrom Views to Compose: Where can I start?
01h 08mAdopting Jetpack Compose @ Scale