Bug reports from testers, with screenshots, straight from the install page
Every plan, guest uploads included. Screen recordings, alerts and star ratings on Pro and Team; replies, release blockers and TestFlight feedback in the inbox on Team
Feedback from testers usually arrives as a chat message with a blurry photo of a screen and no idea which build or phone it came from. Then someone asks three follow up questions and the bug waits a day.
Every AppForShare install page now has a Send feedback card. The tester writes what happened, adds screenshots and draws on them, and sends. The device, OS version and the exact build are attached for them, and the report lands in your feedback inbox. Nothing goes into your app: no SDK, no new dependency, no new release.
Example
Feedback, 3 open
- Bug: checkout button does nothingiPhone, iOS 18.1, 2 screenshots
- Idea: dark mode on the profilePixel 8, Android 14
- Bug: crash on the second launchBlocker, with a recording
- Bug: wrong price on iPadResolved by Sara
Made for
- Teams whose testers are clients, outside QA or friends who will not install another app
- Agencies that want client bug reports in one place instead of five chats
- Developers who test on many phones and want each report tied to the right build
What it ends
- Screenshots in chat with no device, OS or build number
- Asking the tester which version they had installed
- Bug reports spread over email, chat and a spreadsheet
- Adding a feedback SDK just for the beta, then removing it before release
How it works
Step 1
Share the install link as usual
Any build, from the dashboard, the CLI or CI. Channel links work too: on a phone they open the newest build.
Step 2
The tester presses Send feedback
They pick Bug, Idea or Other, write what happened and add up to 5 screenshots. A tap on a screenshot lets them draw on it. On Pro and Team they can add a screen recording.
Step 3
Your team triages it
Reports land in the feedback inbox and on the build page. Mark them resolved, send one to Linear or Jira, or on Team mark it as a release blocker or make it a task.
No SDK, nothing to ship
Feedback SDKs work well inside an app, but they add a dependency, a release and a privacy review, and they only help once the tester has the new build. The install page is where every tester already is, so the button lives there. The same page that installs the build collects the report about it.
Screenshots are made smaller in the tester's browser before upload, so a report sends quickly on a phone connection. The tester can draw on each one with a red pen to point at the problem.
Alerts where your team works
The account owner gets an email for new feedback on every plan, at most one per build per hour, so a busy test day does not flood the inbox. The email says which build and device, and you read the report in the dashboard.
On Pro and Team, new reports also arrive as push notifications and through the feedback.new event in Slack, Microsoft Teams, Google Chat, Discord or your own webhook, with the tester's message. Telegram gets a short notice with the kind and device, without the tester's text. Your AI coding tool can read them through the MCP server, and the CLI prints them with appforshare feedback.
Reply to the tester, rate the build
On Team, reply to a report from the inbox, the build page, the CLI or an AI tool. The tester gets one email in the language of their install page and can answer once on the install page, so the thread stays on the report. On Pro and Team, testers can also rate each build from 1 to 5 stars, and the build page shows the average. See reply to tester feedback.
Blockers on Team
On Team, mark a report as a release blocker. The inbox has a blockers only view, so the whole team sees what has to be fixed before the build goes to everyone. With a release checklist, open blockers also hold the Live channel until they are resolved.
TestFlight feedback in the same inbox, on Team
If you also test through TestFlight, connect App Store Connect and share the app. AppForShare reads the screenshot feedback and crash feedback your TestFlight testers send every 30 minutes and puts each report in the inbox with the source TestFlight, the TestFlight build, the device and, for a crash, Apple's crash log. Mark it resolved or as a blocker, make a task, or send it to Linear or Jira like any other report.
It only reads. Nothing is changed in App Store Connect, and the reports stay in TestFlight as well. A report is matched to your build of the same version in AppForShare; reports for an app you have no build of wait until you upload one.
From inside the app, still without an SDK
Turn on the in-app feedback link of a project and open it from a debug menu or a shake in your test build. The same form opens for the build the tester is running, with the screen they were on, and the report is marked In app. A few lines of Swift, Kotlin, React Native or Flutter, on every plan with an account.
TestFlight feedback in the same inbox (Team)
With an App Store connection, screenshot feedback and crash feedback that TestFlight testers send from the TestFlight app come into the same inbox every 30 minutes, marked TestFlight. Send them to Linear or Jira, mark a blocker or make a task like any other report. AppForShare only reads them from App Store Connect.
Next to your crash reports
On Pro and Team, paste the address of your Crashlytics, Sentry, Bugsnag or other crash dashboard on the project, with {version} and {build} in it if you like. Each report, the owner email and the Linear or Jira issue then link to the crashes of that exact build. AppForShare only keeps the address; it never collects crash data.
Good to know
- It does not collect crash reports from your app. The crash dashboard link points to the tool you already use. On Team, crash logs TestFlight testers send come in with their TestFlight report.
- Up to 5 screenshots per report. One screen recording of up to 45 MB on Pro and Team.
- Replies to the tester by email are on Team, and only when the tester left an email address. On Free and Pro, write to them yourself.
- Send to Linear or Jira (Pro and Team) creates an issue with the screenshots; it goes one way, with no sync back. Copy for an issue gives plain text on every plan.
Questions
- Which plan do I need?
- Every plan with an account gets the feedback form with screenshots and the email. Screen recordings plus push, Slack, Teams, Google Chat, Discord and webhook alerts are on Pro and Team. Marking release blockers and replying to testers are on Team; star ratings per build are on Pro and Team. Builds uploaded as a guest get the form too, with up to 3 screenshots behind a human check, read through the guest's private manage link.
- Do I need to add anything to my app?
- No. The form is part of the install page testers already open. There is no SDK and no code change. If you want a feedback button inside the test build, the in-app feedback link takes a few lines that open a web address.
- What does a report include?
- The kind (bug, idea or other), the tester's text, optional name and email, screenshots or a recording, the build, and the device, OS version, screen size and language their browser reports.
- Can strangers spam me?
- Only people who can open the install page can send feedback. Private projects allow invited testers only. Each address can send 10 reports an hour, and each build takes up to 100 a day.
- Do screenshots count toward my storage?
- No. They are kept until you delete the report or the build's files are removed.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications