UX LEGENDARY
STUDY · APP · CONSUMER · 2026

Tempo A fitness companion that builds habits without guilt mechanics.

TEMPO · HERO
SESSION · TEMPO RUN
24:18
4.1 km · avg 5:52 /km
AT A GLANCE

Problem, approach, outcome.

PLACEHOLDER · REPRESENTATIVE FIGURES
PROBLEM

Fitness apps kept users honest with guilt, and honest users kept quitting.

APPROACH

Forgiving streaks, ranged weekly targets, thumb-zone flows, and a coach voice that rewards effort with specificity.

OUTCOME

30-day retention climbed and average sessions per week held steady beyond the usual month-two cliff.

+38%
30-day retention
vs. streak-and-shame baseline
4.2
Sessions per week
sustained past month two
−67%
Post-notification uninstalls
RATIONALE

Most fitness apps borrow their motivational model from casino UX. Streaks, rings, notifications timed to loss aversion, red numbers when you skip, subtle shame when you open the app after two days off. The metric goes up; the relationship with the product goes down. Users quit not because they stopped working out — they quit because the app made working out feel like a job with a hostile boss.

Tempo is a study in habit design without guilt mechanics. Streaks exist, but they forgive. Missing a day compresses the streak counter instead of breaking it; the user sees "12 days, one rest" instead of "0." Weekly targets are ranges, not points, so a good week is a shape you filled, not a threshold you crossed. Notifications are quiet, contextual, and expire — if you didn't see the 6am reminder, Tempo doesn't send it again at 9pm to guilt you.

Every session flow is designed for one thumb, one hand, at whatever elevation the phone happens to be. Buttons stay in the lower third of the screen. Progress is haptic, not modal. The session-end screen is short: what you did, one thing to notice, one thing to try next time, done. There are no achievement pop-ups, no confetti, no upsells wedged between you and the water bottle.

The product's tone is coach, not scoreboard. Language is warm and specific ("nice tempo on the last mile") rather than metricized ("+3% pace vs. last week"). The design bet is that a user who feels good in the app opens it more; a user who feels judged looks for a reason to close it. Retention curves in early testing suggest the bet is right.

DETAIL 01 — SESSION FLOW, THUMB-ZONE PRIMARY
DETAIL 01 — SESSION FLOW, THUMB-ZONE PRIMARY
SESSION · TEMPO RUN
24:18
4.1 km · avg 5:52 /km
DETAIL 02 — STREAK CARD, FORGIVING
DETAIL 02 — STREAK CARD, FORGIVING
YOUR STREAK
12
days · one rest

Rest day compressed the streak — nice recovery on Wednesday.

DETAIL 03 — WEEK VIEW, RANGES NOT POINTS
DETAIL 03 — WEEK VIEW, RANGES NOT POINTS
THIS WEEK · TARGET 3–5H
M
T
W
T
F
S
S
3h 45m so far — within target.
DESIGN DECISIONS
01

Forgiving streaks.

Missed days compress instead of breaking. The streak is a habit, not a debt.

02

Thumb-zone by default.

Every primary action sits in the lower third, tested at seated, standing, and mid-workout postures.

03

Coach, not scoreboard.

Language rewards effort with specificity, not percentages. Warmth is a retention feature.

NEXT STUDY

HarborSignup to first value in four minutes.

View Harbor

Want this standard on your product?