BodyTrack

PROBLEM

An InBody scan hands you a printout and no history. BodyTrack ingests each scan as a record — including segmental analysis — so weight, muscle mass, body fat, visceral fat, and BMR become trends you can actually read, instead of a stack of paper you compare by eye.

WHAT'S IN IT

• +JWT auth with user profiles, and full CRUD over InBody records including segmental analysis.
• +Interactive Recharts trends for weight, muscle, fat, score, visceral fat, and BMR.
• +Side-by-side comparison of any two scans.
• +AI-generated reading of what changed between scans and what it implies.
• +Separate development and production Docker Compose orchestration, fronted by Nginx.

ROLE

Solo builder — Django REST backend, React frontend, analytics layer, and the Docker/Nginx deployment setup.

NOTABLE DECISION

Split analytics into its own Django app rather than hanging chart endpoints off the records app. Storing a scan and interpreting a scan change for different reasons and at different rates, and keeping that seam explicit meant adding new derived metrics never involved touching the ingest path.