android-architecture

Structure an Android app by enforcing strict layer separation across presentation, domain, and data. Keep business logic out of ViewModels, define repository interfaces in the domain layer, and inject data implementations to ensure feature modules remain testable and scalable.

The best way to modularize an Android project with Hilt is by setting up dependency injection scopes and repository bindings across feature and core module graphs. Apply feature-to-core dependency rules to maintain clear boundaries and scalable production builds.

Manage UI state and effects in Android MVI by using single-state UI models and shared-flow effects. This approach centralizes screen rendering logic and ensures that UI updates remain predictable and consistently testable across feature modules.

Yes, you can apply clean architecture boundaries to AOSP Soong builds. The architecture design principles support Android Studio Gradle projects and AOSP Soong builds when planning layered screens, repository flows, and domain logic separation.

ViewModels leak dependencies when strict layer separation is violated. Refactor the screen into a feature module with domain use cases and a repository interface, ensuring dependencies and dispatchers are explicitly injected rather than directly referenced.

Choose MVI over MVVM when you need strict single-state UI models and unidirectional data flow for predictable screen rendering. MVI enforces shared-flow effects and pure domain logic, while MVVM offers flexibility for separating presentation from business logic.