How piashcse/hilt-mvvm-compose-movie works
Project type and purpose
• A native Android application (min SDK 23+)
• Implements MVVM with Repository pattern, local Room DB, remote TMDB API, Paging 3
• Purpose: Browse/search movies, TV-series, celebrities, manage favorites
File structure
• app/src/main/java/com/piashcse/hilt_mvvm_compose_movie
– di: Hilt modules (NetworkModule, DataBaseModule, RepositoryModule)
– data: datasources (local & remote), models, repositories (local & remote)
– network: API interceptor, constants
– ui: Composable components, screens, navigation, themes, state
– utils: constants, extensions, network‐connection helpers
– HiltApplication.kt: Application class for DI
• app/src/main/res: UI resources
• build scripts: Gradle Kotlin DSL, CI/CD workflow
Extract README insights
• Patterns: MVVM (Model–ViewModel–View), Repository
• Tech stack: Kotlin, Compose, Hilt, Coroutines, Flow, Room, Retrofit, Paging3
• External service: The Movie DB API (requires API key)
Main components & interactions
A. UI Layer
– Composable Screens & Components (e.g. MovieList, MovieDetail, FavoriteMovie)
– Navigation Graph (NavGraph)
B. ViewModel Layer
– One ViewModel per screen (e.g. MainViewModel, MovieDetailViewModel)
– Exposes State (Flow/LiveData) to UI
C. Domain/Data Layer
– Repositories
• RemoteRepositoryImpl (Retrofit ApiService + PagingDataSource)
• LocalRepositoryImpl (Room DAOs)
– DataSources
• ApiService (Retrofit interface)
• MovieWorldDataBase (Room database)
• DAOs: FavoriteMovieDao, FavoriteTvSeriesDao
D. External Systems
– TMDB REST API (HTTPS calls via Retrofit + OkHttp + ApiKeyInterceptor)
E. Dependency Injection
– Hilt Modules provide singletons: Retrofit, OkHttpClient, Database, Repositories
Relationships & data flow
1. UI → calls ViewModel functions (e.g. fetchPopularMovies())
2. ViewModel → invokes Repository interfaces
3. Repository → chooses DataSource
• Remote paths: Repository → ApiService → Remote PagingDataSource → Flow<PagingData>
• Local paths: Repository → Room DAO → Flow<List<Entity>>
4. Data flows back up as Flow/LiveData → ViewModel → UI consumes & renders
5. Hilt: at application startup, modules wire up Retrofit, DB, Repos, ViewModels
Architectural patterns & principles
• MVVM: separation of concerns (UI vs state vs data logic)
• Repository pattern: abstracts data sources (local vs remote) behind a common interface
• Paging3: for infinite scroll lists
• Single Responsibility & DI: each module/class has one role, dependencies injected via Hilt
Essential elements
– HiltApplication (app entry)
– NetworkModule → provides Retrofit + ApiKeyInterceptor
– DataBaseModule → provides Room database + DAOs
– RepositoryModule → binds interfaces to implementations
– ApiService & PagingDataSources (e.g. PopularMoviePagingDataSource)
– Room DAOs & MovieWorldDataBase
– ViewModels for main screens
– Composable NavGraph & sample Screen
– The Movie DB API as external system