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, Discord and webhook alerts are on Pro and Team. Marking release blockers is on Team. Builds uploaded as a guest, without an account, have no feedback form.

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.

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.

AppForShare Create a free account

Bug reports from testers, with screenshots, straight from the install page

Every plan with an account. Screen recordings and alerts on Pro and Team, release blockers 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.

Start free See plans

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

Device, OS and build come with every report.

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, copy one into an issue, or mark it as a release blocker on Team.

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, Discord or your own webhook, with the tester's message. Your AI coding tool can read them through the MCP server, and the CLI prints them with appforshare 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.

Good to know

It does not collect crash reports or send feedback from inside your app. Testers send it from the install page.
Up to 5 screenshots per report. One screen recording of up to 45 MB on Pro and Team.
No reply from the dashboard yet: if the tester left an email, write to them yourself.
No two way sync with Jira or Linear yet. Copy for an issue gives plain text, and webhooks can open a work item for each report.
Blockers are a label today; they do not stop a build from being put into the Live channel yet.

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, Discord and webhook alerts are on Pro and Team. Marking release blockers is on Team. Builds uploaded as a guest, without an account, have no feedback form.
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.
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.