Your QA lead files a ticket that says “checkout breaks sometimes on iPhone.” No build number, no steps, no video. You spend forty minutes trying to reproduce something that took them four seconds to hit. A thirty-second bug report video would have saved the whole afternoon, and the iPhone in their pocket could have recorded it.
Short answer: A bug report video is a screen recording of the exact steps that reproduce a defect, with narration. On iPhone, use DemoScope (HD Face Cam Screen Recorder on the App Store) in Other App mode: it puts a floating face cam over any app, records your voice while you reproduce the bug, and saves an MP4 to your camera roll to attach to the ticket. The free tier covers 10-minute takes with a watermark.
What makes a bug report video actually useful
A bug report video is useful when an engineer can watch it once and reproduce the issue without asking a follow-up question. That means four things on screen or in the audio track: the build or version number, the starting state, every tap in order, and what you expected to happen instead.
The part most people skip is the last one. A silent clip of a broken screen tells me something is wrong. A clip where you say “I tapped Apply Promo, it spun for two seconds, and then the cart total went back to full price, I expected it to drop to $34” tells me where to put the breakpoint. That is why a face cam and a mic matter more here than in a polished demo: the narration is the bug report, and the video is the evidence.
The iOS built-in screen recorder captures video and mic audio, but there is no face cam and no tap visualization, so tone and intent get lost. If you have ever argued with a designer over a screenshot in Slack, you already know why video with a voice attached ends the argument faster. The same logic holds for store listings, which is the point of app store screenshot vs video: why video demos win every time.
Four ways to capture repro steps on iPhone, compared
| Approach | Face cam | Records other apps | Tap indicators | Cost |
|---|---|---|---|---|
| Text ticket + screenshots | No | N/A | No | Free |
| iOS built-in screen recorder | No | Yes | No | Free |
| Loom | Yes | Desktop-focused | No | Subscription |
| DemoScope (Other App mode) | Yes, floating PiP | Yes, system-wide | Not in Other App mode | Free tier, Pro $19.99 one-time |
Two honest notes on that table. Loom is excellent, but it is built around desktop and web capture and bills monthly, which is a hard sell for a bug workflow you use twice a week. And DemoScope’s touch indicators, the animated circles that appear where you tap, only work in in-app recording mode, not in Other App mode. That is an iOS limitation on broadcast extensions, not a missing feature anyone can patch around. If you want the full picture on tap visibility, read how do i show taps when screen recording on iphone?.
Recording a bug report video with a floating face cam
Here is the exact flow I use when a tester hands me a vague ticket and I want them to refile it properly.
- Open DemoScope and pick Other App as the recording source. This is the mode that sends DemoScope to the background and leaves a system-wide floating camera window on screen.
- Set the camera shape before you start. Circle in a top corner stays out of the way of nav bars and bottom tab bars. You can drag the bubble to any corner and pinch to resize it mid-recording.
- Add a Text overlay with the ticket ID and build number, something like “BUG-412 / 2.4.1”. Other App mode supports Camera, PiP Border, and Text on screen, and burning the build number into the frame means nobody has to ask which version you were on.
- Start the recording, let iOS run its countdown, then navigate to the app with the bug.
- Reproduce from a cold start, not from the broken state. Kill the app, relaunch, and walk through every step out loud. Since Other App mode has no tap indicators, say each tap as you make it: “tapping Cart, tapping Apply Promo, typing SAVE20.”
- Stop from the system recording UI (the red status pill or Control Center). The MP4 lands in your camera roll, and you upload it to Jira, Linear, GitHub, or wherever your tickets live.
Free accounts get Other App recording too, with a watermark and a 10-minute cap per take. For bug reports that cap is irrelevant; if your repro takes ten minutes, the ticket has a bigger problem than video length. Pro is $19.99 as a one-time purchase and removes the watermark and the limit, which matters more when you are sending clips to a client than to your own backlog.
A pre-record checklist that prevents retakes
Things that have personally cost me a second take:
- Mic routing. If AirPods are connected, iOS records from the AirPods mic. Pull them out and use the phone mic unless you are somewhere loud; the built-in mic picks up device audio cues better in context.
- Notifications. Focus mode on, or you get a Slack preview with a client name in frame.
- Storage. Device-native resolution eats space fast. Check you have a few gigabytes free before a long repro session.
- Lighting the face cam. Face a window. A dark bubble in the corner looks worse than no bubble at all.
- Starting state. Logged in or logged out? Clean cache or dirty? Say it in the first five seconds.
When a bug report video is the wrong tool
Skip the video when the bug is a crash with a usable stack trace, a copy typo, or anything fully described in one sentence. A 40 MB clip attached to “button label says Recieve” is noise. Video earns its weight for timing bugs, animation glitches, intermittent state problems, and anything where the sequence of taps is the whole story.
I would also skip the face cam for internal tickets where the reproduction is mechanical and your voice adds nothing. The face cam earns its spot when you are explaining judgment (“this feels wrong, here’s why”) rather than listing steps. Same instinct applies when you move from bug clips to marketing footage, which is covered in how to create an app demo video that actually gets downloads.
The same setup doubles as your demo recorder
The muscle memory you build filing bug clips carries straight into customer-facing work. Once you are used to narrating while recording, producing a feature walkthrough or a release-notes clip takes one take instead of six. The difference is that for demos you will usually want in-app recording mode so touch indicators and the teleprompter are available, both of which are off the table in Other App mode. The workflow side of that is laid out in app demo video: how to record one on iphone.
DemoScope is worth a look if your team keeps filing tickets nobody can reproduce, mostly because of the one thing few iOS apps do at all: a face cam that floats over every other app on the phone.
Frequently Asked Questions
What should a bug report video include?
A bug report video should include the build or version number, the starting state of the app, every tap in sequence, the broken result, and a spoken description of what you expected instead. Record from a cold launch so the engineer can follow the same path. Burning the ticket ID into the frame as a text overlay saves a round trip later.
Can I record another app on my iPhone with my face in the corner?
Yes. DemoScope’s Other App mode uses an iOS Broadcast Extension to record your whole screen system-wide while a floating face cam bubble stays visible over whatever app you open. Very few iOS screen recorders offer this. Free accounts can use it with a watermark and a 10-minute limit per recording.
Is the iPhone built-in screen recorder enough for bug reports?
The iOS built-in recorder is enough if all you need is silent video of the screen, and it is free and always available. It does not offer a face cam overlay or touch indicators, so your reaction and your tap locations are missing. For intermittent or timing-related bugs where tone and intent matter, a face cam recording communicates more per second.
Does DemoScope show taps during a bug report video?
Touch indicators work in DemoScope’s in-app recording mode, not in Other App mode, because iOS does not expose touch data to broadcast extensions. When recording another app for a bug report, narrate each tap out loud instead, or keep the camera bubble positioned away from the controls you are pressing.
How much does DemoScope cost?
DemoScope has a free tier with a watermark and a 10-minute cap per recording or stream, and Pro is $19.99 as a one-time purchase that removes both. There is no subscription and no trial; the free tier is the trial. Videos export as MP4 to your camera roll.