How to record an app demo you can put in a short video

The rule nobody thought had to be written

The first week we watched founders upload their own demos, someone uploaded two meme clips they had downloaded off the internet as their app demos. The render worked. The hook was good. It was a good hook glued to somebody else's video, and it was discarded 18 seconds after it finished.

• It has to be your product on screen. The viewer is deciding whether to go get your app, and the only evidence they get is pixels. A stock screen recording, a competitor's UI, a clip from a video you liked: none of them are a demo, they are a claim with no proof under it.

• Borrowed clips carry someone else's watermark. Instagram makes clips with another app's watermark less discoverable and TikTok keeps them off the For You feed, so the one shortcut you took is also the one thing the platforms actively push down. More on what the platforms actually penalize in the account warming guide.

Every rule below assumes you got this one right. It is first in our own product for the same reason.

The seven rules, and why each one exists

This is the checklist the app itself shows before you upload, in the same order. The order is not arbitrary: each rule below is one a real demo failed on.

1. 1

   Your own product on screen. See above. If the footage is not your app, nothing downstream can fix it.

2. 2

   Vertical 9:16. Record in portrait at the device's native resolution, and never rotate mid-take. A phone recording is 9:16 for free. A desktop capture is not, and a 16:9 frame cropped to 9:16 keeps about a third of its width, which is where your navigation and half your data live.

3. 3

   Keep 8 to 15 seconds. That is kept footage, not recorded footage. Record long, trim hard. The clip is the back half of a short video, and someone who has already read a hook will not wait through an app launching. Shorter than 8 and the action is over before a stranger has read the screen. Longer than 15 and the post cuts it anyway.

4. 4

   One feature per clip. One feature, one action, start to finish. A clip that shows three things gives a writer nothing to promise, because a hook is a specific claim and a tour supports none of them. It is also the cheap way to get variety: four features recorded as four clips are four different claims, while one 60 second walkthrough is one post. That is what makes a daily posting schedule survivable.

5. 5

   Real data, no placeholders. Lorem ipsum, Test Test, asdf, user1@test.com and an empty list all read the same way to a stranger: this product is not finished. Seed a test account with plausible names and numbers, and enough rows that the screen looks used, five to eight, not two and not two hundred. Never record signed in as yourself, because a real customer's name in your inbox is unpublishable and your users did not agree to appear in an ad.

6. 6

   End on the payoff. The last frame is the one that gets held, and often the one the whole post lands on. Get to the moment the value is visible, then stop moving for a full second before you end the recording. Do not navigate away, do not hit back, do not let the success state fade out, and never end on a spinner. Trim off the part where you reach for the stop button.

7. 7

   Notifications off, HDR off. A notification banner lands in the top third of the frame, which is exactly where a hook caption sits, and a personal message on screen makes the file unpublishable. You will not notice it, because you were watching your hands. HDR is the quiet one: HDR screen recordings tone-map unpredictably in whatever pipeline touches them next, so they can post washed out or blown out while your own phone shows you the correct version the entire time.

How to actually record vertically

Device by device, with the settings that matter. All of these produce a portrait file with no editing.

• iPhone, on device. Settings, Control Center, add Screen Recording. Swipe down from the top right corner, tap the record button, wait out the three second countdown. Long-press the button first and confirm the microphone is off. The output is portrait at native resolution, so 9:16 is free as long as you never rotate the phone.

• You cannot hide the iPhone status bar on device. No setting removes the clock or the battery from an on-device recording, and the recording indicator sits up there too. Charge past 50 percent so the battery is not a red sliver, and accept the bar. If you need a clean one, use one of the next two methods.

• iPhone through a Mac (QuickTime). Plug the phone in, open QuickTime Player, File, New Movie Recording, then pick the iPhone in the menu next to the record button. You get a full-resolution portrait capture, and Apple normalizes the status bar for device capture (the 9:41, full-battery bar you know from App Store screenshots). That behavior has moved around between OS versions, so check the top bar once in the exported file.

