How sonyaouthred/divvy works
Project type and purpose
• This is a cross-platform mobile/desktop/web front-end written in Flutter/Dart.
• Purpose: a chore-sharing app (“Divvy”) with user authentication, chore scheduling, swap flows, and notifications.
• The front end talks to two back-end services: Firebase Authentication and a Flask REST API server (hosted separately in its own repo).
File structure
• Top-level platform folders (android, ios, linux, macos, web, windows): Flutter build targets and platform wrappers.
• lib/ folder: holds the bulk of the front-end code, organized into:
• models/ (domain objects: Chore, House, Member, Swap, etc.)
• providers/ (state management via Provider: DivvyProvider)
• screens/ (UI pages corresponding to each user flow: login, dashboard, house screens, etc.)
• widgets/ (reusable UI components: tiles, dialogs, leaderboard)
• util/ (helper functions: date utilities, dialog builders, server_util for REST calls)
• firebase/ (Firebase auth service and auto-generated firebase_options.dart)
• divvy_navigation.dart (bottom nav bar)
• main.dart (app entrypoint)
• Configuration and CI: .github/workflows/flutter-ci.yaml, analysis_options.yaml, pubspec.yaml, firebase.json.
README for additional insights
• Confirms Flutter 3.32 / Dart 3.8+ stack.
• States the need to run a separate Flask server locally for data persistence.
• Describes CI: GitHub Actions runs flutter test and builds on iOS/Android.
• Documents code structure, dependencies, and build/run steps.
Elements
• Clear labels (e.g., “ChoreModel”, “DivvyProvider”, “server_util RESTClient”)
• Annotations for protocols (HTTPS/REST) and data formats (JSON)