Views, Compose, Multiplatform - Oh My!
summary
Auto Trader moves a server‑driven UI from Views to Jetpack Compose and then Compose Multiplatform incrementally, replacing components with Compose views, using mobbing sessions, feature flags and snapshot tests to catch regressions; migration hits specific problems: focus and scrolling bugs with mixed view/compose hierarchies, layout width quirks requiring intrinsics, map touch handling, and a final big‑bang conversion of a library that takes three months not six weeks; Compose yields ~100% improvement in advert crash metrics, but CMP brings CI, XC framework and iOS freezes ~32 views headaches.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:05Migrating to Jetpack Compose
- 5:00Migration strategy and interop
- 8:12Focus and scrolling issues
- 12:25Full Jetpack Compose
- 14:51Layout and testing
- 20:09Compose Multiplatform start
- 23:42Repository and iOS integration
- 25:28Main module and platform code
- 27:53Resource handling and build
- 29:20Previews and cross-platform testing
- 32:48iOS development hurdles
- 34:14Compose migration lessons
- 36:24Compose Multiplatform value
- 37:30Recommendations and thoughts
related talks
33mMigrating to Jetpack Compose - an interop love story
33mGoing 100%* Compose Multiplatform
43mSwitching to Compose? Don’t Rush!
44mComposables in Views: Interoperability and the Clash of Lifecycles
37mAdopting Jetpack Compose Safely
22mCompose Migration Side Effects - What Can Go Wrong?
40mBuilding Multiplatform Apps with Compose
38mFrom Android View to Jetpack Compose — A Guide to Migrating to Jetpack Compose