Fitness Hub
Unified fitness data platform that consolidates WHOOP, Hevy, and MyFitnessPal into one operational dashboard.
What I built
Built a personal health and fitness data hub that unifies recovery, sleep, strain, workouts, nutrition, hydration, and weight into one system. Instead of treating each provider as a separate app, the project centralizes WHOOP, Hevy, and MyFitnessPal data so patterns across training and recovery can be understood in a single dashboard.
Challenges
The main challenge was dealing with uneven integration surfaces across providers. WHOOP used OAuth and polling-friendly sync patterns, Hevy relied on API-key access, and MyFitnessPal required an unofficial personal-use bridge. I had to design around those constraints so the product stayed reliable without pretending the APIs were cleaner than they actually were.
Architecture
The app is built with FastAPI, SQLAlchemy, and Alembic, with APScheduler handling local automation and Jinja templates powering the dashboard. It runs locally on SQLite for quick setup, then promotes to hosted Postgres for deployment. Hosted WHOOP and Hevy syncs are triggered through GitHub Actions, while MyFitnessPal stays on a local bridge workflow, giving the system a practical hybrid sync model.
Results
Fitness Hub shows my backend and systems-integration side more directly than the rest of the portfolio. It combines API design, data normalization, scheduling, deployment planning, and test coverage into a single product, and it turns fragmented wellness data into something much more operational and usable.