Mobile Developer Productivity Engineering
summary
Zelando runs ~70 million Android installs, a 40% app-visit growth since 2018, and centralizes app platform work into a modularization effort called project Roadster. Engineering invests in build tools like Gradle Enterprise, remote caching and cloud IDEs; CI pipelines fall from a 25‑minute average to ~20% faster after remote caching, with telemetry from 40,000 builds driving optimizations. Claim: saving one minute of developer wait time scales to roughly 400 engineering hours saved per year.
AI-written summary · about
chapters (19)
- 0:00Mobile dev productivity intro
- 1:29Zalando app ecosystem
- 3:36Why dev experience matters
- 7:35DORA metrics impact
- 9:20SPACE model
- 11:06Zalando dev productivity model
- 16:02Tech debt reduction
- 19:14Modularization strategies
- 21:28Build engineering at scale
- 23:15Build observability
- 24:19Cloud IDEs
- 26:09Sustainable customer value
- 27:37Dropbox investment buckets
- 29:24Engineering culture flow
- 31:52Automating focus
- 33:00Continuous deployment satisfaction
- 33:41Release quality assurance
- 34:23Zalando productivity initiatives
- 35:49Results and outlook
related talks
49mMobile Developer Productivity Engineering at Europe's Largest Online Fashion Store
49mMobile Developer Productivity Panel
39mMobile Developer Productivity Panel
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
36mDeveloper Productivity Engineering: What's in it for me?
48mMobile Developer Productivity at Scale
41mScaling Productivity: How we have improved our dev experience
44mDeveloper Productivity Engineering: What's in it for Java Developers?