• iOS Simulator, for the cleanest frames. xcrun simctl status_bar booted override --time 9:41 --batteryState charged --batteryLevel 100 --cellularBars 4, then xcrun simctl io booted recordVideo demo.mov. Two caveats: the Simulator drops frames on animation-heavy screens, and camera, haptics and payments are not there. Watch the export at full speed before you trust it.

• Android, on device. Swipe down twice, tap Screen record in Quick Settings, set audio to off. Turn on Show taps first, in Developer options or in the recorder's own toggle, so a viewer can see where you pressed. Without it your UI appears to change by itself, which reads as a video edit rather than a product.

• Android over adb, for no recorder UI. adb shell screenrecord --size 1080x1920 /sdcard/demo.mp4 records with nothing on screen, capped at three minutes, then adb pull. Android also ships the Demo Mode Google uses for its own screenshots: adb shell settings put global sysui_demo_allowed 1, then broadcast com.android.systemui.demo with command enter to freeze the clock and hide the status icons, and exit when you are done.

• Web app on a Mac. Do not record the browser window. Put the app in a phone-shaped portrait viewport, around 430 by 930, with your browser's device toolbar or a narrow window, then Cmd+Shift+5, Record Selected Portion, and drag the selection to the app area only, excluding browser chrome and any DevTools ruler. On a Retina display that region records at roughly double those pixels, which is more than enough.

• Turn the pointer on. In the Cmd+Shift+5 Options menu, enable Show Mouse Pointer. It is off by default for screen recordings, and without it every click looks like the interface moving on its own.

• A wide dashboard cannot be rescued in the edit. If your product only makes sense at full desktop width, do not fight it with a crop. Record a narrow slice that stands alone, or use a format built for wide, still frames: image carousels take screenshots without a crop penalty.

Focus, debug builds, and a throwaway account

Most unusable demos are not badly shot. They are shot on a working phone with a working life on it.

• Airplane mode beats Do Not Disturb. Focus still lets time-sensitive alerts and allowed contacts through, and those are precisely the ones with a human name attached. If the flow works offline, fly the phone. If it needs the network, open the Focus, empty its allowed-people list, and turn off time-sensitive delivery.

• Your own app's popups count as notifications. A rate-us prompt, a what's-new modal, a trial-ending banner or a cookie notice landing on your payoff frame kills the take. Dismiss all of them once on the recording account before you start, not while the camera is rolling.

• Record a release build. No TestFlight badge, no DEBUG ribbon, no red version watermark, no dev menu, no localhost in the address bar. Any of them tells a viewer they are looking at something unfinished, and the address bar one is the easiest to miss on a web recording.

• Use a seeded demo account. Build one account with realistic fake data and keep its credentials next to your shot list. It saves you from re-staging screens every time, and it means you never have to decide in the moment whether a customer's email is safe to show. It is not.

• Stop the screen from dimming. Set auto-lock long, turn the brightness up, and turn on rotation lock. A screen dimming halfway through a take is the most common reason a good clip gets thrown away.

Before you hit record

Run this down. It takes about a minute and it saves the retake.

• Release build on the device. No debug banners, no dev menu, no staging URL.

• Seeded account signed in. Real-looking data on every screen you are about to touch.

• Airplane mode or an emptied Focus. In-app modals already dismissed.

• Battery over 50 percent, brightness up, auto-lock long. Rotation locked to portrait.

• HDR video off. In the camera settings too, if you are filming a screen with a second phone.

• Name your last frame out loud. If you cannot name the exact frame you will end on, you are about to record a tour.

• Start on a settled screen. Let it sit still for a beat before your first tap, so an editor can cut in anywhere.

This is the exact input Vubio takes: raw clips, no edit, no captions. The same checklist sits beside the upload box in the app, next to a prompt you paste into Claude Code, Codex or Cursor so the AI that already knows your codebase writes a shot list for your specific product.

One demo should feed weeks of posts

A clip you can reuse is worth several you cannot. Reusability is decided while you record, not later.

• Neutral start and end frames. Begin on a settled screen and end on a still one. A clip that starts mid-scroll, or with a thumb already down, can only be cut in one place.

• No text you added yourself. No captions, no arrows, no callout boxes. The post writes its own hook, and two texts on one frame make both unreadable.

