gradle-build-performancelisted

Gradle build speed per Google's docs: Build Analyzer, gradle-profiler, configuration cache, build cache and remote CI cache, KSP, heap and GC tuning, AGP 9 defaults, Isolated Projects. Use when builds or sync are slow, tasks rerun with no changes, remote cache misses, configuration cache problems appear, kapt dominates, or garbage collection eats build time.
pablitoarango/android-skills · ★ 3 · Web & Frontend · score 74

Install: claude install-skill pablitoarango/android-skills

# Gradle Build Performance Sources of truth: [Optimize your build speed](https://developer.android.com/build/optimize-your-build), [Profile your build](https://developer.android.com/build/profile-your-build), [Build Analyzer](https://developer.android.com/build/build-analyzer), [Gradle build overview](https://developer.android.com/build/gradle-build-overview), [Migrate to KSP](https://developer.android.com/build/migrate-to-ksp), [Built-in Kotlin (AGP 9)](https://developer.android.com/build/migrate-to-built-in-kotlin), [AGP 9.0 release notes](https://developer.android.com/build/releases/agp-9-0-0-release-notes). Gradle facts: [build cache](https://docs.gradle.org/current/userguide/build_cache.html), [configuration cache](https://docs.gradle.org/current/userguide/configuration_cache.html), [Isolated Projects](https://docs.gradle.org/current/userguide/isolated_projects.html), [build environment](https://docs.gradle.org/current/userguide/build_environment.html). ## How to work on a slow build Google splits the job into two stages: apply the configuration changes that help almost every Android project, then profile to find what is specific to this project or machine. 1. **Name the build that hurts.** Usually an incremental debug build after a code edit, sometimes sync or a CI job. Time it several times. The first build after the Gradle daemon starts is slower because the JVM warms up, so do not count it. 2. **Close the gaps in the baseline setup.** Check the project against se