TODAY'S WORKOUT
Upper A
7 exercises · Hypertrophy
Training, health, and the signal between them
Train with context.
Today puts the next useful action first: run the plan, log cleanly, then learn from training history without pretending every estimate is a measurement.
iPhone + Apple WatchHealthKit on-deviceOptional coach sync
9:41● ◔
TuesdayUpper A is ready.
Training pulse
7 days4sessions
31hard sets
8regions
Chest
7.1
Back
6.6
Delts
5.2
Arms
4.4
Estimated set exposure—not activation, recovery, or growth.
A tighter loop
Plan. Log. Learn.
No dashboard maze. The app changes emphasis depending on what you are doing now.
See the next move
Your active workout comes first. Exercise order, targets, and recent performance stay close to the set you are doing.
Capture the work
Fast set entry, drag-to-reorder exercises, and persistent active sessions keep logging out of the way.
Adjust with evidence
Reps, load, estimated regional exposure, sleep context, and history support a decision without manufacturing certainty.
Evidence, with boundaries
Useful claims deserve visible limits.
Every training principle is labeled by confidence, connected to peer-reviewed research, and paired with what the app can—and cannot—infer.
Weekly hard-set volume is a useful programming lever
More weekly resistance-training volume generally produces more hypertrophy, but returns diminish and the best dose varies by muscle and lifter.
The split is a delivery system, not the growth mechanism
Full-body and split routines produce similar strength and hypertrophy when weekly volume is equated. Frequency mainly helps distribute useful work and fatigue.
Hypertrophy is possible across a broad loading range
Muscle growth can occur with low, moderate, and high loads when sets are sufficiently effortful. Moderate rep ranges are often the most practical, not uniquely anabolic.
Private by default
Your health data stays close.
HealthKit reads and workout history stay on iPhone by default. Coach sync is optional, encrypted, and explicitly connected.
See the exact data boundaries →