A mobile app gesture is easy to perform and surprisingly hard to show. In a recording, a thumb may cover the control, a swipe may happen before the viewer knows where to look, and the resulting state may disappear in the next cut. Plan three separate moments: the starting screen, the gesture and the result.
This guide concerns the storyboard and the source recording. Prolifik's Video Hook & Demo can use an owned demonstration clip after you prepare it; it does not create or infer a real gesture that the recording never shows.
Choose one task, not a tour of every gesture
Imagine a fictional team-notes app called Pinboard. A user swipes a task card to assign a reviewer. The marketing team's short video should answer one question: what happens to that card after the swipe?
The viewer needs to see the card before the gesture, the direction of the swipe and the new reviewer state. They do not need the full settings menu, account creation or every possible card action. If the app uses different gestures on iOS and Android, record the actual platform you will name in the video. Do not splice one platform's start with another platform's result.
Apple's Human Interface Guidelines treats gestures as interactions with on-screen content. That is useful source context, but your app's actual implemented behavior is the authority for this demo. A generic animation of a swipe is not proof that Pinboard supports it.
A four-shot storyboard for one real action
Use a short shot list before recording:
| Shot | What the viewer must see | Review check |
|---|---|---|
| Starting state | The task card and the current reviewer state | The card is readable at phone size. |
| Gesture setup | A fingertip or restrained touch cue near the correct card | The cue does not cover the label that matters. |
| Action | The real swipe at a pace the capture can show | Direction and target are unambiguous. |
| Result | The new reviewer or confirmation state | It is the state produced by that action, not a separate mockup. |
The first shot can be brief, but it cannot be skipped when the result has no context. If the product's result is an inline update, hold it long enough to read. If it appears in another panel, show the transition rather than cutting straight to a screen that looks unrelated.
For Pinboard, a quiet on-screen line such as “Assign a reviewer from the task card” names the task. A later line can describe the observed result. Do not write “one swipe automates the whole review process” unless the app really does that. The demo should make a modest claim it can support.
Record the screen so the motion survives the crop
Capture a clean device session with a sample account you are allowed to show. Hide personal notifications and unrelated apps before recording. Disable or replace identifying data in the task list. A real gesture should still be performed on the real app, rather than compositing a finger over a static screenshot.
Keep enough space around the card that a vertical crop does not remove the start of the swipe. If the gesture begins at the edge of the screen, test the crop before filming a long take. The mobile-safe framing guide covers general dimensions; this storyboard concerns the precise touch target and state change.
Avoid assuming that a large cursor or touch halo fixes every visibility problem. The touch cue belongs beside the action, not on top of the new reviewer label. If the capture device does not show touches, you can add a restrained editorial indicator later, but keep it synchronized with the genuine recorded movement. Do not let the indicator suggest an extra tap the user never made.
Edit for comprehension without changing behavior
Trim waiting time before the task card appears, but do not remove a required step. A quick cut can make two taps look like one swipe, especially if the UI animates between states. Watch the edit without narration and write down what action it appears to show.
If you need a freeze frame to explain the result, hold a real completed frame. Do not freeze a loading indicator and call it completion. The freeze-frame guide handles that editing choice in detail. Here the storyboard should reserve a result shot even if no hold effect is used.
Show the same card identity across shots. A different project name, card color or reviewer avatar after the cut may imply that the footage comes from two examples. If you must use separate takes, add a truthful transition and do not present them as one uninterrupted interaction.
Check the final source before making a branded short
Play the source at normal speed on a phone. Ask someone unfamiliar with Pinboard to point to the touch target, name the action and identify the resulting change. That is a comprehension check, not a performance claim. If they cannot, repair the recording or storyboard before generating variations.
The Video Hook & Demo format can frame an approved product clip with a hook. It requires the team's genuine supplied footage. Its current workflow replaces the uploaded clip's original audio with music or silence, so a gesture that depends on spoken explanation needs clear visual copy or another output path. Review the actual returned video and its caption before publication.
Keep the source recording, platform/version note and approved claim together. The next app update may move the gesture or change the result label; the team should know which short needs another capture.
Build a short around the real app gesture
Use an approved recording that shows the action and result before adding a hook.
Explore Video Hook & DemoFacts checked 2026-11-02. Worked examples are illustrative unless a real source is identified.
- Apple: gestures Checked 2026-11-02
- Adobe: full motion recording fmr .html Checked 2026-11-02
- Prolifik: video hook demo Checked 2026-11-02