How rubberduckcrew/gitdone works
Project type and purpose
• GitDone is a Flutter-based Android mobile app whose sole responsibility is to let users authenticate with GitHub (OAuth) and convert to-dos into GitHub issues by talking directly to the GitHub REST API.
• It is a client-only application (no custom backend), structured around Flutter’s standard folder layout and following an MVVM-style separation of UI, view-models, and core services.
File structure
• Top-level directories:
• android/: native Android app wrapper and Gradle build files.
• lib/: all Dart code, subdivided into:
– app.dart / main.dart: app entrypoint and configuration.
– core/: domain & infrastructure (API handler, models, token management, theme, utilities).
– ui/: presentation layer (screens, widgets, view-models) organized by feature (welcome, login, home, settings).
• Patterns: MVVM in ui/ (screen ⇄ view-model), layered core services for API calls and token management.
Pulling additional insights from README
• Key features: GitHub OAuth, issue management (sync planned).
• Roadmap indicates future syncing, but current focus is on OAuth flow and issue creation.
• Tech stack: Flutter & Dart on Android, HTTP REST client to GitHub, standard Flutter widgets.