Distinguish a star score from a written review
A star score summarizes an opinion without necessarily explaining its cause. A written review can describe a problem, expectation or favorite feature, but it may still omit the build and steps needed to investigate. Keep both in the source context. One review may accompany a rating, so adding rating count and review count can double-count the same contribution rather than measure two independent audiences.
When reviewing store data, read the platform's definitions for the displayed metric and the period or territory it covers. Do not assume every dashboard uses the same aggregation. For your own product notes, label rating count, written-review count and average separately. If you do not know how a service produces a number, mark that limitation before using it in a comparison or a public claim.
Understand what private reports add
A private report should give the task, starting state, build, device and observed outcome. It can include an optional opinion, but task evidence is its main value. A person who reports that a saved note disappears has given you an actionable issue even without stars. A person who writes great app without describing an attempted task may have given an opinion but little test evidence.
RateMyApp funds approved private reports with testing credits and lets participants optionally leave community stars. Count approved reports and community ratings separately. Completion of a report does not guarantee a rating. If a score and a report seem inconsistent, investigate the experience before choosing which one to believe. Someone can like the overall concept while encountering a serious failure in the journey you asked them to test.
Use each signal for a different decision
Use written comments to identify themes and questions, private task reports to investigate a journey and ratings to monitor a clearly labeled opinion signal. None alone establishes full product quality. A rising average does not tell you which bug was fixed; a detailed defect report does not tell you how common it is in the entire customer population. Choose additional evidence based on the uncertainty behind your decision.
For a small sample, keep counts beside averages and preserve the original observations. Compare the same build and task when possible. If you change the audience between rounds, record that change rather than attributing every score movement to a redesign. The free rating calculator can illustrate a simple weighted-average scenario, but it does not reproduce every store's display process or predict future customer opinions.
Write public claims with the source attached
If you share a community score, name the community and avoid making it look like a store rating. If you summarize private research, identify the task and scope rather than presenting it as an independent certification. Do not manufacture a testimonial from a bug report or publish private feedback without appropriate permission. A precise description is more useful to a potential customer than a large unlabeled number.
Keep public rating requests voluntary and independent of testing rewards. A private report, a public review and a store install are different actions with different rules. Ask users for an opinion only through an appropriate workflow and accept criticism. The next step is to label your own metrics clearly, inspect the comments behind the numbers and select a concrete product question for further testing.
Working example
Illustrative dashboard: a round receives four approved private reports and two optional community ratings. The owner records four reports and two ratings, not six reviewers. A store dashboard separately shows its own public rating and written-review counts. The owner does not add those numbers to the community average. One private report includes a saved-data failure; another explains a confusing label. The team prioritizes those observations and keeps the community scores as a separate opinion signal. These fictional counts demonstrate correct labeling, not customer activity, rating uplift or a claim about a store's exact aggregation method.
Your next steps
- Label star counts, written reviews, private reports and community scores separately.
- Preserve the build, task and original observation behind a useful report.
- Read averages with counts and source definitions before comparing rounds.
- Attach the source to public claims and keep review requests voluntary.
Questions about this guide
Does every app rating include a written review?
A star score and a written comment are different contributions. Do not assume every rating includes a written review or add the two counts as if they represent separate people.
Is a private testing report a public app review?
No. A private testing report records an attempted task and observations. Public store reviews are submitted independently through the store, and community scores belong to the community that collected them.
Official sources
Sources checked October 4, 2026. Review the current provider documentation before acting on requirements.
Turn the next test into something useful.
Publish a focused brief on RateMyApp. Credits fund approved private reports; public store reviews are voluntary and unrewarded.
List your app for feedback