How njogubless/mwendo works
Mwendo is an adaptive routine and personal-progress app. Its documented user journey is to manage routines, work through a daily plan, and review progress; the sampled tracking service materializes plans and supports completion and adaptation. The tree also identifies accounts, goals, and insights API subsystems, but their detailed behavior and endpoint wiring were not sampled. The Flutter application sources are not present in the supplied tree, so the graph focuses on the backend and does not infer mobile-to-API calls.
Main entry points: tracking/services.py Day operations · routines/services.py Routine services · accounts/services.py Account services · urls.py Django API
Components 17
API and accounts
- Django API
backend/config/urls.py - Accounts
backend/apps/accounts - Account services
backend/apps/accounts/services.py
Routine management
- Routine endpoints
backend/apps/routines/views.py - Routine services
backend/apps/routines/services.py - Routine data
backend/apps/routines/models.py
Daily tracking
- Tracking endpoints
backend/apps/tracking/views.py - Day operations
backend/apps/tracking/services.py - Adaptation logic
backend/apps/tracking/domain - Plan and completion data
backend/apps/tracking/models.py
Goals and insights
- Goal endpoints
backend/apps/goals/views.py - Goal data
backend/apps/goals/models.py - Insights endpoints
backend/apps/insights/views.py - Progress queries
backend/apps/insights/selectors.py
Other components
- App user
- Email service
- PostgreSQL
Connections 9
- App user → Django API: uses
- Account services → Email service: sends reset email
- Routine services → Day operations: syncs today's plan
- Routine services → Routine data: writes routines
- Day operations → Adaptation logic: plans adaptations
- Day operations → Plan and completion data: updates plans
- Account services → PostgreSQL: stores accounts
- Routine services → PostgreSQL: stores routines
- Day operations → PostgreSQL: stores tracking