android-gradle-logic

Centralizing Android Gradle configurations involves creating a build-logic module with convention plugins and a libs.versions.toml version catalog. This setup enforces consistent Kotlin options, Compose configuration, and dependency management across all modules.

Gradle convention plugins are custom build plugins that encapsulate shared configuration logic for Compose, Kotlin options, and Hilt. You need them in multi-module Android projects to prevent configuration drift and ensure uniform library versions across all modules.

To set up a build-logic module, create the directory, wire it into settings.gradle.kts as a plugin management source, define dependencies in libs.versions.toml, and apply the published custom convention plugin in your app/build.gradle.kts file.

Yes, this approach works for existing multi-module Android projects requiring a Gradle-based setup. It integrates by applying custom convention plugins to standardize configurations and reduce dependency drift across your established modules.

The best way to manage dependencies and prevent version drift is using a Gradle version catalog (libs.versions.toml) combined with convention plugins. This centralizes library versions and shared configurations in a single build-logic module.