android-kotlin-patterns

Modern Android Kotlin architecture standardizes a Compose + MVVM + Room + DI blueprint. It separates UI, domain, data, and DI modules to provide reliable state management, persistence, networking, and async handling for mobile build workflows.

Set up Room and Retrofit by layering Room repository/DAO patterns for local persistence and integrating Retrofit/OkHttp for networking. Use Coroutines and Flow patterns within your ViewModel + StateFlow to handle async work and expose data cleanly to the UI.

Yes, this Android Kotlin architecture pattern supports state hoisting in Jetpack Compose. It applies Kotlin best practices including Compose state hoisting and using stable types with LazyColumn to ensure reusable UI components and optimal rendering performance.

Yes, you can use this MVVM blueprint to refactor an existing Android app. It applies to creating or refactoring Android projects, replacing scattered or outdated architecture choices with a reliable baseline using ViewModel with StateFlow and Hilt DI.

You should not use Jetpack Compose with MVVM and Hilt if your project cannot support modern Kotlin dependencies. This architecture requires adopting Coroutines/Flow, Hilt DI modules, and Compose state hoisting, which may not suit legacy codebases with strict legacy constraints.