A feedback button inside your test build, with no SDK
Every plan with an account. Screen recordings on Pro and Team
Testers find bugs inside the app, not on the install page. By the time they go back to the link to report one, they have forgotten which screen it was on. In-app feedback SDKs solve that, but they add a dependency, a sign in and a privacy review to every test build.
The in-app feedback link is a web address per project. Your test build opens it with the platform, version, build number and current screen, and the tester lands on the AppForShare feedback form for that build. Screenshots, drawing on them and the device facts work as on the install page. Nothing to install in the app.
Example
Bug, In app
- ScreenCheckout
- BuildiOS 2.5 (121), matched by build number
- App infouser=test-14, cart=3 items
- Attached2 screenshots
Made for
- Teams that want a Report a bug item in the debug menu of their beta
- iOS teams, since most in-app feedback SDKs for test distribution are Android only
- Apps tested by clients or staff who will not sign in to anything
What it ends
- Bug reports that say "on some screen" with no build number
- A feedback SDK added for the beta and removed before release
- Testers asked to sign in with Google before they can report
How it works
Step 1
Turn the link on
On the project's Testing tab, open In-app feedback and turn it on. You get an address like appforshare.io/feedback/<token>.
Step 2
Add a few lines
Copy the Swift, Kotlin, React Native or Flutter sample from the card. It opens the address with platform, version, build and screen, from a debug menu item, and the Shake to send sample opens it when the tester shakes the phone.
Step 3
Testers report
The form opens for the matching build in the tester's language, with the screen filled in. They write what happened and add screenshots.
Step 4
You triage
Reports land in the feedback inbox marked In app, with the screen and any extra info your app passed.
The right build, every time
The address takes platform (ios or android), version, build, screen and info. AppForShare picks the build with the same build number, then the same version, then the newest build of that platform. Screen (up to 80 characters) and info (up to 500, for example a test account or a feature flag) show on the report.
The in-app link stands in for the install page checks, since the app is already on the phone: a password, a private project or an expired install link do not block it. Turning the link off, or giving it a new address, stops the old one.
Shake to send, still without an SDK
The card has a second set of samples, Shake to send, that open the same address when the tester shakes the phone: motionEnded on iOS, the accelerometer on Android, react-native-shake for React Native and the shake package for Flutter. Each one is a few lines on top of the link sample, kept in test builds only.
The tester takes a screenshot first with the phone's own buttons, shakes, and attaches it in the form. There is no automatic screen capture, so nothing in the app records the screen and there is nothing extra for a privacy review.
Where reports go
Into the same inbox as install page feedback, with In app and the screen next to them. The owner email says the report came from inside the app. Sent to Linear or Jira, the issue carries the screen and the app info. With a crash dashboard link on the project (Pro and Team), each report also links to the crashes of that build.
Good to know
- Keep the button in test builds. It is a web page opened from your app, not a store feature.
- Screenshots are picked by the tester from the phone; the page does not capture the app screen itself.
- The same limits as install page feedback: 10 reports per address an hour and 100 per build a day.
- The in-app feedback link is a project setting, so it needs an account. Guest builds have the Send feedback card on the install page only.
Questions
- Is this an SDK?
- No. Your app opens a web address with a few query parameters. The samples on the card are about ten lines each.
- How is it different from Firebase App Distribution feedback?
- Firebase's in-app feedback is an Android SDK in beta, and the tester signs in with a Google account. This works on iOS and Android, with no SDK and no sign in.
- Which plan do I need?
- Any plan with an account. Screen recordings in a report are on Pro and Team.
- Can testers shake the phone to report a bug?
- Yes. Copy the Shake to send sample for Swift, Kotlin, React Native or Flutter from the card. A shake opens the feedback form for that build and screen; the tester attaches a screenshot they took with the phone's buttons.
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
- Tester feedback with screenshots
- 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