The math of mid-workout logging

A normal hypertrophy session is 5–6 exercises, 3–4 sets each — call it 20 sets. Rest between sets runs 60–180 seconds, and that rest window is the only time you’ll ever log anything. Nobody logs after the workout; if you tell yourself you will, you won’t.

So the entire UX budget of a workout tracker is: 20 interruptions, each a few seconds long, performed with sweaty hands while your heart rate is coming down. If logging one set takes 15 seconds of menu-digging, that’s 5 minutes per session spent fighting an app. Three sessions a week, 52 weeks — 13 hours a year of pure friction. People don’t consciously calculate this. They just quietly stop logging around week three.

Paper fails differently

Worth being honest here: paper is fast. A notebook and a pen beat most apps at raw entry speed. Paper logs die for a different reason — you can’t ask paper anything. What did I bench three Tuesdays ago? Is my weekly back volume trending down? A paper log answers with 20 minutes of page-flipping, so nobody asks, so the log becomes a ritual instead of a tool.

Apps have the opposite problem. They’re great at answering questions and terrible at the 20 interruptions. The tracker that wins is the one that fixes entry without giving up analysis.

Where the taps actually go

The typical flow in a logging app: open the exercise, tap “add set,” tap the weight field, type 3–4 digits on a numeric keyboard, tap the reps field, type again, tap save. Call it eight interactions per set.

Almost all of that is waste, because of one boring fact about strength training: you almost always lift what you lifted last time, give or take 2.5 kg or one rep. The fields should never start empty.

What two taps looks like

In Repsheet, when you add an exercise you’ve done before, its sets open already filled with the weight and reps from your last session. If nothing changed, logging a set is a single tap: tick it complete, done. No keyboard, no menus — the number you need to beat is already sitting in the field.

Beat last session by a rep, or add 2.5 kg? Tap the field, change the one digit, tick complete — two taps. That’s the ceiling for a normal set, not the floor; and when you do need another set, adding one or copying the last set forward is a tap each.

The required path stays minimal

The core loop asks for nothing you don’t need: prefilled fields you accept with one tap. Everything past that is there when you want it and skippable when you don’t — override the weight or reps, add another set, copy the last one forward. This is a design rule, not an accident: every required field is a tax on all 20 sets, so the required path is kept as close to a single tap as it can be, and the extras stay out of the way of the sets that don’t need them.

A log that’s 95% complete because it’s effortless is worth more than a perfect log you abandoned in March. Completeness is what makes the analysis side — progressive overload without spreadsheets, the body heatmap, personal records — actually trustworthy.

What one skipped session costs

Friction compounds in a nasty way. Skip logging one session and next time the prefill for those exercises is stale — it suggests numbers from two weeks ago. You override them from memory, memory is wrong more often than you’d like, and now the log disagrees with reality. Trust decays, and an untrusted log gets abandoned fast. This is why entry friction isn’t a comfort feature; it’s the thing the entire product stands on.

Honest limits

Two-tap logging works when your training repeats structure — same exercises recurring week to week, which is how most effective programs work anyway. The first time you do a new exercise there’s nothing to prefill, and you type weight and reps like in any other app. And loading the bar is still on you — Repsheet records the weight you lifted, it doesn’t do the plate math for you.

One more limit: no app fixes not showing up. Friction removal only converts intent into records — the intent is still on you.

Try the claim

Repsheet is free — no premium tier, the whole app is the free tier — and runs in the browser as an offline PWA, so testing the two-tap claim costs nothing: log one real session at app.repsheet.kirillin.tech. If an unchanged set takes more than one tap — or a changed one more than two — we’ve broken something.