Cache Me If You Can
summary
Explains concrete steps to cut Android build time: how Gradle’s initialization/configuration/execution phases map to AGP’s lifecycle, why use Android Components API (AGP7/8.2) to set variant-scoped inputs, and why old variant APIs deprecate (AGP9 → removed in AGP10). Recommends enabling parallel build, local/remote Build Cache, and Configuration Cache recommended in Gradle 9, avoid afterEvaluate and project access in task actions, mark tasks @Cacheable, use Provider APIs, avoid timestamps/doFirst, split interface/impl modules to limit recompiles, and add Build Scan / DevVelocity plugin for profiling.
AI-written summary · about
chapters (6)
- 0:00Gradle caching concepts
- 15:41Gradle lifecycle and AGP updates
- 22:47Gradle cache mechanisms
- 28:02Task inputs and outputs
- 34:00Multi-module project optimization
- 39:20Debugging with Build Scans
related talks
36mTop Build Performance issues in Android projects - 2023 Edition
17mBoosting your Android CI through integrating Build Cache
32m5 ways to improve your Android build productivity
40mImproving Android Build Performance
33mIMPROVING ANDROID BUILD PERFORMANCE
11mWhat’s new in Android Gradle plugin
30mImproving Android Build performance
30mHow we brought down our build times. General optimization tips