• No music. Audio in the clip fights whatever the post uses, and licensed music inside your file is a rights problem you inherit on every platform you cross-post to. Hand over a silent file.

• Nothing on screen that dates it. No version numbers, no New in 2.1 badge, no seasonal theme, no expiring promo banner, no visible date in a header. A demo that survives to November is worth ten that die in September.

• Skip the zoom-and-pan recorders. Automatic zooms and cursor spotlights read as tutorial content, and they fight whatever crop or framing the post applies later. Record flat.

• Keep the original file. Archive the raw capture and never overwrite it with an export. Every re-encode costs quality, and you will want that source again the third time you use the clip.

Four checks on the finished file

Do these before the clip goes anywhere. All four take under a minute.

• Say what happened in one sentence. If you cannot, the clip shows two things or none, and no hook fixes that.

• Show it to someone who has never seen the app. Ask what it does. Their answer, in their words, is your hook.

• Scrub to the last frame. If that single frame does not sell it alone, your payoff happened earlier and that is where the clip should end.

• Watch it on a different screen. Open the export on a laptop or another phone. HDR problems and dark-mode contrast issues are invisible on the device that recorded them.

Folklore you can skip

Common advice with nothing behind it. Where it is only our opinion, we say so.

• “Screen recordings get less reach than face-to-camera.” No platform says this. What is published is about reposted clips, watermarks and engagement bait, not about capture method. See the account warming guide for what is actually written down.

• “Put the recording inside a phone mockup frame.” Our opinion, strongly held: a phone drawn inside a phone screen spends a fifth of the frame on a picture of a device the viewer is holding. It makes your UI smaller and adds nothing.

• “Record in 4K for quality.” Every platform re-encodes to roughly 1080 wide. Native device resolution is already enough, and going higher mostly slows the upload and drags in the HDR path you were avoiding.

• “Add a logo sting and a call to action to the clip.” The post supplies both, and it usually places your demo in the middle rather than at the start, so a logo intro lands nowhere.

• “Hide your UI so competitors cannot copy it.” If ten seconds of screen is your moat, it was not a moat. Anyone serious already signed up for your trial.

• “Perfect the recording, then post.” The tenth take is not measurably better than the second, and neither is worth a week. Record three clips, post, and let the numbers tell you which feature to shoot next.

Questions we get

• How long should an app demo video be? 8 to 15 seconds of usable footage per clip. Record for as long as you need and trim down. That range exists because a demo is the back half of a short video: the opening seconds belong to a hook, and a viewer who has already read a claim will not sit through a menu opening. Under 8 seconds a stranger has not parsed your screen yet. Over 15 the post gets cut anyway, and then something other than you picks which 10 seconds survive.

• How do I record a vertical demo of a web app? Do not record the browser window. Resize the app to a phone-shaped portrait viewport, roughly 430 by 930, using your browser's device toolbar or just a narrow window, then record only that region with Cmd+Shift+5 on a Mac or a region recorder on Windows. Cropping a normal 1920 by 1080 capture to 9:16 keeps about 608 pixels of width, under a third of the frame, so the nav, the sidebar and most of any table are gone and the text that survives is too small to read on a phone.

• Should I add captions or music to my demo clip? No. The post that uses the clip adds its own hook text, caption and audio, and two layers of text on one frame fight each other. Baked-in captions also date the clip, so a demo that could have been posted for months becomes single use. A silent clip with no overlay is the most reusable file you can hand an editor, human or otherwise.

• How many demo clips do I need before I start posting? Three is enough to start, one per feature. Volume comes from the writing, not from the footage: the same clip can front many different posts because the hook, the angle and the framing change every time. Recording one clip per feature is also how you get variety cheaply, since four features shot as four clips give you four separate claims to make.

• What if my app is not visually impressive? Find the input-to-output moment: something the user types, uploads or taps, followed by the thing your product produces. Before-and-after reveals carry a clip even when the UI is plain. If genuinely nothing changes on screen, the demo is telling you something true, and the honest move is to use a format that does not depend on footage, like an image carousel or a text post.