Mobile Developer Productivity Panel
summary
Large orgs report concrete wins: Android teams range from ~95 monthly contributors to 350–400 monthly (600–800 over six months) and monorepos exceed 10M LOC and 10,000 modules. Notable tactics that move metrics are publishing AARs to substitute modules to cut build and sync times by over 50%, provisioning dev pods (Kubernetes snapshots) with 40% monthly Android adoption for fast context switches, heavy IDE/Apple Silicon investment, and early AI tooling where 80% of devs report ≥20% productivity gain.
AI-written summary · about
chapters (10)
- 0:00Panel introduction
- 1:27Team structures
- 8:57Tooling stacks
- 10:20Measuring productivity
- 16:45Biggest wins
- 23:27AI in infrastructure
- 28:25Remote dev ROI
- 35:30IDE plugins
- 41:06Quality vs velocity
- 47:19Closing remarks
related talks
39mMobile Developer Productivity Panel
48mMobile Developer Productivity at Scale
37mMobile Developer Productivity Engineering
41mScaling Productivity: How we have improved our dev experience
24mMobile Development
17mBest Practises for Android Development as a Daily Business
49mMobile Developer Productivity Engineering at Europe's Largest Online Fashion Store
40mCase Study- How Android Platform @ Reddit learned to stop worrying and embrace DevX
