How We Accidentally Halved the Release Build Time
summary
A mobile-banking Android team describes how they accidentally halved their release build time by addressing code and resource shrinking. They cover R8 profiling and analysis plus profiling individual Gradle tasks involved in preparing the release APK. The talk targets practicing Android engineers and includes low-level, hands-on techniques.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:10Project context
- 6:22Minification problem
- 11:34R8 configuration analysis
- 18:16Fixing rule issues
- 20:02Memory consumption problem
- 22:34Resource merging research
- 27:14Resource optimization
- 31:44Shrinking modes
- 34:12Summary and conclusions
- 37:40Q&A
related talks
27mFaster builds on Android: from 2 minutes to 2 seconds
42mStop Building the Project and Start Working
32mFaster Feedback Cut Gradle Build and Pipeline Times in Half
47mBuild times breaking your flow? Learn how to speed them up!
38mFrom Development to Production: Tips to Optimise Android App Deployments
37mTackling Android Development at Scale
30mHow we brought down our build times. General optimization tips
41mHow Are Other Teams Doing It? Lessons in CI/CD from 3500 Android Teams