How gauravk95/mvp-kotlin-android works
Project Type and Purpose
• This is an Android mobile‐client application template written in Kotlin.
• It implements the MVP (Model–View–Presenter) pattern, uses Dagger2 for dependency injection, RxJava2 for reactive streams, Retrofit2 for network calls, and Room for local persistence.
File Structure
• Top‐level “app” module contains:
• src/main/java/com/github/mvpbasearchitecture/base (BaseActivity, BasePresenter, etc.)
• data (models, local/remote sources, repositories)
• di (Dagger components & modules)
• ui (Activities, Fragments, Adapters, Presenters)
• utils (Rx schedulers, extension functions, font utilities)
• res (layouts, drawables, values)
• Build scripts & config: build.gradle, proguard rules, AndroidManifest, gradle wrapper.
README for Insights
• README explicitly calls out modules: base, data (with sub‐packages), di (component/module), ui (custom, adapters, main), utils.
• Provides an MVP architecture blueprint image—use this as a reference.
Main Components
a. View Layer
• MainActivity & MainFragment (UI)
• XML layouts (activity_main.xml, fragment_main.xml, item_main.xml)
b. Presenter Layer
• MainPresenter (implements MainContract.Presenter)
• BaseMVPActivity/BaseMVPFragment (generic wiring)
c. Data Layer
• AppDataRepository (repository façade)
• Local Data Source: Room (AppDatabase, ItemDao) + AppLocalDataSource
• Remote Data Source: Retrofit (APIService, NetworkAPIs) + AppRemoteDataSource
• Preferences: AppPreferences (SharedPreferences abstraction)
d. Dependency Injection
• ApplicationComponent & ApplicationModule
• ActivityComponent & ActivityModule
• NetworkModule, DataModule, DatabaseInfo, PreferenceInfo
e. External Services
f. Persistence
g. Utilities
• RxJava SchedulerProvider, extension methods, font utils (auxiliary nodes)
Relationships & Data Flow
• UI → Presenter: user actions trigger Presenter methods.
• Presenter → Repository: calls AppDataRepository.getItems() (returns Rx Observable/Single).
• Repository → DataSources: decides whether to fetch from local DB or network; merges results.
• Remote Data Source → Retrofit APIService → External HTTP service.
• Local Data Source → Room database via DAO.
• Repository emits data back to Presenter → Presenter updates View.
• DI graph: ApplicationComponent provides singletons (NetworkModule, DataModule); ActivityComponent injects Activities/Fragments.
Architectural Patterns & Technologies
• MVP (clear separation of View, Presenter, Model).
• Repository pattern for data abstraction.
• Retrofit2 for HTTP client.
• Room for local persistence.
Final Checklist
• Clear labels on all components (class names or group names).
• A note on the architectural pattern (MVP + Repository + DI + Rx + Retrofit + Room).