android-modularization

To enforce Clean Architecture boundaries in Android modularization, split modules by feature first, then by layer. Keep domain modules independent, while data and presentation layers depend on it in a controlled way to isolate responsibilities.

Add a new feature module without tangled Gradle dependencies by creating `:feature:<name>:domain`, `:feature:<name>:data`, and `:feature:<name>:presentation`. Register these in `settings.gradle.kts` and apply Gradle convention plugins for standardized build setup.

Share code across Android feature modules without coupling by centralizing shared domain models in `:core:core-domain` and shared UI logic in `:core:core-view`. This cross-feature sharing strategy prevents direct feature-to-feature dependencies.

Gradle convention plugin standardization works with version catalogs for multi-module builds. You standardize build setup by defining convention plugins in a `:build-logic` module and driving the build rules through your version catalog.

Use Kotlin Multiplatform shared core locations for reusable code when you need to prevent feature coupling across targets. Centralizing reusable logic in core modules ensures feature modules remain isolated and adhere to strict layer dependency constraints.