How jouwdan/todo works
Project type and purpose
• This is a native Android mobile application (“Todo”) written in Kotlin.
• It follows MVVM and Clean Architecture principles, uses Jetpack Fragments & Navigation, Hilt for DI, and Firebase (Authentication + Firestore) as its backend.
File structure
• Top-level “app” module contains all source code.
• “src/main/java/dev/jord/todo” subdivides into:
• data/model (Task, User)
• data/repository (interface + implementation)
• di (Hilt modules: AppModule, FirebaseModule, RepositoryModule)
• ui (Fragments split into auth, home, account) + ViewModels + Adapters
• util (Constants, Extensions, UiState)
• Navigation XML files for auth & home flows
• Activities (LoginActivity, MainActivity) host the NavHostFragments
• Tests & Android instrumentation tests mirror source structure
• build scripts, ProGuard, manifest, resource layouts, drawables, themes
Insights from README
• Uses Firebase Auth & Firestore as its sole backend
• UI built on Material 3, adapts system theme
• Strong emphasis on MVVM / Clean Architecture
• Dependency injection via Dagger Hilt
Elements
• User actions → Fragment → ViewModel → Repository Interface → Repository Impl → Firebase
• Firebase responses → Repository Impl → ViewModel → Fragment
• ViewModels in another
• Repository interfaces & implementations in a third
• External services (Firebase) in a cloud symbol or different hue
• Navigation XMLs as part of UI layer
• Hilt Modules and where they inject dependencies