In this guide
Structured feedback uses fixed fields: ratings on a scale, choices, a category. Open feedback is free text. They answer different questions, and you need both.
What each is good at
| Structured | Open | |
|---|---|---|
| Strength | Easy to compare and count | Shows things you did not think to ask |
| Weakness | Only covers what you asked | Hard to sort, uneven quality |
| Use it to | Spot patterns, rank issues | Understand why, find surprises |
When to use which
- Structured first when you have several testers and want to see where they agree: which screen, how severe, which device.
- Open when you do not yet know what is wrong, or need the reason behind a number.
- Both together is the default. A field tells you where and how bad; the text tells you why.
Why the platform asks for both
AppReviewX feedback is private and structured. Fields keep reports comparable, and free text keeps the detail. A report with only text is hard to compare; a report with only fields lacks context.
Example with both
Example (made up):
- Area: Sign-up
- Severity: blocks me
- Device: phone, Android
- What happened: "After entering my email the button stayed gray. I waited, then restarted. The second time it worked, but I almost quit."
From the fields you can count how many testers hit sign-up problems. From the text you see the cause may be a slow response without a loading indicator.
Tips
- Keep fixed fields few. Every extra field lowers the answer rate.
- Always leave one free-text box, even in a form made of choices.
- Add an "other" choice instead of forcing a wrong one.
- Read the open answers before you decide anything based on numbers alone.
Related
- Hub: App feedback for developers
- User interviews for mobile apps
- Interview questions for your app
- Article: How to give useful app feedback
Get started. 1 feedback = 1 credit, new accounts start at 0.