Record software demos for a small phone screen

Set up a dedicated demonstration state

Choose one action with a clear result. Prepare the starting screen so the action can begin without a tour through unrelated menus. Keep enough context for the viewer to know where they are. A close crop of a button is not helpful if no one can tell which screen contains it.

Use a demonstration account with invented records. Remove names, notifications, bookmarks, browser autofill suggestions and other information that should not appear publicly. Turn off desktop alerts before capturing. Check the account's plan and role: they affect which controls appear.

Write down the product version or recording date and the exact task. If a teammate edits the video later, this note helps them distinguish real behavior from a deliberately shortened pause. Vimeo's screen-recording guidance describes editing techniques; the recording still needs to begin with truthful source footage.

Choose a capture region by testing the smallest label

Identify the smallest text the viewer must read, such as a menu item, field label or success message. Make a brief test recording and place it in the intended vertical layout. Export it before making the full take. The final encoding and framing can reveal problems that a capture preview hides.

If the label is unreadable, reduce the amount of interface in view or enlarge the interface during capture. Check that changing browser zoom does not alter the workflow or hide required controls. Rehearse at the chosen size rather than adjusting it midway through the final take.

Avoid enlarging a low-resolution recording after the fact and assuming it gains detail. A crop can focus attention but cannot restore text that was never captured clearly. Return to the source and record again if the key evidence is missing.

Use a shot ledger for the actual action

This fictional example concerns an invented scheduling app. The task is assigning a draft to a reviewer.

The example does not claim a particular app supports this workflow. It shows how to keep a recording accountable to its purpose. If your real action includes a save button, permission prompt or confirmation dialog, record it. Do not imply it happens automatically by cutting the necessary step.

Allow a short pause after the result so the viewer can recognize it. Keep cursor movement purposeful. A fast cursor circling every panel makes the capture harder to follow and adds no evidence.

Place the recording inside the final composition

Use the real footage for the demonstration segment. The surrounding hook, captions and brand styling should explain what the viewer will see. They should not make a broader claim than the captured action supports. Prolifik's Video Hook & Demo format is the relevant creation path once that recording is ready.

Check where overlays sit. A caption that covers the selected menu item defeats the purpose of the recording. Use the existing vertical video safe-zone guide to review placement, then test the actual export in the intended app rather than relying on a universal margin rule.

If you need a horizontal recording inside a vertical frame, consult the horizontal-to-vertical guide. Decide whether a crop, stacked layout or closer recapture best preserves the task. A decorative border does not solve tiny text.

Test at ordinary viewing size

Watch the export on a phone without pinching to zoom. Check three things separately: the viewer can identify the control, follow the action, and recognize the result. A readable heading does not prove the action itself is readable.

Also watch without audio. Captions should explain any step that the cursor alone cannot communicate. Listen without looking to find narration that says “here” or “this” when a named control would be clearer. Replace ambiguous words without turning the audio into a list of every pixel.

Ask a colleague to repeat the action from the video in an appropriate test account. If they need you to explain the screen, adjust the capture or script. Record the reason for any retake so another editor does not revert to the prettier but less useful version.

Save the source and recheck before reuse

Keep the raw recording, final export and task note together. A future interface change may require a new capture even if the general advice remains correct. Record which menu names and completion states the video depends on.

Do not call footage current because it was exported recently. Export date and recording date can differ. Before reusing the piece, compare the captured controls with the live product and check that the same role can still complete the action. Publish the demonstration when the source, framing and final phone-size test agree.