The question that came back most often after the teleprompter posts was some version of this: “I set up my script, I rehearsed the pacing, and then I switched to External PiP to record a different app and the teleprompter was just gone.” That is not a bug. It is an iOS constraint, and it changes how you build a teleprompter workflow for anything recorded outside DemoScope.
Short answer: DemoScope’s teleprompter only works in in-app recording mode on iPhone and iPad. External PiP mode uses an iOS Broadcast Extension to capture the whole system, which limits the available tools to Camera, PiP Border, and Text on screen. For External PiP recordings, move your script to a physical card or a second device and shrink it to beats, not sentences.
Why the teleprompter disappears when you leave the app
The DemoScope teleprompter is an overlay drawn by DemoScope while DemoScope is the app on screen. It scrolls at an adjustable speed, it is visible only to you, and it never lands in the exported MP4. That works because DemoScope owns the screen.
External PiP recording works differently. DemoScope activates a floating face cam window, sends itself to the background, and hands capture off to the iOS Broadcast Extension so you can walk through any app on your phone. Once DemoScope is backgrounded, it has no surface to draw a private overlay on. Same reason touch indicators and the DemoScope HUD controls do not appear in External PiP mode either. The tools that survive the handoff are Camera, PiP Border, and Text on screen.
One thing worth being precise about: the teleprompter is the only DemoScope tool documented as visible to you but not recorded. Do not plan to use the Text on screen tool as a substitute prompt. Treat it as a label for your viewer, not a private cue card for you.
In-app vs External PiP: what you actually get
| In-app recording | External PiP recording | |
|---|---|---|
| Records other apps | No | Yes, system-wide |
| Teleprompter | Yes | No |
| Touch indicators | Yes | No |
| Face cam overlay | Yes | Yes |
| PiP Border customization | Yes | Yes |
| Text on screen | Yes | Yes |
| Recording controls | DemoScope HUD | iOS system recording UI |
| Best for | Scripted walkthroughs of your own app | Demos that span multiple apps |
If your entire demo lives inside one app you control, record in-app and keep the teleprompter. That is the version of the workflow covered in mastering the teleprompter workflow: how to sound natural while recording on your iPhone. External PiP is the right call only when the demo genuinely crosses app boundaries, like showing Settings, then Safari, then your app.
Converting a scrolling script into External PiP beats
The mistake is trying to memorize the script you wrote for a scrolling prompter. Word-for-word paragraphs fall apart the moment you are also driving a multi-app flow with your thumb. Convert instead.
- Take your existing script and mark every place where you tap, switch apps, or change screens. Those are your beats.
- Write one line per beat, maximum eight words, phrased as an action plus a claim. Example: “Open Settings, show the permission toggle, one tap.”
- Cap it at six to eight beats per recording. Longer than that and you will fumble an app switch.
- Write the beats on an index card or a second phone and prop it directly beside your recording hand, roughly at eye level with the camera bubble.
- Do one silent dry run of the app-switching sequence with the card visible. You are rehearsing navigation, not wording.
- Start External PiP, wait two seconds of dead air before speaking, then work the beats.
The dead air at the start matters more than people expect. The iOS system recording UI takes a moment to hand off, and a clean two seconds gives you a predictable head on the file.
When to go back to in-app recording instead
Be honest about whether you need the app switch at all. If your script is dense, full of exact numbers, version strings, or API names, the teleprompter is worth more than the ability to leave the app. Technical scripts are the hardest thing to hold in your head, which is the whole premise of these advanced teleprompter tips for technical demo scripts.
My recommendation, and the trade-off it costs: default to in-app recording with the teleprompter, and accept that you may have to record the “other app” portion as a separate clip. You lose the single continuous take. You gain a scripted delivery and touch indicators on the part of the demo that actually explains your product. For most app demos, that is the better trade.
Skip External PiP entirely if your demo is 90 percent inside your own app and you were only switching out to show one notification.
Where this fits in the larger workflow
None of this changes the fundamentals: short blocks, natural pacing, and a rehearsal pass before the real take. If you are still building the base system, this guide to an efficient teleprompter workflow for mobile recording in 2026 covers the structure, and the breakdown of where most creators get mobile script recording wrong covers the failure modes worth avoiding early.
DemoScope runs on iOS 14 and later, exports MP4 (H.264) straight to your camera roll, and Pro is a $19.99 one-time purchase that removes the watermark. If most of your recordings are scripted walkthroughs of one app, that in-app teleprompter is the feature you will use every single session.
Frequently Asked Questions
Why can’t I see the teleprompter when recording another app?
Because DemoScope’s teleprompter is only available in in-app recording mode. External PiP mode backgrounds DemoScope and uses an iOS Broadcast Extension for system-level capture, so the tools are limited to Camera, PiP Border, and Text on screen.
Can I use the Text on screen tool as a teleprompter in External PiP?
Treat it as a label for viewers rather than a private prompt. The teleprompter is the only DemoScope tool documented as visible to you and not recorded, so use a paper card or second device for your script during External PiP recordings.
How long should a script be for an External PiP recording?
Six to eight beats, one short line each, is a practical ceiling. Without a scrolling prompter you are holding the script in working memory while also navigating between apps, and longer scripts are where retakes come from.
Does External PiP mode support touch indicators?
No. Touch indicators are an in-app recording feature only. If showing taps matters to your demo, record that portion in-app with DemoScope rather than in External PiP mode.
Is DemoScope a subscription?
No. DemoScope Pro is a $19.99 one-time purchase that removes the watermark and unlocks the full feature set, including the teleprompter and External PiP recording. There is a free tier with watermarked recording if you want to test the workflow first.