Keep the workout name visible before and after the move. Otherwise a viewer cannot tell whether the app rescheduled the session or created a different one.
Pick the small task people can recognize
A fitness app may have workout plans, progress charts and exercise instructions. Putting all of them in one short video makes it hard to see which problem the product solves. This example chooses a single interruption: a session planned for today needs to move to another day.
The hypothetical user already has a saved workout. We do not need to explain account setup or how that workout was created. Start with the existing session and end when its new place in the schedule is clear. This is an illustrative editing case study, not a client campaign, a health claim or a report of improved adherence.
Set up the demo state before recording
Use a demo account and name the session something short, such as “Upper body”. Put it on a day that is visible without scrolling. Choose a destination day in the same calendar view if the product supports that, so the viewer can follow the change.
Record the full real flow. If moving the session requires a confirmation screen, keep that step. If the app copies rather than moves a workout, the caption must say so. Do not edit separate screens together to imply an interaction the app cannot perform.
- Use the same session title on the source and destination screens.
- Hide notifications and personal activity history.
- Check whether a reminder also changes when the session moves.
- Avoid recording a loading failure and cutting directly to an unrelated success state.
Let the before-and-after do the explaining
Violet’s reaction can introduce the interruption, but the expression does not need to carry the whole story. Use a short portion of the source clip and move to the schedule while the opening caption is still fresh. Once the calendar appears, keep the interface full-screen.
Leave the original day visible long enough to establish the starting state. Then show the control, the new day and the confirmation. A short hold on the finished calendar is more informative than another reaction at the end.
| Timing | Screen or footage | Caption |
|---|---|---|
| 0–2 seconds | Reaction opening | Plans changed. |
| 2–5 seconds | Upper body in its original slot | Today won’t work. |
| 5–9 seconds | Open the actual move control; select Thursday | Move the session. |
| 9–11 seconds | Confirm if the app requires it | Keep the plan. |
| 11–15 seconds | Same session visible on Thursday | There it is. Thursday. |
Use a caption the feature can support
The line “Move the session. Keep the plan.” describes a visible interface action. It does not promise that a person will train more often or achieve a fitness result. Keep any closing copy equally close to what the product demonstrates.
The date in the caption must match the recording. This sounds small, but a reused caption template can make an otherwise clear demo confusing. If the session moves from one week to another, include the dates rather than relying on weekday names alone. Keep the text away from the selected day and the confirmation control.
Test whether the action is understood first
Show the draft without narration to someone who has not used the app. Ask what changed and what stayed the same. The answer you want is that the saved workout moved to another day. If they think a new workout was generated, the beginning or ending needs a clearer view of the session name.
For an opening test, compare the proposed reaction-first version with a calendar-first version. Keep the interface sequence unchanged. Record which variant ran where and when, and compare available viewing and destination-click data under similar conditions. Do not treat a viewing difference as evidence that people exercised more; that would require separate product data and a suitable study.
- Can the reviewer identify the destination day?
- Can they tell the original session was preserved?
- Is the last frame held long enough to read?
- Does the destination page explain the demonstrated scheduling feature?
Keep the edit easy to update
Save the screen recording and text layers separately. Scheduling interfaces change, so replacing a product recording should not require recreating the entire composition. Keep a short note with the recording date and the app version used for the demo.
The proposed handoff includes the reaction-first cut, the calendar-first cut and a still of the final schedule. It also includes the untouched recording so a reviewer can check the sequence. The preview on this page is source footage only; no finished fitness-app campaign or measured result is presented.
Questions & answers
Why not show someone exercising?
The feature being explained is scheduling. Exercise footage would not show whether the saved session moved correctly. Add it only if it helps a separate part of the story.
Can I call this a customer success story?
No. This page is a worked example with a hypothetical app workflow. A customer success story needs an actual customer, permission and evidence for its claims.
What if moving a session changes the whole plan?
Show and explain that behavior. This sequence assumes an individual session can move; adapt the demonstration to the actual product rather than hiding the difference.
Find the opening for your next edit.
See the public samples, then unlock the library when you’re ready to work with the originals.
Explore the library