Feature video
Show the feature working in the actual product. Capture the interface first, then build the video around the clearest user action and resulting state.
Decide what the viewer must see
Write one sentence for the feature and one for the proof: “The user does X; the product visibly does Y.” Choose a short task that reaches that result without relying on narration. If the user supplied a particular feature or flow, keep it central.
Use the product's real colors, typography, and UI. A simple browser or device frame can add context. Avoid decorative captions over controls the viewer needs to read.
Capture the real interaction
- Inspect the working app and identify the starting state, user action, and final state.
- Set a suitable capture size and clear disposable test data. Never expose private accounts, keys, messages, or customer data in footage.
- Capture the real browser, simulator, or screen. Use a pointer or touch indicator only when it clarifies the action.
- Record a little time before and after the action so the cut has room to breathe.
For a web app, use the browser or recording tools available in the environment. For a mobile app, use a simulator or device capture. If only a supplied recording is available, edit that recording and state any limits in what it proves.
When animation timing matters, preserve the app's actual entrance, hover, and transition. Check the capture for dropped or repeated frames. Heavy scenes may need a deterministic frame-by-frame capture, if the project supports one.
Edit the story
- Start on the useful state or the action that leads to it.
- Cut waiting, loading, and setup only when removing them does not misrepresent the experience.
- Keep one visual focus at a time. A slow camera move or crop can guide attention, but never cut off the control, label, or outcome.
- Use short on-screen words only when the UI alone cannot explain the result.
- End on the completed state long enough to read it.
Choose sound deliberately. A silent UI clip can work well in a feed; narration or music should add information or rhythm. Use licensed audio only.
Formats and verification
Render the formats requested by the user, commonly 16:9, 4:5, 9:16, or 1:1. Reframe each one against the real UI instead of relying on automatic center cropping. Make a poster for each format from a frame that shows the feature clearly.
Watch every final export. Check text legibility, pointer placement, transition timing, sound, and the final outcome. Confirm the files decode and report the format, duration, and any limitation in the capture. Publishing to an external service is a separate step that follows the user's instructions.