On this page
Choose a line only when your recording can deliver its payoff. A reaction should introduce the demonstration, not replace it.
Play the opening. Plan the next shot.
These are source reactions paired with suggested edits. The captions describe the product footage you add; they do not describe the source creator’s personal experience.
Wait, you can group these?
Then show: Record the ungrouped items, select them, and use the real grouping control without hiding a necessary step.
End on: Hold on the grouped view long enough to read the new labels.
Where did I save that?
Then show: Show the exact search phrase typed into your app and the matching saved item appearing.
End on: Open that item so the viewer sees the correct content, not just a search result.
That’s the view I needed.
Then show: Move from the crowded starting screen to the actual focused view in your app.
End on: Pause on the completed view and use a closing instruction tied to that feature.
Start with a real product action
List three things your app can visibly do. Use actions that fit inside one short recording: finding, sorting, saving, comparing or exporting. Then choose the one with the clearest final state.
The lines below are editable examples. They are not quotes from the people in the footage or a list of tested winning ads. Change the wording to match your feature and remove any claim your demonstration cannot support.
Twelve openings and the shot each one needs
Pair a restrained expression with a small improvement and a stronger expression with a more visible reveal. The three playable reactions above show the source footage; the next shots are edit briefs for you to record in your own app. Read each line over the actual footage before deciding that the tone fits.
| Opening line | Expression | Required next shot |
|---|---|---|
| “Where did I save that?” | Curious | Search and open the correct saved item |
| “There’s a shorter way.” | Mild surprise | Show the shorter path without hiding prerequisites |
| “This list needed a cleanup.” | Puzzled | Sort or group the exact list shown |
| “Find the one I forgot.” | Concerned | Reveal a missed task through a real filter |
| “Wait, you can group these?” | Surprised | Group selected items and show the result |
| “Here’s the button I missed.” | Curious | Locate the control, then use it |
| “Keep the useful part.” | Focused | Extract or save a specific section |
| “One place for these notes.” | Relieved | Bring actual notes into one view |
| “See the difference side by side.” | Curious | Present a real comparison view |
| “The boring step, done.” | Small smile | Complete the routine operation shown |
| “Back to the thing I was doing.” | Relieved | Return to a saved state or recent item |
| “That’s the view I needed.” | Happy | Reveal the useful view and hold it |
Match the scale of the expression
A large jaw drop for a minor button placement can feel disconnected. Try a smaller expression first, then compare the whole edit. The face is only one part of the opening; crop, text and the timing of the cut can make the same source feel louder or quieter.
Avoid stacking several opening lines. If the viewer needs two separate questions before understanding the product, simplify the idea. One question followed by one readable action is a better first draft.
When the screen should open instead of a face
Not every opening needs a reaction. Some features explain themselves faster when the first frame is the product: a cluttered list, a finished view or the control itself. A human clip earns its place only when it gives the sequence meaning.
These screen-first structures work for TikTok, Reels and Shorts. They are proposed structures, not verified performance claims. Use only actions your own product can demonstrate, and compare one of them against your best reaction-led version.
| Opening structure | First shot | Next shot |
|---|---|---|
| Result first | The clean final view | The steps that create it |
| Visible problem | A cluttered list | One useful filter |
| Find the control | A highlighted area of the interface | The actual control being used |
| Question | “Where did this go?” | Search and the correct result |
| Small comparison | Two views of the same data | Why one is useful for this task |
| Routine shortcut | The repeated manual action | The shorter supported action |
| Single constraint | “Only the overdue items” | A real filtered view |
| One detail | A useful field or setting | Its effect on the result |
| Undo and recover | An item in the wrong state | The actual recovery action |
| Quiet completion | A small smile or completed task | A readable final product state |
Make the opening work without sound
Use a short line if the screen alone does not explain the problem. Let the viewer see the relevant state before moving on. A fast cut can feel energetic and still leave no time to understand what changed.
Avoid putting the entire explanation in small type. Crop to the feature, simplify the example data and remove unrelated interface panels. The words should clarify the image, not compensate for an unreadable recording.
Turn the list into a working brief
Choose three lines for the same demonstration. Keep the demo and closing instruction fixed, and write down which opening changes. If you change the expression, wording and total length together, you are comparing complete opening treatments rather than learning which single detail helped.
Check the final captions for accidental first-person testimonials. An editorial line about a button can be useful. A claim that the source creator personally saved time or money requires evidence you do not get from a generic reaction clip.
- Hook: the exact line.
- Payoff: the exact screen state.
- Expression: why it fits the size of the reveal.
- Cut point: where the demo begins.
- Check: what a viewer might wrongly infer.
Questions & answers
Can I use these exact lines?
Use or adapt these example lines where they accurately introduce your demonstration. They are starting points, not claims of tested performance.
Should I always use a shocked face?
No. Curiosity, relief and a small smile can fit everyday app actions more naturally than a dramatic expression.
Do all TikTok hooks need a face?
No. A readable product result can be a useful opening. Use a human shot when it improves the sequence.
Should I copy a trending opening?
Adapt a structure only when it fits the product action. A familiar format cannot make an unsupported promise true.
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