Build bigger, better: Gradle for large projects
summary
AndroidX grows from 5 to 240 Gradle projects and 90k to 400k lines of code, so the talk explains concrete fixes: centralize dependency versions with a buildSrc Kotlin module, replace repeated 150-line build.gradle files with ~35-line modules via a custom plugin DSL, use lazy APIs (Property, DirectoryProperty, flatMap), prefer Worker API and custom task types, and measure with Build Scans and a homegrown Tracer Agent; experiments pick an ~8 GB JVM for best build vs GC tradeoff.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:36Android Projects are the same
- 0:58Android X build growth
- 2:19Java or Kotlin only libraries
- 2:58Apply only needed plugins
- 3:19Scope annotation processors
- 3:41Lint final app module
- 4:09Use api and implementation
- 4:39Modularization side-effects
- 9:30Per-module configuration
- 14:58General Advice
- 15:22Lazy task configuration
- 16:09Task Wiring
- 22:18Computation during Configuration
- 25:53Caveats
- 29:44Gradle Memory Limits
- 32:07Limit Gradle workers
- 33:25Tracer Agent
related talks
40mImproving Android Build Performance
36mImproving Gradle Builds
28mEffective Gradle Scripts for Android Projects
48mGradle 3.0 and beyond for Android Development
32m5 ways to improve your Android build productivity
34mWhat's new with the Android Gradle plugin
51mCreate Elegant Builds At Scale With Gradle
41mKeeping your team's Gradle builds in top shape
