Apex
2026
You
A goal in your own words, photos, physio notes, how you felt
Input
Running context
One memory of you that every plan is built from
Grows with every log
Train · Eat · Friends
Sessions, meals, grocery lists and shared workouts
Output
what you give it, what it remembers, what it gives back
Why
Context
Fitness and food apps ask for a lot before they give anything back: target weights, macro splits, a full week of logging. Most people stop before the app ever knows them.
Each app also only knows a slice. The workout app doesn’t know you slept badly, and the meal planner doesn’t know you trained legs.
Intent
Apex keeps one running context of a person across training, food and recovery, and builds every plan from it.
It works with whatever you give it. A name and a goal is enough to start. Six months of logs makes it exceptional.
Role
Product, system and build, end to end.
I designed the experience, wrote the logic the AI follows and built the web app. Most of the design work was deciding what the app should ask for, what it should work out itself, and what it should never require.
Each screen answers one question: what should I do today, what should I eat, what do I need to buy, and what does it know about me.
System
Two flows, one context.
Movement is split into strength, cardio, mobility and stability. Nutrition into protein, carbohydrates, fats, vitamins and minerals, and hydration. Every log lands in the same running context.
Goals are intentions, not numbers. Nothing is required and everything helps. Training with a friend shares the session while each person keeps their own plan.
Core Screens
Eat, pantry, train and self
Status
Apex is a working web app and a personal project, built to test whether one running context can replace a stack of single-purpose fitness and food apps.
