How to write app feedback a developer can act on
"Nice app, works fine" costs the developer time and teaches nothing. Good test feedback is short and specific. Use these four parts for every finding.
1. What you tried
Name the screen and the action: "Tapped Sign up with a new email, then pressed back."
2. What you expected
"I expected to return to the welcome screen."
3. What happened
"The app closed. Reopening it showed a blank screen for about five seconds."
4. Where it happened
Add the device, the Android or iOS version and the app version. A bug that only appears on one phone is still a bug, and the developer cannot find it without these details.
Include what worked
Tell the developer what felt good, especially in onboarding. That tells them what to keep when they change things.
Skip the verdict
Leave out stars and "I would pay for this". Report what you saw. On AppReviewX feedback is private, at least 50 characters long, and the owner pays stars only for feedback they can use.
Need testers for your app? Open a test group on AppReviewX. Start free