# Screen Recording for Bug Reports

**Capture bugs visually, not textually.**

## Why Screen Recording?

Traditional bug reports ask testers to describe bugs in words:

- "The button was unresponsive"
- "The page took a long time to load"
- "The text was cut off"

These descriptions are vague. Developers have to ask follow-up questions. It's slow.

**With video, the bug is clear immediately.** Developers see exactly what went wrong and can start fixing.

## How clip.qa Recording Works

### iOS
- **Native screen recording** via iOS Broadcast Extension
- **Audio support** — narrate the bug while recording
- **Direct to app** — no external tools, no waiting for uploads
- **On-device processing** — videos stay on your phone until you export

### Android
- **System screen recording** — built-in Android recording
- **Optional narration** — add voice context
- **Local processing** — videos stored in app sandbox

### Web (Chrome Extension)
- **Lightweight recording** — minimal CPU overhead
- **Screenshot + video** — capture state changes and animations
- **Instant export** — share links or download locally

## Recording Tips

- **Keep it short** — 30 seconds to 2 minutes is ideal
- **Narrate the issue** — "Tapping this button does nothing" helps AI understand intent
- **Capture the full sequence** — Show what you did and what happened
- **Include error messages** — If the app crashed or showed an error, capture that

## Editing (iOS App)

Before generating a report, you can:

- **Trim start/end** — Remove unnecessary frames
- **Trim middle sections** — Cut out irrelevant actions (e.g., typing credentials)
- **Mark annotations** — Highlight the problem area with arrows or circles
- **Adjust audio** — Mute, reduce, or re-record narration

## Best For

Screen recording works best for:

- **UI bugs** — Layout, styling, rendering issues
- **Navigation bugs** — Wrong page, broken links, missing content
- **Crashes** — Capture the crash with reproduction steps
- **Performance** — Slow loading, stuttering, freezes
- **Multi-step workflows** — Bugs that only happen after specific sequences

## AI Analysis

clip.qa's AI:

- Watches the video frame-by-frame
- Identifies the moment the bug occurs
- Extracts context (app state, device info, OS version)
- Generates a structured report
- Suggests severity and classification

## Privacy & Storage

- Videos are stored locally on your device in the app's sandbox
- Exported videos are encrypted in transit (TLS 1.3)
- Videos are never used for training
- You control when and if videos leave your device