Rest timer UX: keep the next set within reach

Separate the countdown from its default.

Liftoff places a running 01:06 countdown above a Default Exercise Timer area showing 1m 30s. JEFIT keeps a 00:59 countdown near the current sets and a separate Rest Timer setting. These screens make an important distinction visible: the remaining time now is not the duration that will start after the next set.

In your design, decide whether an adjustment affects only this rest or changes the exercise default. A quick +15 action should not quietly rewrite the routine unless the product explains that rule. If it does update a future default, show the new value and offer an appropriate way to reverse the change.

Keep units understandable when multiple clocks are visible. A session elapsed timer, a set duration and a rest countdown can all use minutes and seconds. Labels, placement and emphasis should distinguish them without relying only on different colors. A person returning after a phone call should not have to remember which clock was counting down.

Make quick adjustments literal.

Zing exposes -15 sec and +15 sec around Skip Rest. Boostcamp similarly provides -15s and +15s, alongside explicitly named Pause and Skip actions. The adjustment amount is visible before the tap, so the user can predict the change without opening a duration picker.

Treat extension, reduction and replacement as different operations. Adding fifteen seconds to the remaining countdown is not the same as setting the total rest to fifteen seconds. If a control changes the total instead, label it accordingly. Check what happens when a reduction would cross zero and avoid a surprising jump into another exercise.

For rapid repeated taps, update the displayed result consistently and prevent delayed responses from making the countdown appear to move backward unexpectedly. Provide enough target separation that a person trying to extend the interval does not skip it. Precision gestures can be optional, but the common adjustment should remain a simple deliberate action.

Keep pause and skip semantically separate.

WeGLOW presents a pause control under the circular countdown and a large Skip Rest action below it. Hybrid Calisthenics shows remaining time, total rest time and a separate Skip rest button. Their arrangements illustrate how pausing time and ending the interval can remain distinct even when both are available together.

Specify the paused state before designing its icon. Does the workout session clock keep running? Can the user leave this panel and return? Does the next set wait? Those are product decisions, not answers supplied by a screenshot. The interface should display the resulting state and name the action that resumes it.

Avoid making dismissal secretly mean either pause or skip. A close icon on a timer sheet may simply reveal the set log while rest continues. If that is the contract, retain a visible route back to the active countdown. Finishing the whole workout deserves a separate label and should not share an ambiguous forward-arrow control with skipping one rest.

Show what the person is returning to.

Workouts For Men names the next exercise, set and repetition count beneath the timer. Six Pack in 30 Days combines its countdown with NEXT 2/15, a movement name and a demonstration area. The useful pattern is not the specific movement; it is retaining the next task while the user waits.

Choose the smallest next-set summary that lets someone prepare. Exercise name, set position, equipment or an instruction link may be more useful than a second motivational message. If the next item changes because the routine was edited elsewhere, reconcile that change before the timer hands the person off.

Keep the preview subordinate to the countdown without making it unreadably small. Long exercise names need wrapping rather than truncation that removes the distinguishing variation. If a demonstration can play during rest, define its audio behavior and ensure watching it does not inadvertently restart, pause or advance the workout.

Distinguish ready, running and extended states.

Gymverse shows Tap to Start with a set of duration presets and small -5/+5 adjustments. JustFit shows an active REST countdown, a +30s action and the next movement. The visual distinction between a prepared duration and a running interval is essential; large digits alone do not establish that time is actually passing.

Give each state a truthful primary action. A ready timer needs Start, a paused timer needs Resume and an active timer may emphasize an adjustment or skip. If completing a set starts rest automatically, make that transition perceptible without blocking the next useful interaction with a modal explanation.

A completion signal should not imply the next set has been logged. Returning to an exercise and recording its performance are separate events. Keep the workout record intact if a timer is skipped or extended, and let the person understand whether the next step is to begin, view instructions or record a completed set.

Build a clock contract, not just an animation.

Represent the interval using an appropriate time source and explicit ready, running, paused and finished states. Do not make the countdown depend on a rendering callback firing every second. Define what happens while the app is backgrounded, the device sleeps or the process restarts, then render the remaining value from that contract.

Coordinate in-app controls with any supported notification or lock-screen actions. Extending rest in one surface should not leave a stale completion alert in another. A denied notification permission should not erase the session or pretend an alert will arrive. Explain the available behavior without claiming that every device configuration supports the same delivery.

Keep one-off changes, exercise defaults and session preferences separate in the data model. Log timer events independently of completed sets so analytics can distinguish an intentional skip from a session abandonment. Do not interpret a longer rest as poor engagement or recommend a training duration from these interface observations.

Test the return to the next set.

Ask participants to complete a set, extend rest, pause it, leave the timer panel and return to the correct exercise. Repeat with a short remaining interval and with the phone farther from the hand. Observe wrong-control taps, difficulty finding the active clock and uncertainty about whether the next set has started.

Exercise backgrounding, interrupted audio, time changes, notifications disabled and rapid repeated extension. Verify that only one completion transition occurs. Check that the set log does not gain a duplicate entry when rest ends and that cancelling a timer does not delete performance already recorded.

For accessibility, announce state changes meaningfully rather than speaking every countdown tick by default. Give icon controls action names and include the adjustment amount in their accessible labels. Use a readable remaining-time value, sufficient target separation and an alternative to relying on a shrinking colored ring or a sound alone.

Review the between-set handoff.

Use these checks on a working build, not only on the polished reference state.

• ✓Label remaining time separately from defaults and session elapsed time.
• ✓State the amount and scope of every adjustment.
• ✓Distinguish Pause, Skip Rest and Finish Workout.
• ✓Retain the next exercise and set context.
• ✓Reconcile background and notification controls.
• ✓Check that timer completion never logs a set by accident.

Related workout design decisions

For the surrounding logging experience, compare the workout tracker design examples and keep the timer integrated with the active set rather than treating it as another app.

If rest can trigger alerts, review the notification settings examples so notification choices do not become a hidden prerequisite for using the countdown.