How We Rebuilt Instagram Photo Sharing: Compose Interoperability With Large Legacy Systems
summary
Instagram rebuilds its photo‑sharing UI in Compose while keeping legacy Views via Android View wrappers and render controllers; a staged rollout (experimentation → closed → open) validates tradeoffs with small bets like the crop toggle and a migrated bottom bar, showing neutral engagement metrics and 70% developer preference for Compose. Performance quirks include a first‑compose millisecond hit and coroutine startup cost ~1ms, so state holders, DisposableEffect keys, and selective direct view rendering are used to make the hybrid system work at scale.
AI-written summary · about
chapters (8)
- 0:00Compose rebuild at Instagram
- 3:12Photo sharing evolution
- 8:32Compose adoption phases
- 13:12Interoperability with View
- 17:43Recomposition in hybrid apps
- 23:39State sync in interop
- 29:57Wrapping legacy components
- 32:13Key takeaways
related talks
01h 08mAdopting Jetpack Compose @ Scale
18mCompose Adoption at Pinterest: A Postmortem
38mViews, Compose, Multiplatform - Oh My!
36mCoupling Compose- Interoperability in a Legacy Codebase
33mMigrating to Jetpack Compose - an interop love story
44mComposables in Views: Interoperability and the Clash of Lifecycles
41mFrom ImageView to Compose: Architecting Image Loading
01h 12mJetpack Compose over inheritance