How decoutkhanqindev/dexreader works
Project type and purpose
• Dex Reader is an Android mobile application (client-side) implemented in Kotlin with Jetpack Compose.
• It follows Clean Architecture with MVVM, fetching manga data from the MangaDex API and synchronizing user data via Firebase Auth & Firestore.
• Purpose: present manga lists, details, reader, search, categories, favorites, history, profile, settings.
File structure
• Top-level module: app/ (Gradle, AndroidManifest, resources, Kotlin sources).
• Packages under com.decoutkhanqindev.dexreader:
• data/ (local database & prefs, network APIs & DTOs, repository implementations, mappers)
• domain/ (models, repository interfaces, use-cases)
• presentation/ (Composable screens, view models, navigation, theme)
• di/ (Hilt modules: LocalDataModule, NetworkDataModule, RepositoryModule)
• utils/ (shared helpers)
• Build scripts: Gradle Kotlin DSL, google-services.json, proguard, wrapper.
• Tests: instrumented and unit tests.
README for additional insights
• Architecture: MVVM + Clean Architecture.
• Tech stack: Kotlin, Compose, Hilt, Room, DataStore, Retrofit + OkHttp + Moshi, Firebase Auth, Firestore, Coil, Coroutines/Flow.
• Features: caching, pre-fetching, theme sync.
2. In Presentation layer, list major screens (Home, Reader, Search, Categories, Details, Auth, Profile, Settings) plus ViewModels.
– Local: Room DAOs & DataStore
– Network: Retrofit services (MangaDexApiService), FirebaseAuthSource, FirestoreSource
6. DI container (Hilt) on the side or as an overarching module injecting each layer’s dependencies.