How phuhuynhh/moviefindr works
Project Type and Purpose
• This is a native Android mobile application (“Movie Findr”) written in Kotlin, using Jetpack Compose for UI.
• It follows Clean Architecture: three Gradle modules named app (presentation), domain (business logic), and data (data access).
• It fetches movie data from The Movie Database (TMDB) API, caches results in Room, and supports offline mode.
Overall Architectural Pattern
• Presentation layer (app module) depends on domain.
• Domain layer defines use-case interfaces and business models.
• Data layer implements repositories that satisfy domain interfaces, providing remote (Retrofit+OkHttp+Moshi) and local (Room) data sources.
• Dependency injection modules wire everything together.
Main Components
A. Mobile Client (Android Device)
• Presentation / UI
– Jetpack Compose screens & components
– ViewModels (extend BaseViewModel)
– Navigation graph (AppNavGraph, MainNavGraph)
• DI Container
– Modules: AppModule, MoshiModule, OkHttpClientModule, RetrofitModule, RepositoryModule, StorageModule
B. Domain Layer (jar module)
• Use cases: GetMoviesUseCase, GetMovieDetailUseCase
• Repository interfaces: MoviesRepository, MovieDetailRepository
• Models: MovieInfo, MovieDetailInfo, PaginatedList, DataResult, NetworkError
C. Data Layer (aar module)
• Remote Data Source
– Retrofit / Moshi
– ApiService + AuthorizationParamInterceptor
– NetworkObserver
• Local Data Source
– Room database (WhatMovieDatabase)
– DAOs: MoviesDao, MoviePageDao, MovieDetailEntityDao
• Repositories implementing domain interfaces
– MoviesRepositoryImpl (decides fetch-from-cache vs fetch-from-network)
– MovieDetailRepositoryImpl
D. External Service
• TMDB REST API (requires API token stored in gradle.properties)
Relationships and Data Flow
1. UI Layer triggers an action (e.g., “Load Movies”)
2. ViewModel calls the corresponding UseCase in domain
3. UseCase invokes repository interface
4. RepositoryImpl chooses:
• Remote call: Retrofit → TMDB API → JSON → Moshi → domain models
• Local call: Room DAO → Entities → mappers → domain models
5. Domain models returned to ViewModel
6. ViewModel maps domain models → UI models (UiMovie, UiMovieDetail)
7. Compose UI observes state flows and renders screens
8. Offline scenario: repository detects no network via NetworkObserver and falls back to Room cache
Important Architectural Patterns & Principles
• Clean / Hexagonal Architecture (clear module boundaries, dependency inversion)
• Single Responsibility: each layer handles its own concern (UI vs business vs data)
• Repository pattern for data abstraction
• Dependency injection for decoupling and testability
• MVVM in presentation (ViewModel + Compose UI)
• Coroutines + DispatchersProvider to control threading
Technology & Framework Highlights
• Kotlin, Jetpack Compose, AndroidX Navigation
• Dagger-style DI modules (could be Koin or Hilt)
• Retrofit + OkHttp + Moshi for networking
• Room for local persistence
• Coroutines for async
• Unit tests in domain/data, AndroidTests in app