Putting a Jetpack on your legacy codebase
summary
Pinterest runs a single large 2012 app with ~100 monthly committers and legacy custom screen manager code that mimics fragments and blocks libraries like Jetpack Compose (rejected so far due to measurable startup/render regressions tied to revenue). Platform work shows concrete moves: full migration to Hilt, dual-writing to Jetpack DataStore with validation logs, use of contractors for Kotlin/nullability conversions, and four migration patterns (under‑the‑hood, shim, central team, self‑serve) with tradeoffs for QA, developer effort, and risk.
AI-written summary · about
chapters (9)
- 0:00Introduction and platform teams
- 4:25Experiments and tech adoption
- 7:36Jetpack Compose at Pinterest
- 13:54Google’s framework history
- 18:52Legacy code at Pinterest
- 23:32Screen manager and Jetpack
- 26:19Legacy RxJava and migrations
- 30:38Platform team strategies
- 37:26Summary and closing
