Screenshots and Video

Snapbug Recorder

The Snapbug Recorder mobile app (Android and iOS) lets you capture screenshots and screen recordings directly on your device, annotate them, and send them to the Snapbug inspector.

Overview

Snapbug Recorder is a standalone mobile app (separate from the SDK) designed for QA engineers, product managers, and founders who need to capture visual evidence of bugs — in any app, without integrating anything. It pairs with the inspector over a room code, so captures land right where your team triages them.

Capturing

Floating Bubble

Recorder shows a floating bubble over the app you are testing. Tap it to capture the current screen; while recording, tapping the bubble stops the recording. The bubble stays out of your way and works across app switches.

Notification Actions

While Recorder is running, a persistent notification offers one-tap actions without leaving the app under test:

  • Record / Stop — start or stop a screen recording
  • Screenshot — capture the current screen
  • Bug Report — jump straight into the report flow
  • Connect / Disconnect — manage the inspector connection

Importing Existing Screenshots

Already have a screenshot in your gallery? Import it into Recorder to annotate and share it the same way as a fresh capture.

Video Recording

Record screen interactions to capture complex bugs, multi-step flows, or animation issues.

  • On Android, recording uses the system MediaProjection API — you grant screen capture permission once per session.
  • On iOS, recording uses ReplayKit.

After stopping, the recording opens in a preview where you can review it before sharing.

Sharing

After a capture you can:

  • Send to Inspector — the primary action; the capture appears in the inspector's Reports with its context attached.
  • Share — use the system share sheet to send the file to Slack, Jira, email, or any other app.

Pairing with the inspector uses a short room code — type it in or scan the QR code shown by the Chrome extension.

Automatic Context

Captures sent to the inspector carry device context — device model, OS version, and screen details — so your team always knows the environment a bug was reported from.

Next Steps

DataStoresАннотации