gradle-build-performance

Start by generating a Build Scan with ./gradlew assembleDebug --scan to identify the slow phase. Then enable configuration cache, build cache, and parallel execution in gradle.properties, and apply one optimization at a time while measuring results.

Replace kapt dependency declarations with ksp equivalents for supported libraries like Hilt, Room, and Moshi, and swap the kotlin-kapt plugin for com.google.devtools.ksp. KSP is roughly twice as fast as kapt and is mandatory for AGP 9 compatibility.

Yes, configuration cache is supported on AGP 8.0 and later. Enable it with org.gradle.configuration-cache=true in gradle.properties, starting with problems=warn mode and moving to fail once your build is clean of configuration-phase I/O.

Slow configuration is usually caused by eager task creation with tasks.create(), file or network I/O during configuration, or subprojects/allprojects blocks in the root build file. Fix these by using tasks.register(), deferring I/O with providers, and adopting convention plugins.

Cache misses typically come from non-deterministic task inputs, dynamic dependency versions like 1.+, or tasks that were never marked cacheable. Enable org.gradle.caching=true, pin exact dependency versions, and audit task inputs for stability.