The App Review Glossary: 30 Terms Every Developer Should Know
A plain-English app review glossary: 30 definitive terms every developer should know, from recency-weighted rating to review gating and developer response.
The Argus Team
Reply Argus
Your store rating is not a simple average. That single fact — both the App Store and Google Play weight recent reviews more heavily, a shift Google confirmed at I/O 2019 — trips up more developers than any other term in this list, and it's term one of thirty. Most app review vocabulary lives in half-remembered blog posts and console tooltips, so two people can read the same dashboard and picture completely different mechanics.
This is the fix: thirty terms, defined in a sentence or two each, accurate to how Apple and Google actually behave in 2026. Skim it, bookmark it, or read it end to end. Where a term deserves a full playbook, there's a link. Where a number is unsettled, we say so instead of inventing one.
Rating math and the algorithm
Start here, because almost every downstream decision — whether to reply, when to prompt, how to read a dip — depends on how the number is actually built.
- Star rating — the 1-to-5 score shown on your listing. It's the headline metric, but it's a summary of many underlying reviews, not a raw mean of every rating you've ever received.
- Recency-weighted rating — since Google I/O 2019, both stores emphasize recent reviews over old ones, so a rough patch this month drags your visible score down faster than a five-year-old rave props it up. This is why momentum matters more than lifetime totals. We break down the full mechanism in [how your app star rating is calculated](/blog/how-is-your-app-star-rating-calculated).
- Lifetime (cumulative) rating — the all-time average across every rating, shown in some console views. It moves slowly and rarely matches the recency-weighted number a shopper sees on the storefront.
- Rating distribution — the histogram of how many 1★, 2★, 3★, 4★ and 5★ ratings you hold. A 4.3 built on a fat middle behaves very differently from a 4.3 split between fives and ones.
- Rating reset — Apple lets a developer reset the app's summary rating when shipping a new version, wiping the visible score to start fresh. Google Play offers no equivalent manual reset, so a Play rating is something you recover, not clear.
- Review velocity — the rate at which new reviews arrive over a window. Because ratings are recency-weighted, high velocity means your recent sentiment is doing most of the talking, for better or worse.
Developer response terms
The reply is the one lever you fully control. These are the words for what it is, how it's measured, and what it moves.
- Developer response — the public reply you post under a review from App Store Connect or Play Console. The reviewer is notified when you post it, and on both stores it appears beneath their review for everyone to read. Google I/O 2019 reported an average +0.7 star lift for developers who respond.
- Response rate — the share of your reviews (or of a segment, like all sub-3★) that received a developer response. It's the honest measure of whether you're actually showing up or just triaging the loudest.
- Time-to-first-reply — how long between a review posting and your response going live. It matters more than it looks: a reply that lands while the reviewer still remembers writing feels alive, three weeks later feels automated.
- Reply character limit — Google Play enforces a hard 350-character cap on developer replies. Apple publishes no official limit; community testing suggests a few thousand characters, but shorter reads better on both. Fitting warmth into 350 is a craft of its own.
- Review update — when a reviewer edits their rating or text after the fact, often after a reply resolves their issue. This is the event a good response is quietly fishing for.
- Rating recovery — the act of nudging an updated review upward. Academic work backs it: McIlroy et al. (IEEE, 2017) found 38.7% of rating changes after a developer response were increases, and Hassan et al. (4.5M reviews) found responding made users roughly 6× more likely to raise their rating (4.4% vs 0.7%).
Terms are easier to trust when you see one in the wild. Here's a developer response doing rating recovery — mirroring the specific complaint, owning it, and leaving a door open for the review update.
App keeps logging me out every few hours. Frustrating when I'm mid-task.
The every-few-hours logout is a token-refresh bug we shipped in 4.2, and you're right to be annoyed — mid-task is the worst possible moment for it. A fix is in the build going out this week. If you'd rather not wait, email us and we'll flip your account to the patched flow today. Sorry for the friction; it shouldn't do this.
That reply names the bug, gives a timeline that's true, and offers an out — the shape research keeps rewarding. For the full method, see [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews) and the evidence in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).
Discovery and ASO terms
Reviews aren't just feedback; they feed the machinery that decides who finds you and whether they tap install.
- ASO (App Store Optimization) — the practice of improving your listing to rank and convert better: title, keywords, screenshots, and yes, ratings and reviews, which factor into both ranking and the decision to install.
- Featured / helpful review — the reviews the store surfaces at the top of your listing. Apple weights ones other users mark helpful; a wall of thoughtful replies under them is cheap, durable social proof.
- Review sort order — how reviews are ordered on the listing. The App Store offers Most Helpful, Most Favorable, Most Critical, and Most Recent; Play offers Most Relevant, Newest, and by rating. Shoppers read the criticals, so that's where a calm reply earns the most.
- Ratings prompt (in-app review) — the native rate-this-app card you trigger via Apple's SKStoreReviewController or Google Play's In-App Review API. Both are quota-limited and system-throttled; you can't spam it, and you can't guarantee it shows.
- Review-to-install conversion — the lift in installs attributable to a stronger rating. Apptentive found moving from a 3★ to a 4★ average can raise conversion by roughly +89%, which is why a fraction of a star is worth real work.
Moderation, fraud, and policy
This is the part with rules you can actually break. Know the lines, because both stores enforce them and the penalties reach the whole listing.
- Review gating — routing happy users to the public store while diverting unhappy ones to a private form. It's a violation of Apple's guidelines and Google Play policy; you must use the native prompt for everyone. Filtering by sentiment before the store is the version that gets apps in trouble.
- Review bombing — a coordinated flood of negative reviews, often over a policy change or controversy rather than the app's function. Recency-weighting makes it hurt fast; the store may filter obvious campaigns, but not always.
- Fake reviews — reviews from bots, review farms, or accounts that never used the app, planted to inflate a rating. Both stores detect and remove them, and buying them risks removal of the app itself.
- Incentivized review — a rating exchanged for a reward, discount, or unlock. Prohibited on both stores; you may ask for a review, never trade for one.
- Report / flag a review — the console action to ask the store to remove a review that breaks policy (spam, profanity, off-topic, or a clear conflict of interest). It's a request, not a delete button, and a genuine but harsh review won't qualify.
Signals researchers track
When you move past single replies to reading reviews at scale, this is the vocabulary of the patterns.
- Sentiment analysis — scoring review text as positive, negative, or neutral to see the mood behind the stars. A 4★ can hide a real complaint; sentiment catches what the number rounds off.
- Theme / topic clustering — grouping reviews by what they're actually about (crashes, pricing, a missing feature) so ten scattered gripes become one prioritized problem. This is how a review inbox turns into a roadmap.
- Review success predictors — the factors that make a reply more likely to earn an update. Srisopha et al. (EASE 2021) ranked them: length-ratio of reply to review mattered most, then content similarity, then timeliness, then politeness. Substance beats speed, and both beat mere courtesy.
Tooling and automation terms
The last six are the words for doing all of the above without living inside two consoles. Some of them describe how [Reply Argus](/features) works, because this is the exact problem it exists to solve — watching both stores and drafting grounded replies so the definitions above become a workflow instead of a wish.
- Review inbox — a single feed that pulls App Store and Google Play reviews together, so you triage one stream instead of tabbing between two consoles that each notify differently.
- Auto-publish rule — an opt-in rule that posts a reply automatically by rating, keyword, language, or store (for example, thank every 5★ in its own language), while anything risky still waits for your approval. Approve-by-default is the safe posture; auto-publish is the explicit exception you choose.
- Knowledge-base grounding — feeding replies from a source of truth (your past approved replies, store listing, marketing page) so a draft cites what's real about your app instead of guessing. It's what keeps an automated reply from promising a feature you don't have, and drift detection flags when those sources contradict each other.
- Localization / in-language reply — answering a reviewer in the language they wrote in, natively, not as a translated English line. A huge share of app reviews aren't in English, and a warm reply in their tongue reads as a person, not a queue. See [replying in any language](/blog/reply-to-app-reviews-in-any-language).
- MCP connector — a Model Context Protocol bridge that lets an AI assistant (Claude, ChatGPT, Cursor) operate your review workflow through defined tools. It's how you run reviews from the chat window you already work in; more in [reviews over MCP](/blog/app-reviews-mcp).
One glossary, one caveat on limits
Two numbers here are firm and two are not. Play's 350-character reply cap and the +0.7-star and +89% figures come from cited public sources. Apple's reply character limit is not one of them — Apple publishes no official limit, so treat any hard number you see quoted as folklore, not fact. When in doubt, write shorter.
One term worth its own note: the rules aren't identical across stores. Reply length, prompt behavior, rating reset, and what you can flag all differ between Apple and Google, and the differences bite when you assume parity. We keep a running comparison in [reply rules for every app store](/blog/reply-rules-for-every-app-store).
Frequently asked
- What is a recency-weighted rating?
- It's a store rating that emphasizes recent reviews over old ones. Since Google I/O 2019, both the App Store and Google Play weight newer reviews more heavily, so your visible score reflects how the app is doing lately rather than a flat average of all time. A rough month can pull it down faster than years of praise can hold it up.
- What is a developer response to an app review?
- It's the public reply a developer posts under a review from App Store Connect or Play Console. The reviewer gets notified, and the reply shows beneath their review for all future readers. Google I/O 2019 reported an average +0.7-star lift for developers who respond, and it gives you a chance to earn a review update.
- What is review gating and is it allowed?
- Review gating is filtering users by sentiment before the store — routing happy people to leave a public review while diverting unhappy ones to a private form. It's against Apple's App Store guidelines and Google Play policy. You must offer the native review prompt to everyone, regardless of how they feel.
- How long can a developer reply to an app review be?
- Google Play enforces a hard 350-character limit on developer replies. Apple publishes no official limit; community testing suggests a few thousand characters, but nothing is confirmed. Aim to fit Play's 350 and your reply works cleanly on both stores — shorter reads better everywhere.
- Does an app store rating reset when I release a new version?
- On Apple, you can choose to reset your app's summary rating when you ship a new version, which clears the visible score. Google Play offers no manual reset — a Play rating is something you recover through new positive reviews over time, not something you can wipe.
- What is an MCP connector for app reviews?
- An MCP (Model Context Protocol) connector lets an AI assistant like Claude, ChatGPT, or Cursor operate your review workflow through defined tools — reading reviews, drafting replies, publishing under your rules — from the chat window you already use, without opening two store consoles.
Now you share a vocabulary with everyone who reads your store metrics, which is most of the work. The rest is doing it every day across two stores and a dozen languages without the specific replies slipping during a busy week. That's the gap [Reply Argus](/features) closes: it watches your App Store and Google Play reviews in one inbox, drafts a grounded reply to each in the reviewer's own language, and lets you approve by default or set opt-in auto-publish rules for the safe ones. [Start free — no card](/signup), and it drafts your first reply in minutes for you to approve.
Try it
Let Argus draft your next reply.
Watch it answer a real review in your voice. 10-day trial, no card to begin.
Keep reading
App Store Reviews Not Showing? The Full Fix List for Apple and Google Play
App Store or Google Play reviews not showing? Here's every real cause — moderation delay, wrong country storefront, filtering, rating lag, cache — and the fix.
Read moreAre App Store Reviews Fake? How to Spot Them and What to Do
Yes, some App Store and Google Play reviews are fake — but fewer survive than you think. How to spot them, and what to do when they hit your app.
Read more