How mrihsann/expense-tracking-app works
Project type and purpose
• This is a single-module Android application (“Expense Tracking App”) built with Kotlin and Jetpack Compose
• It follows a Clean Architecture / MVVM pattern for tracking user expenses and handling authentication
High-level architectural layers
• Presentation Layer
– Composable Screens (AuthScreen, HomeScreen, ListScreen, AddScreen, SettingsScreen, TrackingScreen)
– ViewModels (AuthViewModel, HomeViewModel, ListViewModel, AddViewModel, SettingsViewModel)
– NavigationGraph & Screen sealed class
• Domain Layer
– Use Cases (SignIn, SignUp, SignOut, CurrentUser)
– Repository Interfaces (IFirebaseAuth)
– Domain Models (Expense, ExpenseCategory)
• Data Layer
– Repository Implementations (FirebaseAuthImpl)
– Local Data Source (AppDataStore using Android DataStore)
– Remote Data Source (Firebase Auth service)
– DI Modules (FirebaseModule, LocalStorageModule, RepositoryModule, UseCaseModule)
External components
– Firebase Authentication (external cloud service)
– Android DataStore (local key-value persistence)
Relationships and data flows
UI (Compose Screens) → ViewModels
ViewModels → Use Cases (domain)
Use Cases → Repository Interfaces
Repository Interfaces → Implementations (data)
• FirebaseAuthImpl → Firebase Auth
• AppDataStore → DataStore
Any asynchronous or callback responses flow back up the same path in reverse
Key architectural patterns
– MVVM (ViewModel mediates between UI and domain)
– Clean Architecture layering for testability and separation of concerns
– Dependency Injection (modules register interfaces to implementations)
– Jetpack Compose for UI, Android Navigation for routing
[ ] DI modules and bindings explicitly shown