How matheus-miranda/run-tracker works
Project type and purpose
• This is a fully modularized Android application ("RunTracker") implementing a Clean (on-device) architecture.
• Purpose:
• User authentication (Register, Login)
• Run tracking (start, pause, resume, finish runs; collect GPS data; sync runs)
• Analytics dashboard (aggregate run metrics).
File structure
• Top-level modules:
• app – the Android application host, navigation, DI wiring, theme setup
• auth, run, analytics – each split into data, domain, presentation sub-modules
• core – shared code (data, database, domain, presentation/design system, UI helpers)
• build-logic – custom Gradle convention plugins
• Pattern: each feature follows a layered Clean Architecture:
presentation → domain → data
• Data modules use Room (core/database) and Ktor HTTP client (run/network, core/data/networking). Run/data also uses WorkManager (CreateRunWorker, FetchRunsWorker, etc.)
• DI modules in each layer (…/di/…Module.kt).
README for additional insights
• UI flows: Home, Register, Login, New Run, Running, Paused, Resumed, Finished, Analytics
• Confirms three main feature areas: authentication, running, analytics.