Why a report form?
When something goes wrong, users who can't find a way to tell you write a store review instead, and a review can't hold a screenshot or tell you which version they use. A report form inside the app catches the problem first, with what you need to fix it: what happened, a picture of it, and the app version, OS and device, filled in by the app instead of asked of the user.
What you get
- Three topics: something's wrong, feedback and questions, which you can filter in the panel.
- Up to three screenshots, shrunk in the browser so they upload fast on mobile data, with their location data removed.
- Device details from your app's link, or from the browser when the form is opened on the web.
- An optional email so you can reply; only you see it.
- An inbox in your panel: new reports are marked, with a count on your site list; mark them resolved or delete them.
- In your users' language: the form speaks nine languages, right to left for Arabic and Hebrew.
- Spam checks: Cloudflare Turnstile and limits per visitor and per site.
Privacy
Screenshots are stored privately and served only to you. The form tells users that their message, screenshots, email and device details go to the app's developer. Mention the form in your app's privacy policy; the privacy policy generator can help.
Questions
Does it work on my own domain?
Yes. If your AppPage site uses your own domain, the form is at yourdomain.com/report.
Can users suggest features too?
They can send feedback here. For ideas others can vote on, add the feature request board to the same site.
Will I get an email for each report?
Not yet. New reports show in your panel; email alerts are planned.