Your demo runs four minutes and thirty seconds. You watched it back once, felt the drag around the two-minute mark, and now you are staring at the file wondering which chunk to sacrifice. The problem is that you already recorded it, so every cut costs you a re-record or a trip into an editor you did not plan on opening.
Short answer: The best explainer video tips for hitting a short runtime all happen before you press record: pick a target length, cut features instead of footage, and rehearse the tap sequence. On iPhone, DemoScope records your screen with a face cam overlay, touch indicators, and a teleprompter so you can hit a clean single take instead of trimming later. DemoScope Pro is $19.99, one time.
How long should a mobile explainer video actually be?
Runtime should be set by where the video is going to live, not by how much you have to say. A demo destined for an App Store product page has a hard technical ceiling. A Product Hunt launch video has a social attention ceiling. A support tutorial has neither, but it does have a “how fast can I stop watching this” ceiling.
| Where the video lives | Target length | What that means in practice |
|---|---|---|
| App Store preview video | 15 to 30 seconds (Apple’s limit) | One flow, no intro, no talking head monologue |
| Product Hunt / launch demo | 60 to 90 seconds | Problem, one core flow, one differentiator |
| Twitter/X or LinkedIn demo clip | 30 to 60 seconds | Show the payoff in the first 5 seconds |
| Support or onboarding tutorial | 90 seconds per task | One task per video, not one video per feature |
| Bug report video | 20 to 45 seconds | Reproduce, narrate, stop |
Pick the number before you write the script. If you decide “90 seconds” up front, the script writes itself differently: you stop introducing yourself, you stop explaining your app’s philosophy, and you start on the second tap instead of the login screen.
Why cutting scope beats cutting footage
Most long demos are not long because of pacing. They are long because they cover three features when the viewer only needed one. Trimming footage compresses the symptom. Cutting scope removes the cause.
Try this test on your script: for every feature you mention, ask whether the viewer’s decision changes if you delete it. If someone will still download, still upgrade, or still understand the bug without that section, it goes. A 90-second video with one feature explained clearly converts better than a 4-minute tour where nothing lands.
This matters more on mobile than on desktop because there is no editing step in most iPhone recording workflows. DemoScope, for example, records your screen with a face cam overlay and exports MP4 to your camera roll, but it does not trim, cut, or crop. That sounds like a limitation until you realize what it forces: you plan the video instead of fixing it. If you want a longer read on the failure modes here, explainer video tips: why most mobile tutorials fail (and how to fix yours) covers the structural mistakes that inflate runtime.
Two workflows, and what each one costs you
There are basically two ways to end up with a short explainer video. You can record long and cut down, or you can plan short and record once.
| Record long, edit down | Plan short, record once | |
|---|---|---|
| Where the time goes | Recording, then editing passes | Scripting and one rehearsal |
| Tools needed | Recorder plus a separate video editor | One recorder |
| Typical cost | Recorder plus editor subscription, recurring | DemoScope Pro, $19.99 one-time |
| Failure mode | Frankenstein pacing, mismatched audio | Fumbled take, so you re-record |
| Best for | Multi-scene marketing pieces | App demos, tutorials, bug reports |
For a 90-second mobile demo, the second column wins on almost every axis. Re-recording a 90-second take costs 90 seconds. Editing a 4-minute take costs 40 minutes and a subscription.
What to do in the first 10 seconds
Lead with the result, not the setup. The fastest structure for a short mobile explainer:
- Seconds 0 to 3: the finished outcome on screen. Show the thing the app produces.
- Seconds 3 to 8: name the problem in one sentence, on camera.
- Seconds 8 onward: do the flow, narrating only what your fingers are doing.
Skip the “hey everyone, in this video” opener entirely. Skip the logo animation. Skip the login screen by starting the recording on an already-signed-in state.
A face cam bubble helps here specifically because it lets you deliver that one-sentence problem statement without cutting away to a separate talking-head clip. DemoScope’s camera bubble is draggable to any corner and resizable, with circle, square, vertical rectangle, and horizontal rectangle shape options, so you can park it away from your app’s UI instead of over your primary button.
Practical ways to protect a tight runtime while recording
Rehearse the taps, not the words. Run the flow twice with the app closed to muscle memory, then record. Most overruns come from hunting for a menu on camera.
Use a teleprompter for the narration. DemoScope includes a built-in teleprompter that displays your script on screen with adjustable auto-scroll speed and is only visible to you, not to the recording. Reading a 130-word script at a normal pace lands you close to 60 seconds, which is a much more reliable way to hit a runtime than improvising.
Let touch indicators replace sentences. Touch indicators show animated circles at your tap locations with a customizable color. When the viewer can see where you tapped, you do not have to say “now I’m tapping the settings icon in the top right.” That single habit tends to save 10 to 20 seconds in a short demo. For more on tightening the recording itself, see follow-up: 5 explainer video tips that actually work when recording on iphone.
Fix your environment before the clock starts. Nothing wrecks a good take faster than a notification banner, a low-battery alert, or bad lighting on your face cam that you only notice on playback. Follow-up: the recording environment setup that makes or breaks your mobile explainer video walks through the pre-record checklist.
Split, do not stretch. If your flow genuinely needs three minutes, that is two videos, not one long one. Two 90-second videos get watched. One three-minute video gets abandoned at 40 seconds.
When your demo spans more than one app
Some explainers cannot stay inside a single app. Sharing to another app, handling an OAuth redirect, or showing a Shortcuts integration all require leaving your app mid-recording. DemoScope handles this with External PiP recording, which activates a system-wide floating face cam window, sends DemoScope to the background, and records your screen across all apps using an iOS Broadcast Extension.
Two limits worth planning around: in External PiP mode, touch indicators and the teleprompter are not available (those are in-app recording features only), and your on-screen tools are limited to Camera, PiP Border, and Text overlay. So if your video needs tap dots, keep the flow inside one app. If it needs cross-app navigation, script the narration tighter because you will not have a teleprompter to lean on.
Choosing between recording modes, and between recording tools generally, is its own decision tree. The complete guide to choosing the right tutorial video app for mobile recording breaks it down by what you are actually making.
Frequently asked questions
How long should an app demo video be?
For an App Store preview, 15 to 30 seconds, which is Apple’s technical limit. For a launch or Product Hunt demo, 60 to 90 seconds. For a tutorial, aim for 90 seconds per single task and split anything longer into separate videos.
Can you make a short explainer video without a video editor?
Yes, if you plan the runtime before recording instead of trimming afterward. Write a script of roughly 130 words per minute of target runtime, rehearse the tap sequence twice, and record in one take. DemoScope on iPhone and iPad records screen plus face cam and exports MP4 to your camera roll, but it does not include editing, trimming, or cropping, so the planning step is not optional.
Does DemoScope let me trim my recording after I stop?
No. DemoScope has no video editing features: no trimming, cutting, cropping, or filters. Recordings export as MP4 (H.264) at device-native resolution straight to your camera roll. If you need a trim, you would do it in a separate app afterward.
What is the cheapest way to record an iPhone explainer video with my face on screen?
The iOS built-in screen recorder is free but has no face cam and no touch indicators. DemoScope has a free tier that records with a watermark, and DemoScope Pro removes the watermark and unlocks all features for $19.99 as a one-time purchase, not a subscription.
How do touch indicators help shorten a tutorial?
Touch indicators are animated circles that appear at your tap locations during recording, with a customizable color. They let viewers see where you tapped, so you can stop narrating your own navigation (“now tap the gear icon, top right”), which is usually where 10 to 20 seconds of a short demo leaks away.
If your explainer videos keep sprawling past the length anyone will sit through, the fix is upstream of the recording. Set the number, cut the scope to fit it, rehearse the taps, and record clean. DemoScope is worth a look if you want the face cam, touch indicators, and teleprompter in a single iPhone app without adding a subscription to the pile.