Kotlin Android MVVM – Repository Pattern

I will build a complete Android feature following clean MVVM architecture — covering a Room database entity and DAO, Repository abstracting local and remote data sources, ViewModel with StateFlow UI state management, Hilt dependency injection, Retrofit networking with Kotlin coroutines, and a Jetpack Compose or XML UI layer. A properly layered Android feature with Hilt injection is independently testable at every layer, extendable without breaking existing functionality, and consistent with the architecture pattern your team uses across the rest of the app.

The feature covers Room entity, DAO, and database configuration, Repository with remote and local source coordination, ViewModel with loading, success, and error states, Hilt module for all dependencies, Retrofit API interface with coroutine suspend functions, and UI layer observing StateFlow. Unit tests cover the ViewModel and Repository layers.

Designed for Android teams needing a production-quality feature built to clean architecture standards without diverting internal sprint resources.