COMPILING...? HOW TO REDUCE YOUR WAIT TIMES AND "GET BACK TO WORK"
summary
An Android app with an initial clean build of 3m20s reaches ~45s after concrete changes: bumping to Gradle 4.4 and Android plugin 3.1.2, enabling Gradle daemon and parallel tasks saves ~1 minute, updating Kotlin plugin saves ~10s, converting PNG→WEBP trims 5MB APK, removing AutoValue and Butter Knife saves ~15s and ~4.5s, and turning on build cache saves ~1m40s; disabling Crashlytics cuts noop builds to ~5s. Uses Gradle profiler, remote cache (Artifactory) explored; Bazel proves hard to port.
AI-written summary · about
chapters (17)
- 0:00Introduction and motivation
- 1:05Current build setup and pain points
- 3:10First optimizations and Gradle updates
- 5:19Resource and dependency tweaks
- 6:23Removing annotation processors
- 7:27Build cache and Crashlytics impact
- 8:48Remote build cache benefits
- 9:51Modularization and JVM modules
- 10:32Kotlin vs Java compilation
- 11:14Workflow and testing improvements
- 11:56Hardware and remote builds
- 12:37Profiling and analysis tools
- 13:20Exploring Bazel for Android
- 15:27Time savings and cost-benefit analysis
- 16:10Maintenance and CI integration
- 17:13Alternative tools and resources
- 17:57Q&A and closing remarks
related talks
27mFaster builds on Android: from 2 minutes to 2 seconds
31mImproving Android Build performance
40mBuild times breaking your flow? Learn how to make them fast!
19mGetting to a green build with caching on CI
57mImprove Build Times in Less Time
41mKeeping your team's Gradle builds in top shape
30mAndroid Developer Productivity
32m5 ways to improve your Android build productivity