How dozenbro/group13-smart-nutrition-fitness works
The current product is a shared-history web demo for recording weight and height, calculating BMI, and reviewing recent measurements. A user enters a measurement in the React interface; FastAPI validates and saves it, calculates BMI, and returns it for display. Reloading history requests saved records. PostgreSQL persistence and schema versioning are documented. TDEE calculation exists internally but is not exposed by the API. Accounts, workouts, and meal suggestions are roadmap capabilities, not implemented workflows; their source implementation is therefore not represented. Unsampled roadmap details are limited to the README’s stated scope.
Main entry points: main.py Measurement endpoints · main.jsx Measurement interface · database.py Database sessions · SPRINT_2.md Workout plans
Components 11
User interface
- Measurement interface
frontend/src/main.jsx
Measurement API
- Measurement endpoints
backend/main.py - BMI and TDEE logic
backend/health.py
Persistence
- Measurement model
backend/models.py - Database sessions
backend/database.py - PostgreSQL
- Schema migrations
migrations/versions/001_measurements.py
Planned capabilities
- Accounts and profiles
docs/sprints/SPRINT_1.md - Workout plans
docs/sprints/SPRINT_2.md - Meals and suggestions
docs/sprints/SPRINT_3.md
Other components
- User
Connections 9
- User → Measurement interface: enters measurements
frontend/src/main.jsx - Measurement interface → Measurement endpoints: requests API
frontend/src/main.jsx - Measurement endpoints → Database sessions: gets session
backend/main.py - Measurement endpoints → Measurement model: queries and saves
backend/main.py - Measurement endpoints → BMI and TDEE logic: calculates BMI
backend/main.py - Database sessions → PostgreSQL: reads and writes
README.md - Schema migrations → PostgreSQL: versions schema
README.md - Accounts and profiles → Workout plans
- Workout plans → Meals and suggestions