AppForShareCreate a free account

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.

Start freeSee plans

Example

Bug, In app

  • ScreenCheckout
  • BuildiOS 2.5 (121), matched by build number
  • App infouser=test-14, cart=3 items
  • Attached2 screenshots
https://appforshare.io/feedback/<token>?platform=ios&version=2.5&build=121&screen=Checkout

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

  1. 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>.

  2. 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 or a shake handler.

  3. 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.

  4. 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.

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

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.

Read next

Try it on your own app

Free account in a minute. Pro starts with a 7 day free trial.

Create a free accountPricing

More features