Record app footage people can actually follow.

For an app demo, the recording is the proof. The viewer should be able to tell where the task starts, which action you take and what changes. A clean capture of one useful feature is a better starting point than a long tour you hope to rescue in the edit.

This guide prepares source footage for a social video. It does not promise a particular export specification, store approval or better engagement. Store preview videos have separate requirements; check the destination before making one file serve every channel.

Decide what must remain readable

Choose the question first. For example: “How do I find the next step from a client call?” The essential visual evidence might be the project name, the Call notes control, the selected note and its next-step section. Other navigation does not need equal attention.

Write the steps using the SaaS demo script worksheet. Keep a list of the labels and results that must be legible on a phone. This gives you a concrete pass/fail test for the recording.

Choose the capture route

If you are demonstrating a mobile app

Record the app on the device and in the orientation needed to understand the task. On iPhone, Apple documents screen recording through Control Center and saving the result to Photos. Some apps restrict recording. Follow the current Apple screen-recording instructions for your device.

On Android, Google documents recording through Quick Settings; availability and controls depend on the device and version. Use the Android screen-recording guide rather than assuming every phone has the same controls. Check whether the microphone or device audio is enabled before capture.

If you are demonstrating a desktop SaaS app

Record a clean app window or a carefully chosen region. Resize the window only if the app genuinely supports that layout. If a smaller viewport hides a required control, keep the authentic wide view and plan close-ups rather than presenting a broken or invented mobile interface.

For vertical output, choose between showing the whole screen, cropping to the working region or using a wide overview followed by close-ups. There is no one crop that preserves every desktop workflow. Record a short test and view it inside your intended edit before completing the session.

Run a framing test before the full take

1. Capture the starting screen, the important control and the resulting state.
2. Place the test clip in the vertical canvas you expect to use. Keep the product’s proportions intact.
3. View the export at normal phone size. Read the control name without zooming the player.
4. If it is too small, isolate the relevant region or record an additional close-up. Do not stretch the UI to fill the canvas.
5. Check the destination’s preview so its controls do not cover your essential action or labels.

A blank margin can be acceptable when it preserves legible context. Enlarging the entire capture is not automatically better: the button you need may move outside the crop. For a path across several panels, use a readable overview followed by separate focused shots, with clear continuity between them.

Prepare a safe demonstration state

Use a demo account or realistic sample records. Close unrelated tabs, hide notifications and inspect names, messages, addresses, billing details, browser suggestions and account menus. Preview the recording for accidental exposure; an editor’s blur does not protect a detail in an unblurred transition frame.

Keep the real sequence. If the result is preloaded for a second shot, make the cut clear and do not claim the elapsed time represents live processing. Do not show a sample integration as connected or a draft as published when it is not.

Record a short sequence with deliberate holds

Try this original rehearsal sequence for the fictional notes app: begin on a sample project, pause so its name can be read, open Call notes, choose one call, then hold on the next-step section. Record enough still time around each action to make an accurate edit. The exact durations depend on the controls and reading load.

Move the pointer directly and pause before a consequential click. On a phone, avoid covering the important result with unrelated gestures. If the action fails or the wrong record opens, reset the starting state and record another take. Keep the result that actually answers the viewer’s question, not just the smoothest motion.

Copy a capture worksheet

Viewer question:
Device / app version / orientation:
Safe demonstration account and sample record:
Starting screen:
Control and label that must be readable:
Action to capture:
Result to hold on:
Whole-screen or close-up plan:
Audio choice:
Sensitive details checked:
Phone-size test result:
Retake needed and why:

Review the recording before adding effects

• Starting point: can a new viewer understand which project or screen is open?
• Action: are the required control and the actual click or tap visible?
• Result: does the ending show the promised outcome long enough to inspect?
• Privacy: is every visible record, notification and menu safe to share?
• Audio: is any recorded speech intentional and clear, and is unwanted audio absent?
• Framing: do the important labels survive the intended vertical crop and phone-size export?

If any answer is no, fix the capture while the demo account is ready. A new recording may be simpler and more accurate than trying to hide the problem with animated overlays.

Turn the source clip into a short video

Keep an original copy of the recording. Then trim the sequence, add an opening that matches the task and check the final export. Follow the product-demo editing guide for that stage. The text readability guide helps when labels, narration captions and product UI compete for space.

UGC Pilot can fit into the creative and editing workflow where its current capabilities support your media. This page does not claim it records your screen or repairs an unreadable capture automatically. Generated footage may introduce a question; a genuine recording should demonstrate the software.