Exercise swaps: show what changes in the plan
Ten recorded replacement screens show how workout apps present the current exercise, alternatives, equipment and the scope of a swap.
Exercise substitution UX should identify the movement being replaced, offer understandable alternatives and explain where the change applies. A person may want to adapt one workout to available equipment without rewriting the whole program. The replacement picker needs to preserve that distinction before any confirmation.
A useful replacement screen is a comparison surface, not a second exercise catalogue. Keep the current movement visible, describe the candidate sufficiently to distinguish it and retain the person’s position in the session. Search and filters can broaden the choices, but they should not remove the reason the picker was opened.
These recordings show interface labels and selection controls. They do not establish that two movements are medically appropriate substitutes, equivalent in training effect or suitable for an injury. Treat recommendation labels as product copy and work with qualified domain expertise when defining the actual substitution logic.
Explain whether the change is for today or the program.
Pump Club exposes separate SWAP FOR ENTIRE PROGRAM and SWAP FOR THIS WORKOUT actions after an alternative is selected. SmartGym states that logging an alternate exercise applies only to the particular workout and explains an effect on its trainer suggestions. Both make scope part of the decision instead of leaving it implicit.
Choose a safe, explicit scope for your own product. If the common task is adapting today’s session, do not silently apply the choice to every future workout. If a persistent preference is supported, make its wording and confirmation different enough that the person can predict what will change next week.
After confirmation, show the substitute in the relevant routine position and retain an understandable route back to the original. The recording of a scope button is not proof that a backend update propagates correctly. Test the current session, the saved plan and the next generated workout as separate outputs.


Keep the current movement as the reference.
Befit divides its replacement view into CURRENT and RECOMMENDED sections. MyFitCoach shows the current Goblet Squats card above a Replace with list, including equipment and a Best sorting label. The current item gives the alternatives meaning and reduces the need to remember a long movement name from the previous screen.
Keep enough identifying detail to distinguish variants. One-arm, seated, incline and left/right qualifiers are not decorative copy. A thumbnail can support recognition, but the name and relevant equipment should remain readable when images are unavailable or when a screen reader is used.
Do not let the current item look like a candidate already selected for replacement. Separate current, highlighted and committed states. If the list includes the original exercise, make returning to it intelligible rather than presenting a circular swap as a new recommendation. A successful selection should be visible in the resulting workout, not only in a disappearing sheet.


Make constraints inspectable.
Gymverse marks some alternatives with Missing Equipment. Zing offers ways to browse All Exercises, By Muscle Group and By Equipment beneath a current-and-replacement comparison. These references show two ways to keep a practical constraint close to the selection rather than forcing someone to discover it after the swap.
If equipment is a filter, make its active state visible and easy to revise. A person in a different gym may need to change the available set temporarily. Do not rewrite a permanent profile merely because they explore an equipment filter during one session. Explain whether unavailable candidates can still be inspected or selected.
Use plain constraint language without implying a medical guarantee. A matching muscle label or shared equipment category does not by itself prove functional equivalence. If the product uses a recommendation score, give users enough context to understand the criterion without dressing an unexplained ranking as universal suitability.


Separate learning about a candidate from applying it.
Evlo places a current-exercise video above alternatives with individual swap and favorite controls. LADDER distinguishes Current, Coach Recommendation and Similar Movements, with video thumbnails and swap controls. The useful separation is between inspecting a movement and changing the active plan.
Define the tap targets clearly. A row tap might open instructions while a labeled Replace button commits the choice. If tapping the row applies immediately, do not also style the same row as a video preview. Separate favorite actions so a person collecting ideas does not accidentally replace the exercise mid-session.
Keep playback behavior compatible with the active workout. A preview should not lose a running timer or erase partially entered performance. If the screen needs a larger demonstration, preserve the selected candidate when returning. Explain any required reset of set targets before it occurs rather than surprising the user after the preview closes.


Make selection and commitment distinct when needed.
Gym WP offers Similar exercises and Equipment paths within a replace-exercise grid, alongside Search and Create. Alpha Progression shows a candidate list and an explicit Replace action at the bottom. These interfaces highlight a design decision: browsing can remain reversible until a clearly named commitment.
An explicit confirmation is useful when scope, logged sets or prescribed values may change. Keep the chosen exercise visible near the action, and explain any values that cannot transfer. Do not carry a previous weight into an unrelated movement merely because both exercises have a numeric weight field.
Custom exercise creation is a separate path from selecting a suggested substitute. If the person creates an item, return it to the replacement context with the same session position and scope. Avoid sending them to a general library and asking them to reconstruct the task. Cancellation should return to the original workout without an unexplained partial swap.


Preserve the session while changing one movement.
Represent a planned exercise, a performed alternative and a persistent program change as separate concepts where the product requires them. Store stable exercise identities rather than comparing display names. Define what happens to uncompleted targets, completed sets, notes, rest preferences and historical comparisons before designing the success state.
Handle a candidate that becomes unavailable while the picker is open. Keep the original exercise until the replacement is confirmed successfully, and prevent a double submission from inserting it twice. If offline editing is supported, show the pending state and reconcile it without quietly reverting to the original when connectivity returns.
Provide an appropriate recovery path for a mistaken swap. Restoring the original should not discard sets already performed without an explicit explanation. When a swap affects future recommendations, distinguish a user’s choice from the algorithm’s next suggestion. The interface should help people understand the scope rather than making them reverse-engineer program behavior.
Test the swap and its scope.
Ask someone to replace a movement because a piece of equipment is unavailable, preview two alternatives and apply one to today only. Then inspect the next scheduled workout and the saved program. The key question is whether the result matches their scope choice, not whether the first candidate looked attractive.
Repeat with an exercise that already has a completed set, a unilateral movement, a custom item and a long translated name. Check cancellation from a preview, interrupted saving and a filter that returns no results. Keep those failures distinct from a claim that an exercise is unsuitable or safe; that requires a separate domain assessment.
For accessibility, expose current and selected states in text and programmatic labels, not only card color. Provide names for swap icons and make nested preview controls separately reachable. Measure incorrect-scope changes, immediate reversals, lost set data and failed recovery. A higher swap rate alone does not demonstrate a better workout experience.
Review the replacement contract.
Use these checks on a working build, not only on the polished reference state.
- Keep the current movement and session position visible.
- Distinguish a temporary alternative from a program-wide change.
- Expose equipment constraints without implying medical suitability.
- Separate preview, favorite and apply actions.
- Explain which targets and logged sets survive.
- Verify the next scheduled workout after each scope choice.
Questions and answers
Questions worth resolving before shipping
Should a swap change every future workout?
Only when the person explicitly chooses that scope and the product supports it. A temporary equipment problem is not automatically a permanent preference. Name today-only and program-wide actions separately, then verify their different results.
Can we copy set targets to the substitute?
Define this with the product’s training model and appropriate domain expertise. Similar-looking fields do not establish equivalent loads or repetitions. Explain any retained, recalculated or cleared targets so the person can review them before continuing.
Does a recommended alternative mean it is safe for an injury?
No. The examples show recommendation labels and interaction patterns, not clinical suitability. Do not turn equipment or muscle-group matching into a medical promise. Keep the UI analysis separate from decisions requiring qualified professional judgment.
2,805 apps in the top charts.Ask them anything.
Compare the original movement, replacement picker and updated workout in context. ScreensDesign Pro gives you real product flows to inform a more predictable fitness app.