android-gradle-logic

Centralize Gradle build logic by consolidating common Android configurations into reusable convention plugins within a dedicated build-logic module, applying them across modules to eliminate configuration duplication and drift.

A Gradle convention plugin is a reusable plugin that enforces standard Android settings like Compose, Kotlin options, and Hilt configurations. It is registered in a composite build to maintain consistent multi-module project setups.

Yes, manage Android dependencies using a Version Catalog by defining versions in a single libs.versions.toml file. Convention plugins reference this catalog to centralize dependency management across all project modules.

The best way to reduce duplicated Gradle configurations is implementing a composite build with a build-logic module containing convention plugins. This approach replaces scattered module-level build scripts with centralized, reusable configuration blocks.

Yes, adopt Gradle convention plugins incrementally by adding the build-logic module progressively across multi-module projects. This safe adoption strategy allows you to migrate modules individually without disrupting existing build configurations.

Configuration drift occurs when Android projects suffer from fragmented Gradle configurations across modules. Centralizing common settings like Compose and Hilt into convention plugins eliminates this drift by enforcing consistent configurations project-wide.