You get four sentences into a demo script, reach the part where you have to open a settings menu, and the script keeps scrolling while your thumb is still hunting for the right toggle. By the time you find it, the teleprompter is two lines ahead and you’re reading a sentence about a screen you haven’t opened yet. So you stop, restart, and this time you read faster, which is worse.
Short answer: A teleprompter workflow for iPhone demos works when you write the script around your taps, not your sentences. In DemoScope, an iOS screen recording app, the built-in teleprompter overlays your script during in-app recording and is visible only to you, not in the export. Set scroll speed to your slowest on-screen action, then break the script at every navigation step.
The drift problem is a pacing problem, not a reading problem
Most advice about mobile teleprompters is about sounding natural. That matters, and there’s a whole separate discussion in mastering the teleprompter workflow: how to sound natural while recording on your iPhone. But sounding natural assumes you’re only talking. In an app demo you’re doing two jobs at once: narrating and driving the interface.
The script scrolls at a constant speed. Your hands do not move at a constant speed. Typing an email address into a form takes eight seconds. Tapping a tab bar icon takes half a second. A single fixed scroll rate will always be too fast for one and too slow for the other, and the gap compounds over a two-minute demo until you’re improvising or restarting.
The fix is to stop treating the script as prose and start treating it as a sequence of timed blocks that match what your thumb is doing.
Write the script in beats
A beat is one spoken line plus one on-screen action. Here’s the format I use before every recording:
- List the taps first, in order. Open app, tap Projects, tap New, type name, tap Save. Five actions. Write them as a bare list before you write a single word of narration.
- Assign one sentence per action. Not two. One. If an action genuinely needs two sentences of explanation, it’s a slow action, and you’re going to pad it in step 4.
- Insert a blank line between every beat. Blank lines are your visual cue in the scroll. When a gap comes up the screen, you know the next tap is coming.
- Pad slow actions with filler you actually mean. Typing takes time, so the typing beat gets a sentence you can say while your thumb is busy: “I’ll call this one Onboarding Flow, and the name is just for you, it doesn’t show up anywhere public.”
- Cut anything you can’t say while tapping. If a line requires you to look at the screen to think, it belongs in the intro or the outro, not in the middle of a navigation sequence.
A ninety-second demo usually lands at eight to twelve beats. If you have twenty, the demo is two demos.
Set scroll speed against your slowest beat, not your average
Direct answer: set the teleprompter scroll speed slow enough for your single slowest on-screen action, then talk to fill the extra room on the fast beats.
This is the opposite of what feels right. Your instinct is to average it out so the script tracks your normal pace. But being ahead of the script is recoverable, you just pause, breathe, and let it catch up, which reads as a natural beat in the audio. Being behind the script is not recoverable. You start rushing, your voice pitches up, and the take is gone.
In DemoScope the teleprompter auto-scrolls at an adjustable speed and only you see it, so nothing about a slow scroll leaks into the exported MP4. Do one silent rehearsal pass: run the demo with the script scrolling and your mouth closed, just tapping. If the script reaches the end before your thumb does, slow it down and rehearse again. That single pass saves more retakes than anything else in the workflow.
For scripts loaded with API names, version numbers, and error strings, the pacing math gets stricter, and there are specific tactics for it in advanced teleprompter workflow tips: handling technical demo scripts on iPhone.
Where the teleprompter is actually available
This is the part that catches people out. DemoScope has two recording modes, and the teleprompter exists in only one of them.
| Capability | DemoScope in-app recording | DemoScope External PiP mode | iOS built-in recorder |
|---|---|---|---|
| Teleprompter overlay | Yes, auto-scrolling, not recorded | No | No |
| Touch indicators | Yes, customizable color | No | No |
| Face cam overlay | Yes, draggable and resizable | Yes, floating system-wide | No |
| Records other apps | No | Yes, across all apps | Yes |
| Tools available | Camera, teleprompter, touch indicators, text | Camera, PiP border, text on screen | None |
| Cost | $19.99 one-time for Pro (watermark-free) | $19.99 one-time for Pro | Free, built into iOS |
External PiP mode uses an iOS Broadcast Extension to capture at the system level, which is why it can record any app on your phone with a floating face cam. That same system-level capture is why the teleprompter and touch indicators can’t ride along: DemoScope is in the background, so it has no surface to draw a private overlay on.
Practical consequence: if your demo has to cross app boundaries (showing a share sheet landing in Messages, or a deep link from Safari), you’re recording in External PiP mode and you’re doing it from memory. Plan for that by shortening the cross-app segment to three or four sentences you can hold in your head, and recording your longer narrated sections in-app where the teleprompter is available.
The two-pass structure for mixed demos
Here’s the pattern I’ve settled on for demos that need both modes. It’s opinionated and it costs you an extra recording session, but it beats memorizing ninety seconds of script.
Record the narration-heavy portion in-app with the teleprompter running and touch indicators on, since that’s where most of the explaining happens and where viewers most need to see what you’re tapping. Then record the cross-app portion separately in External PiP mode with just the face cam and a short text overlay for context. Two clips, two camera-roll files, each one clean.
The trade-off, stated plainly: DemoScope has no video editing, no trimming, and no cutting, so joining those two clips happens elsewhere or not at all. If you need one continuous file and you’re not going to touch a separate editor, pick one mode and script to its limits rather than splitting.
When to skip the teleprompter
The teleprompter is the wrong tool in three situations, and using it anyway produces worse video than going without.
- Demos under twenty seconds. Reading a single App Store preview line off a scrolling overlay adds eye movement for no benefit. Memorize it.
- Bug reports. You’re describing something you just found. Talk through it live, keep touch indicators on so the engineer can see exactly what you tapped, and don’t script a discovery.
- Any take where you already know the material cold. If you’ve demoed this feature nine times this month, the script will slow you down and add that faint read-aloud cadence to your voice.
There’s a broader argument about over-scripting in teleprompter workflow: why most creators get mobile script recording wrong, and the short version is that the teleprompter is a pacing tool more than a memory tool.
A pre-record checklist that prevents retakes
Run this before you hit record. It takes ninety seconds and it kills most of the reasons a take dies.
- Script pasted into the teleprompter and scroll speed set from a silent rehearsal pass
- Face cam bubble moved to the corner your script doesn’t need (usually top left if your taps are bottom right)
- Camera shape picked and locked: circle, square, vertical rectangle, or horizontal rectangle
- Touch indicator color set to something that contrasts with your app’s primary UI color
- Do Not Disturb on, because a banner notification ends a take instantly
- Enough free storage for a device-native resolution MP4, which is larger than people expect
- App in a known starting state, logged in, with test data already seeded
If you want the full version of this as a repeatable system rather than a one-off list, how to build an efficient teleprompter workflow for mobile recording in 2026 covers the setup side in more depth.
The thing that finally made scripted demos work for me was accepting that the script serves the taps, not the other way around. Write the actions first, one sentence each, scroll slow, and let the silence sit where your thumb is working. DemoScope Pro is a $19.99 one-time purchase with the teleprompter, touch indicators, and watermark-free MP4 export included, and the free tier is enough to test whether a beat-based script actually fixes your pacing before you pay for anything.
Frequently Asked Questions
Does the teleprompter show up in the recorded video?
No. The DemoScope teleprompter overlay is visible only to you while recording and does not appear in the exported MP4. Viewers see your app and your face cam bubble, not your script.
Can I use a teleprompter while recording other apps on my iPhone?
No. The DemoScope teleprompter only works in in-app recording mode. External PiP mode, which records any app on your phone with a floating face cam, is limited to Camera, PiP Border, and Text on screen because iOS Broadcast Extension recording happens at the system level with DemoScope in the background. For cross-app demos, script short segments you can deliver from memory.
What scroll speed should I use for an app demo?
Set it to match your slowest on-screen action, not your average talking pace. Do one silent rehearsal where you tap through the whole demo without speaking and watch whether the script finishes first. If it does, slow the scroll down and rehearse again.
How long should a scripted iPhone demo script be?
Aim for eight to twelve beats for a ninety-second demo, where one beat is one spoken sentence plus one on-screen action. If your action list runs past roughly twenty steps, split it into two separate recordings rather than one long take.
Can I edit the recording afterward if I flub a line?
Not inside DemoScope. DemoScope has no video editing, trimming, or cutting features, and finished recordings save to your camera roll as MP4. That is exactly why the teleprompter and the pre-record checklist matter: the workflow assumes you’re getting the take right in one pass.