~/talk

Build bigger, better: Gradle for large projects

Talkat Google I/O 2019 · 2019-05-07..05-09· [android, developer-experience]
links:none on file
slides:none on file

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

  1. 0:00Intro
  2. 0:36Android Projects are the same
  3. 0:58Android X build growth
  4. 2:19Java or Kotlin only libraries
  5. 2:58Apply only needed plugins
  6. 3:19Scope annotation processors
  7. 3:41Lint final app module
  8. 4:09Use api and implementation
  9. 4:39Modularization side-effects
  10. 9:30Per-module configuration
  11. 14:58General Advice
  12. 15:22Lazy task configuration
  13. 16:09Task Wiring
  14. 22:18Computation during Configuration
  15. 25:53Caveats
  16. 29:44Gradle Memory Limits
  17. 32:07Limit Gradle workers
  18. 33:25Tracer Agent
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.