# BugScreen

> BugScreen is the in-app bug reporter built mobile-first: a person reports a
> problem from inside an iOS, Android, or React Native app, and it files to the
> team's existing tracker with screenshots, logs and device context attached.

## Product

- [Home](https://www.bugscreen.app/): What BugScreen is and how it works.
- [Pricing](https://www.bugscreen.app/pricing): Free, Pro, Team, and Enterprise plans. Unlimited testers on every plan.
- [Changelog](https://www.bugscreen.app/changelog): Product updates.
- [Support](https://www.bugscreen.app/support): Common questions about the BugScreen app, and how to reach a human.

## Blog

- [Blog](https://www.bugscreen.app/blog): Product launches, engineering notes, and mobile QA guides.
- [How to record a mobile bug](https://www.bugscreen.app/blog/screen-recording-bug-report): Capture a useful iPhone or Android screen recording, add timestamps and build details and check the evidence before sharing.
- [iPhone Duo app bugs](https://www.bugscreen.app/blog/iphone-duo-app-bug-reporting): Capture display, folding and keyboard failures with the evidence and reproduction details developers need.
- [How to send Google Play beta feedback](https://www.bugscreen.app/blog/how-to-send-google-play-beta-feedback): Submit private app-beta feedback, find it in Play Console and give internal testers a direct reporting route.
- [Mobile device test matrix](https://www.bugscreen.app/blog/mobile-device-test-matrix): Choose release QA configurations, assign scenarios and record evidence and coverage gaps with a copyable template.
- [Bug intake triage template](https://www.bugscreen.app/blog/bug-intake-triage-template): A mobile QA worksheet for evidence checks, triage decisions, ownership and inconclusive reproduction.
- [How to send TestFlight feedback](https://www.bugscreen.app/blog/how-to-send-testflight-feedback): Send native beta feedback, find it in App Store Connect and prepare an actionable engineering issue.
- [Introducing BugScreen](https://www.bugscreen.app/blog/introducing-bugscreen): How BugScreen turns a tester's screenshot into a developer-ready ticket in GitHub, Jira, or ClickUp.
- [Mobile app bug reporting guide](https://www.bugscreen.app/blog/mobile-app-bug-reporting-guide): How to capture screenshots, logs, device details, and reproducible context during mobile QA.
- [How to collect user feedback in a mobile app](https://www.bugscreen.app/blog/how-to-collect-user-feedback-in-a-mobile-app): Choose the right method for surveys, feature discovery and contextual issue reports.
- [Mobile beta testing checklist](https://www.bugscreen.app/blog/mobile-beta-testing-checklist): Plan a mobile beta from cohort and build verification through issue intake, privacy and release gates.
- [How to manage mobile beta feedback](https://www.bugscreen.app/blog/manage-mobile-beta-feedback): Collect, triage, deduplicate and close the loop on feedback as a mobile beta cohort grows.

## Solutions

- [Solutions hub](https://www.bugscreen.app/solutions): Use cases and role-based solutions for mobile bug reporting.
- [QA bug reporting](https://www.bugscreen.app/solutions/qa-bug-reporting): QA bug reporting where a tester's screenshot becomes a tracked ticket.
- [Beta testing feedback](https://www.bugscreen.app/solutions/beta-testing-feedback): Keep a flood of mobile beta testing feedback triageable against a fixed release deadline.
- [TestFlight feedback](https://www.bugscreen.app/solutions/testflight-feedback): Complement TestFlight's native feedback with a consistent issue-reporting and tracker-routing workflow.
- [Google Play beta feedback](https://www.bugscreen.app/solutions/google-play-beta-feedback): Add structured issue reporting to Android internal, closed and open tests.
- [Frequent releases](https://www.bugscreen.app/solutions/frequent-releases): Bug reporting for teams on a regular release train, where a bad build can't be rolled back.
- [Remote QA handoff](https://www.bugscreen.app/solutions/remote-qa-handoff): Remote QA bug reporting so a QA-to-engineering handoff across timezones doesn't cost a day per round-trip.
- [Client feedback for agencies](https://www.bugscreen.app/solutions/agencies-client-feedback): Turn vague client feedback into actionable tickets in your agency's tracker.
- [End-user bug reporting](https://www.bugscreen.app/solutions/end-user-bug-reporting): Let mobile app users report contextual problems without leaving the app.
- [Screenshot to bug report](https://www.bugscreen.app/solutions/screenshot-to-bug-report): Turn a screenshot into a bug report automatically.
- [File bugs to Jira](https://www.bugscreen.app/solutions/file-bugs-to-jira): File bugs to Jira (and GitHub or ClickUp) straight from a mobile app.
- [File bugs to ClickUp](https://www.bugscreen.app/solutions/file-bugs-to-clickup): File bugs to ClickUp (and Jira or GitHub) straight from a mobile app.
- [File bugs to Linear](https://www.bugscreen.app/solutions/file-bugs-to-linear): Turn an in-app mobile bug report into a Linear issue with screenshots, logs and device context.
- [UAT and stakeholder testing](https://www.bugscreen.app/solutions/uat-stakeholder-testing): Simple in-app bug reporting for non-technical UAT testers.
- [Firebase App Distribution bug reporting](https://www.bugscreen.app/solutions/firebase-app-distribution-bug-reporting): The reporting step between a distributed test build and your issue tracker.
- [Bug reporting for developers](https://www.bugscreen.app/solutions/bug-reporting-for-developers): Native SDK bug reporting for mobile developers.
- [Bug reporting for QA teams](https://www.bugscreen.app/solutions/bug-reporting-for-qa): In-context bug reporting built for QA teams.

## Comparisons

- [Compare BugScreen](https://www.bugscreen.app/compare): How BugScreen stacks up against other mobile bug-reporting tools.
- [BugScreen vs Jam](https://www.bugscreen.app/compare/bugscreen-vs-jam): Native mobile vs browser bug reporting.
- [BugScreen vs Marker.io](https://www.bugscreen.app/compare/bugscreen-vs-marker-io): Native mobile vs website feedback and UAT.
- [BugScreen vs BugHerd](https://www.bugscreen.app/compare/bugscreen-vs-bugherd): Native mobile vs website and client feedback.
- [Jam alternative for mobile](https://www.bugscreen.app/alternatives/jam-alternative): A Jam-like capture workflow for native mobile apps.
- [Marker.io alternative for mobile](https://www.bugscreen.app/alternatives/marker-io-alternative): Mobile-native reporting for teams using Marker.io on web.
- [BugHerd alternative for mobile](https://www.bugscreen.app/alternatives/bugherd-alternative): Mobile-native reporting for teams using BugHerd on web.

- [BugScreen vs Instabug](https://www.bugscreen.app/compare/bugscreen-vs-instabug): Mobile bug reporting compared on pricing, platforms, and tracker handoff.
- [BugScreen vs Shake](https://www.bugscreen.app/compare/bugscreen-vs-shake): Mobile bug reporting compared on pricing, platforms, and tracker handoff.
- [Instabug vs Shake](https://www.bugscreen.app/compare/instabug-vs-shake): A neutral comparison of two bug-reporting tools.
- [Instabug alternative](https://www.bugscreen.app/alternatives/instabug-alternative): A mobile-first Instabug alternative for pre-release QA.
- [Shake alternative](https://www.bugscreen.app/alternatives/shake-alternative): A mobile-first Shake alternative for pre-release QA.

## Tools

- [Developer tools](https://www.bugscreen.app/tools): Free, browser-based tools for developers working with Jira, GitHub, and mobile bug reports.
- [Jira Markdown to ADF converter](https://www.bugscreen.app/tools/jira-markdown-converter): Convert Markdown to Atlassian Document Format (ADF) JSON for the Jira REST API, and ADF back to Markdown. Runs entirely in the browser.
- [Bug report template generator](https://www.bugscreen.app/tools/bug-report-template-generator): Fill in the fields and copy a clean, reproducible bug report as Markdown, Jira, or plain text. Runs entirely in the browser.
- [Beta test issue template](https://www.bugscreen.app/tools/beta-test-issue-template): Capture build, distribution, device, affected flow and reproduction details, then copy a beta issue as Markdown, Jira or plain text.
- [Screenshot annotate & redact](https://www.bugscreen.app/tools/screenshot-annotate): Annotate a screenshot with boxes, arrows, and a pen, then permanently blur or black out sensitive info. Runs entirely in the browser — the image is never uploaded.

## Documentation

- [Companion video attachments](https://www.bugscreen.app/docs/companion/video-attachments): Gallery and shared video reports in video-capable companion releases.

- [Android — Screenshot reports](https://www.bugscreen.app/docs/android/screenshot-reports)
- [Android — Video attachments](https://www.bugscreen.app/docs/android/video-attachments)
- [Android — Manual reports](https://www.bugscreen.app/docs/android/manual-reports)
- [Android — Logging](https://www.bugscreen.app/docs/android/logging)
- [Android — Custom data](https://www.bugscreen.app/docs/android/custom-data)
- [Android — User accounts](https://www.bugscreen.app/docs/android/user-accounts)
- [Android — Configuration](https://www.bugscreen.app/docs/android/configuration)
- [Android — Collected data](https://www.bugscreen.app/docs/android/collected-data)
- [iOS — Screenshot reports](https://www.bugscreen.app/docs/ios/screenshot-reports)
- [iOS — Video attachments](https://www.bugscreen.app/docs/ios/video-attachments)
- [iOS — Manual reports](https://www.bugscreen.app/docs/ios/manual-reports)
- [iOS — Logging](https://www.bugscreen.app/docs/ios/logging)
- [iOS — Custom data](https://www.bugscreen.app/docs/ios/custom-data)
- [iOS — User accounts](https://www.bugscreen.app/docs/ios/user-accounts)
- [iOS — Configuration](https://www.bugscreen.app/docs/ios/configuration)
- [iOS — Collected data](https://www.bugscreen.app/docs/ios/collected-data)
- [React Native — Screenshot reports](https://www.bugscreen.app/docs/react-native/screenshot-reports)
- [React Native — Video attachments](https://www.bugscreen.app/docs/react-native/video-attachments)
- [React Native — Manual reports](https://www.bugscreen.app/docs/react-native/manual-reports)
- [React Native — Logging](https://www.bugscreen.app/docs/react-native/logging)
- [React Native — Custom data](https://www.bugscreen.app/docs/react-native/custom-data)
- [React Native — User accounts](https://www.bugscreen.app/docs/react-native/user-accounts)
- [React Native — Configuration](https://www.bugscreen.app/docs/react-native/configuration)
- [React Native — Collected data](https://www.bugscreen.app/docs/react-native/collected-data)
- [BugScreen MCP](https://www.bugscreen.app/docs/mcp): Configure apps and investigate saved reports through an authenticated assistant. Requires an existing account and workspace.

- [Docs hub](https://www.bugscreen.app/docs): SDK install and integration guides.
- [Android SDK](https://www.bugscreen.app/docs/android): Kotlin SDK setup.
- [iOS SDK](https://www.bugscreen.app/docs/ios): Swift SDK setup.
- [React Native SDK](https://www.bugscreen.app/docs/react-native): TypeScript wrapper bridging the native iOS and Android SDKs.
- [Companion app](https://www.bugscreen.app/docs/companion): The app testers install to report bugs in a build that has no SDK in it — pairing, capture, and what a companion report does and doesn't carry.
- [Customise the bug reporter](https://www.bugscreen.app/docs/console/reporter): Customise reporter wording, set Type choices, and show or hide Severity for each BugScreen app.
- [Report Inbox](https://www.bugscreen.app/docs/console/inbox): Find and read tester reports, check delivery to integrations, and understand report retention.
- [Integrations](https://www.bugscreen.app/docs/integrations): Connect an issue tracker.
- [GitHub integration](https://www.bugscreen.app/docs/integrations/github): File issues to GitHub.
- [Jira integration](https://www.bugscreen.app/docs/integrations/jira): File issues to Jira.
- [ClickUp integration](https://www.bugscreen.app/docs/integrations/clickup): File tasks to ClickUp.
- [Slack integration](https://www.bugscreen.app/docs/integrations/slack): Post reports to a Slack channel.
- [Linear integration](https://www.bugscreen.app/docs/integrations/linear): File issues to Linear.