How 7und3dpy/mobile-programming-project works
Project type and purpose
• This is a single-module Android mobile application (“Dogs Application”) built in Kotlin. It follows MVVM (Model-View-ViewModel), uses Jetpack components (ViewModel, Room, Paging 3), Retrofit/Moshi for networking, and Hilt for dependency injection. Its purpose is to fetch, cache, paginate, and display a list of dog images/data in a RecyclerView.
File structure
• Top-level “app” module with Gradle, ProGuard, tests, AndroidManifest, etc.
• Under app/src/main/java/turio/it4785e/displaydog you see these packages:
• ui (MainActivity, MainViewModel, layouts, adapter) – presentation layer
• data (model, dao, database, repository/RemoteMediator) – data layer
• network (ApiService) – remote data source
• di (AppModule) – DI definition
• adapter – RecyclerView adapter
• Configuration files: Hilt setup in AppModule, Room schema in Database.kt, Retrofit in ApiService.
README for additional insights
• Confirms use of Coroutines, Flow, Paging 3, Room, Retrofit, Moshi, Coil, Material Components, JUnit/Espresso, MultiDex.
Main components
a. Presentation Layer
• UI: MainActivity + XML layouts + DogsAdapter
• ViewModel: MainViewModel (exposes Flow/LiveData to the UI)
b. Dependency Injection
• Hilt AppComponent & AppModule (provides ApiService, Database, DAOs, Repository)
c. Data Layer
• Repository: DogsRemoteMediator implements PagingSource + RemoteMediator
• Local Data Source: Room Database + DogsDao + RemoteKeysDao
• Remote Data Source: Retrofit ApiService + Moshi converter
d. External Services
• REST API endpoint (hosted externally; returns paginated dog data)
e. Cross-cutting
• Kotlin Coroutines & Flow (across ViewModel, Repository, networking, DB threads)
Relationships and interactions
• Repository →
• Hilt provides all dependencies into ViewModel, Repository, ApiService, Database
Architectural patterns and principles
• MVVM: clear separation of UI, state management (ViewModel), and data sources
• Repository + RemoteMediator: abstracts paging and caching logic
• Single source of truth: local Room database backed by network
• Dependency inversion via Hilt modules