android-gradle-logic

Centralize Android Gradle build configurations by defining common settings like Kotlin options and Compose setup in reusable Gradle Convention Plugins. This eliminates repetitive build configuration across multiple Android modules.

Manage all Android dependencies and plugin versions in a single file by utilizing a Gradle Version Catalog. This Skill configures a `libs.versions.toml` file to facilitate centralized version management across your entire project.

The best way to share Kotlin compiler and target SDK options is by applying Gradle Convention Plugins. This ensures all Android application modules consistently use the same configurations without manual copy-pasting in each `build.gradle.kts` file.

Yes, you can use Gradle Convention Plugins to set up Hilt and Compose. This Skill allows you to define common configurations like Compose setup and Hilt once, ensuring consistent application across your Android modules.

To apply a convention plugin to your Android app module, add the specific plugin ID to your module's `build.gradle.kts` file. For example, apply the `nowinandroid.android.application` plugin to quickly start using centralized build logic.

Multi-module Android projects often have inconsistent build configurations due to manual copy-pasting in individual `build.gradle.kts` files. Centralizing logic into reusable Gradle Convention Plugins and Version Catalogs solves this by adhering to modern Android development best practices.