How shub39/grit works
Project type and purpose
• This is a native Android mobile application (“Grit”) written in Kotlin.
• Purpose: a simple To-Do list and daily habit tracker featuring analytics, notifications, widgets, and backup/restore.
File structure
• Top-level:
• app/ – the single Android application module
• build scripts (Gradle, fastlane, CI workflows)
• app/src/main/java/com/shub39/grit: follows a clean-architecture style, divided into:
• app/ – Application & Activity entrypoints + Navigation
• core/ – cross-cutting layers:
data/ (DataStore, notifications, backup)
domain/ (interfaces and models)
presentation/ (shared UI components and themes)
• di/ – dependency-injection modules (Koin or Hilt style)
• features:
habits/ (feature-specific data, domain, presentation)
tasks/ (same as above)
• viewmodels/ – MVVM ViewModel classes
• widgets/ – Android AppWidgets for home-screen display
• Persistence: Jetpack DataStore + Room databases (HabitDatabase, TaskDatabase).
• Receivers: BootReceiver, NotificationReceiver for scheduling via AlarmManager.
• Backup/Restore: ExportImpl / RestoreImpl under core/data/backup.
README for additional insights
• Confirms feature set: Todos, Habit tracking, analytics, notifications, widgets.
• No external servers or cloud backends—entirely on-device with optional backup export.
Elements
• Blue for UI/Presentation
• Green for Domain
• Orange for Data/Persistence
• Gray for Android System & external services