kotlin-project-modularization

To review Kotlin Multiplatform module boundaries, analyze app, feature, data, and common modules to verify dependency direction, visibility control, granularity, and ownership cohesion. This structural analysis identifies leaked internals and incorrect module types during architecture audits.

Analyzing an Android modularization dependency graph requires checking whether dependencies flow in a clean direction without leaking internals. This structural review assesses module granularity, ownership cohesion, and testability to determine which modules should split, merge, or become internal.

To determine if Kotlin modules are too coarse or too fine, assess their granularity and structure against ownership cohesion. Evaluating module type choice and responsibility boundaries reveals whether modules should split, merge, or hide internals to improve maintainability.

Yes, this modularization review applies to both Kotlin Multiplatform and Android apps. It evaluates app, feature, data, and common modules during design reviews, refactors, and architecture audits to verify dependency direction, visibility control, and testability.

You should refactor Android modules to hide internals when dependency analysis reveals leaked module internals or incorrect dependency directions. Adjusting visibility control and module type choice during a refactor improves build hygiene and long-term maintainability.