Putting a Jetpack on your legacy codebase
summary
Pinterest platform team is actively replacing a custom reflection‑based navigation called ScreenManager reflection and migrating core pieces to AndroidX Jetpack. They already convert Dagger to Hilt fully rolled out across ~100 monthly committers, hit Compose adoption blockers from feed rendering performance, and run a slow DataStore migration that they estimate taking ~six months to avoid user logouts. Migration patterns used: new‑code only, shim layers, central migrations (used for Hilt), and staged distributed rollouts.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:02Platform teams and their role
- 8:21Jetpack's origin and Google's experience
- 13:45Legacy codebase challenges at Pinterest
- 18:03Prioritizing Jetpack migrations
- 24:58Migration strategies overview
- 30:19Current status and future plans
