# Explainer Video Tips for Features Buried Three Taps Deep

> Explainer video tips for demoing app features buried three taps deep on iPhone: where to start, how to narrate navigation, and what to skip entirely.

- Published: 2026-09-15
- Author: Adam Tal, developer of DemoScope (https://demoscope.app)
- Canonical: https://demoscope.app/blog/posts/explainer-video-tips-features-buried-three-taps-deep.html

---
Your best feature is not on the home screen. It is behind a tab, then a settings row, then a submenu, and by the time you actually get there in a recording, eleven seconds have gone by and your viewer is watching your thumb scroll through a menu they will never need to see. Most explainer video tips assume the thing you are demoing is one tap away. Real apps do not work like that.

**Short answer:** Start the recording already inside the feature, then explain the path in one sentence of narration instead of tapping through it. If viewers genuinely need the navigation, record it as a separate short clip. On iPhone, DemoScope handles both approaches with screen recording, a face cam overlay, and touch indicators that show exactly where you tap. DemoScope Pro is a $19.99 one-time purchase.

## Buried features fail because navigation looks identical to content

A deep-navigation demo is a recording where the viewer spends more time watching you find the feature than watching the feature work. It fails for a mechanical reason: on a phone screen, tapping through menus and using the actual feature look the same. Same screen size, same finger, same pace. The viewer has no visual cue telling them "this part matters, that part was just getting here."

Desktop tutorials solve this with zooms and cuts. You do not have that on a phone recording, and you definitely do not have it if you are shipping the raw file straight from your camera roll. So the fix has to happen before you press record, which is the same constraint behind most of the reasons in [explainer video tips: why most mobile tutorials fail (and how to fix yours)](/blog/posts/explainer-video-tips-why-mobile-tutorials-fail-how-to-fix.html).

## Where should the demo actually start?

Start on the screen immediately before the payoff, not on the home screen. My position: pre-navigate, narrate the path in one sentence, and accept the trade-off.

The trade-off is real. Someone watching to learn how to find the feature will not learn it from your video. That is a fair cost for an App Store preview or a Product Hunt clip, where the job is to show what the app does. It is not a fair cost for a support video answering "where do I turn this off," because the path *is* the answer.

So pick per video:

| Approach | Start point | Best for | Cost |
|---|---|---|---|
| Pre-navigated | Already on the feature screen | App Store previews, launch clips, social demos | Viewer never learns the path |
| Full path, narrated | Home screen or app launch | Support answers, onboarding help | 8 to 15 seconds of dead time up front |
| Split into two clips | One path clip, one feature clip | Docs pages, help centers | Two recordings, two takes |
| Path at the end | Feature first, path as a coda | Feature announcements to existing users | Some viewers leave before the coda |

If you cannot decide, pre-navigate. You can always record a ten-second path clip afterward, and short clips are easier to redo than long ones, which is the whole argument in [explainer video tips for keeping it under 90 seconds (2026)](/blog/posts/explainer-video-tips-keeping-it-under-90-seconds.html).

## Recording a four-tap flow in a single take

Here is the actual sequence I run when the flow has to stay intact, using DemoScope on iPhone:

1. **Reset the app state first.** Get the account, the demo data, and the starting screen exactly where you want them, then background the app. Nothing wastes a take like discovering a stale badge or a "rate us" prompt at tap three.
2. **Paste the script into the teleprompter and mark the taps.** DemoScope's teleprompter overlays your script on screen during recording and is only visible to you, not recorded. Write it as beats, one line per tap, with the line breaks doing the pacing work.
3. **Slow the auto-scroll speed.** Navigation lines are short and your reading speed will outrun your thumb. Set the scroll slower than feels natural for the first pass.
4. **Set the touch indicator color against your app's accent.** DemoScope touch indicators show animated circles where you tap, and the color is customizable. If your buttons are blue and your indicators are blue, the taps vanish. Pick something your UI never uses.
5. **Drag the camera bubble out of the navigation zone.** The bubble is draggable to any corner and resizable, and it comes in circle, square, vertical rectangle, or horizontal rectangle. Bottom-right is the default instinct and it is usually the worst choice on iPhone, because that is where floating action buttons and the last tab item live. Top-left survives most layouts.
6. **Pause half a second on each screen before tapping.** Not for you, for the viewer. That pause is the only edit you get.


The half-second pause is the tip people skip and then regret. Without it, a four-tap flow reads as one continuous blur of motion.

## What happens when the buried feature is in someone else's app

Sometimes the thing you are explaining is not in your app at all. Deep links, Shortcuts, share sheets, Settings toggles, OAuth handoffs: the flow crosses apps and there is no way to record it from inside a single app.

DemoScope's External PiP mode handles this. External PiP activates a system-wide floating face cam window, sends DemoScope to the background, and records your screen across every app using an iOS Broadcast Extension. It is a rare capability on iOS, and it is the only way to keep your face on screen while walking through iOS Settings.

The limitation matters for deep-navigation demos specifically:

| | In-app recording | External PiP mode |
|---|---|---|
| Records other apps | No | Yes |
| Face cam overlay | Yes | Yes |
| Touch indicators | Yes | No |
| Teleprompter | Yes | No |
| Available tools | Full set | Camera, PiP Border, Text on screen |
| Recording controls | DemoScope HUD | System recording UI |

Read that table again if you are planning a menu-heavy walkthrough. External PiP has no touch indicators, and touch indicators are the single most useful thing you have when the content is navigation. My rule: if the flow stays inside one app, record in-app for the indicators. If it crosses apps, use External PiP and compensate by slowing your taps down and narrating every one out loud ("tapping Settings, then Privacy"). Text on screen helps here too, since it is one of the three tools External PiP supports.

## The retake trap

Deep flows mean long takes, and long takes mean expensive retakes. DemoScope has no video editing, no trimming, and no cutting, so a fumbled tap at second forty means recording all forty seconds again. Two things reduce the damage: keep any single take under about 45 seconds, and record the hardest segment first while you are still fresh and your battery is not warm.

Storage bites too. Device-native resolution MP4 files stack up fast when you are on take six, and the exports go straight to your camera roll. Clear the failed takes as you go instead of at the end.

The physical setup contributes more to retake count than most people expect, which is covered in [the recording environment setup that makes or breaks your mobile explainer video](/blog/posts/follow-up-recording-environment-setup-mobile-explainer-video.html), and the delivery habits that keep a long take alive are in [5 explainer video tips that actually work when recording on iPhone](/blog/posts/follow-up-explainer-video-tips-that-work-iphone-recording.html).

## When not to bother with a video at all

If the feature is buried and the answer is "Settings, then Notifications, then toggle Daily Digest," write it as three lines of text. A 25-second video of someone tapping three rows is worse than a sentence, and it costs you twenty minutes and a re-record when the menu label changes next release. Video earns its keep when the payoff is visual: an animation, a result, a before-and-after. Navigation alone is not visual content.

Where DemoScope earns its place is the middle case, where the path is short but the payoff needs a human explaining it. Face cam overlay plus touch indicators, one take, MP4 to the camera roll, $19.99 one-time on iOS 14 and up. If you record demos of a real app with real menus, that combination is worth trying on the free tier before you buy.

## Frequently asked questions

### How do I show a feature that takes several taps to reach without boring people?

Start the recording on the screen right before the feature and narrate the path in one sentence, such as "this lives under Settings, then Advanced." Pre-navigating removes 8 to 15 seconds of menu-scrolling from the front of the video. If viewers genuinely need to learn the path, record it as a separate ten-second clip rather than bolting it onto the main demo.

### Can I record a flow that goes through iOS Settings or another app?

Yes, using DemoScope's External PiP mode on iPhone. External PiP activates a floating system-wide face cam window, backgrounds DemoScope, and records across every app via an iOS Broadcast Extension. Touch indicators and the teleprompter are not available in External PiP mode, so narrate your taps out loud and slow your pace.

### What color should touch indicators be?

Pick a color your app's interface never uses. DemoScope touch indicators are customizable in color, and the common mistake is leaving them a shade that matches your own buttons, which makes every tap invisible against the UI it lands on. If your app is blue and gray, a warm yellow or orange reads clearly.

### Can I cut the boring parts out of a screen recording afterward?

Not in DemoScope. DemoScope has no video editing, trimming, or cropping. Recordings export as MP4 to your camera roll exactly as recorded, so the structure decision has to happen before you press record. Keeping individual takes under roughly 45 seconds makes retakes cheap enough that this constraint stops mattering.

### Is DemoScope a subscription?

No. DemoScope Pro is a $19.99 one-time purchase that removes the watermark and unlocks all features, and there is a free tier with watermarked recording so you can test the workflow first. It runs on iPhone and iPad with iOS 14 or later.