new-module-checklist

Adding a new Gradle module requires updating settings.gradle.kts, registering it in the central module registry, and relying on CorePlugin conventions. You must also place the module in the correct directory family and run assemble and formatting validation to catch configuration errors early.

To wire Koin dependency injection for a new module, hook the module into the nearest Koin aggregator and configure the Koin loaders appropriately. This ensures your new feature, data, or common module integrates seamlessly with the existing Android architecture and dependency injection graph.

Structuring domain and data interfaces in a new module involves organizing domain repositories and use cases appropriately, including handling hybrid operation splits. Following this architectural convention ensures clean separation between your data layer and domain logic within the Android codebase.

You should extend an existing module surface instead of creating a new Gradle module when the new functionality logically fits within the current architecture. Evaluating this during module creation prevents unnecessary module sprawl and maintains the repository's expected layout and build conventions.

After introducing a new Gradle module, the required build validation steps are assembling the module and running formatting checks. These integration checks validate the Gradle registration and Koin wiring, catching configuration errors early before they impact the broader Android build.

Yes, Gradle module creation applies across multiple types including feature, data, common, task, and android helper modules. Each module type follows the same conventions-first approach for settings inclusion, central registry updates, and Koin dependency injection wiring.