A one-star review feels concrete. It has a person, a complaint and a date. That makes it easy to overvalue. Store review samples are shaped by platform selection, product history, geography, version changes and who chooses to write. Treat each review as an attributable observation first.
Keep the source intact
Save the exact text, rating, visible author, app version, publication date or displayed date, region, source URL and collection time. Do not rewrite the quote into a stronger complaint. Separate the reviewer’s words from your interpretation.
Exact review: “The shared timer reset when I changed screens.”
Researcher interpretation: Possible interruption during screen switching. Current applicability is unknown until the app version and present workflow are checked.
Classify applicability, not sentiment alone
| State | What it means | Required check |
|---|---|---|
| Unreviewed | The source is captured but no current judgment has been made. | Read the exact review and identify its version/date. |
| Current complaint | The described problem still appears relevant after checking the current remedy. | Record what was checked and why it remains unresolved. |
| Addressed | Current product evidence shows a remedy. | Link the feature, release note or tested workflow. |
| Historical unknown | The evidence may be old and present behavior is not confirmed. | Keep it out of current unmet counts. |
| Excluded | The review concerns a different job, market or unsupported factual claim. | State the exclusion reason. |
Deduplicate conservatively
The same review may appear across pages or exports. Prefer a stable review ID scoped to app and storefront. Without one, avoid aggressive text matching that could merge different people. Report missing identities and explain the deduplication rule beside any count.
Do not turn themes into people
Theme grouping can make a sample easier to read, but ten mentions are not automatically ten distinct users and are never ten buyers. A repeated phrase also does not prove willingness to switch or pay. Use a theme to choose the next interview or current-product check.
Ask what would falsify the opportunity
For each apparent complaint, inspect the strongest current alternative. If an existing setting, free tool or documented workflow solves the issue, mark that evidence. If the complaint persists, seek a separate purchase case: who recently paid, what triggered payment, and why the existing remedies were inadequate.
Source references
- Apple: Ratings, reviews and responses — platform context for ratings and reviews.
- Apple App Store Connect API: customer reviews — authenticated first-party review resources.