In this guide
The developer whose app you test is probably a person like you, often working alone, who will read your words closely. Respectful feedback is not softer feedback. It is feedback that is specific and aimed at the problem.
Why tone matters
On AppReviewX, developers test each other's apps. The person receiving your feedback today may be writing yours tomorrow. You earn credits by writing feedback and spend them to get feedback on your own app, so you are on both sides. Write what you would want to read.
Feedback also only helps if it is read. A hostile message gets defended against; a clear one gets fixed.
Do and don't
| Do | Don't |
|---|---|
| Describe what happened: "The list is empty after I log out and in again." | Judge the person: "You clearly didn't test this." |
| Say what you expected | Only say "bad" or "useless" |
| Separate fact from opinion: "I couldn't find the settings" vs "I'd prefer a darker theme" | Present taste as fact |
| Give a suggestion when you have one, and mark it as one | Demand a solution or a deadline |
| Mention what works if it does | Pile on every small thing in one angry block |
| Report one problem per entry | Mix five problems in a single paragraph |
| Stay on the app | Comment on the developer's skill or plans |
How to phrase hard things
- Instead of "This screen is confusing", try "I didn't know what to tap first. A label on the top button might help."
- Instead of "It crashes all the time", say "It closed twice when I opened the camera. Both times right after I tapped Allow."
- If you are unsure it is a bug, say so: "I'm not sure if this is intended, but ..."
Keep it private and fair
On AppReviewX your feedback is private: it goes to the app's owner. Keep it that way. Do not post a developer's unfinished work or your findings elsewhere without being asked. Store ratings are voluntary and unpaid, and nobody should push you to leave one, in either direction.
A quick check before sending
- Could this sentence be said to the developer's face?
- Is every complaint backed by what I actually saw?
- Would I know what to do if I received this?
If you can answer yes three times, send it. 1 feedback written = 1 credit.
Next steps
Test an app and earn credits. For a fuller guide to being useful, read how to give useful app feedback.
Related:
- Become an app beta tester
- Testing beta apps safely: privacy tips
- Which permissions to grant in a beta app