How to Analyze App Store Reviews for Better App Insights

Yusuf Yılmaz · November 16, 2026 · 8 min read

Short answer

Read your reviews country by country, give every low-rated review one or two short topic tags, and count the tags per country and per app version. A complaint that keeps coming back from different people, in different weeks or countries, is a product signal; a single review is a data point. Fix the top recurring problems first, mention the fix in your release notes, reply to the affected reviews in App Store Connect, and check whether those tags shrink after the release.

Why reviews matter

Reviews are where people who downloaded your app tell you, unprompted and in their own words, what works and what doesn’t. They are also public. Apple says individual ratings inform your app’s summary rating, which appears on your product page and in search results, and that ratings and reviews can influence how your app ranks in App Store search. Apple doesn’t say how much.

So a recurring complaint costs you twice: it is a problem in the product, and it sits on your product page for every potential user to read. In some storefronts the product page also shows a reviews summary that Apple generates with large language models, and themes repeated across many reviews are what such a summary picks up.

Ratings vs written reviews

People can rate your app from 1 to 5 stars, and for iOS apps they can also write a review. Treat these as two different signals:

  • A rating is a number. It moves your overview rating but says nothing about why. Through Apple’s standard in-app prompt, people submit a rating and can optionally write a review, so many of your ratings may come without any text.
  • A written review carries a reason. It is the part you can analyze, but it comes from the people who chose to write.
  • Both can change. When someone edits a rating or review, the latest version is shown, and a new submission replaces their previous one. A complaint you read last month may have been updated since.

Use ratings to notice that something changed and written reviews to find out what. If you ask for ratings in your app, Apple’s SKStoreReviewController lets you prompt up to three times in a 365-day period, and Apple advises asking when people are most likely to feel satisfied, such as after completing a task. Ask right after an error or a paywall and you are mostly collecting opinions about that moment.

Why country-level analysis matters

Apple shows a separate overview rating for each country or region of the App Store, and the country of a rating reflects where the customer first got the app. A 4.7 in the United Kingdom and a 4.1 in Germany are two separate numbers that people in those countries see, and a global average hides the difference.

Countries differ for reasons a global view won’t show: a clumsy translation, a price that feels high in one market, a date format that’s wrong for local users, or a strong local competitor. Why storefronts behave so differently is covered in understanding App Store rankings across countries; for reviews, the practical consequence is to analyze each priority country on its own. In App Store Connect, open Ratings and Reviews for your app and choose the country or region from the menu at the top left.

Identifying recurring complaints

You don’t need software to start. A spreadsheet and a fixed method are enough:

  1. Pick a period (for example the last eight weeks) and your three to five most important countries.
  2. Read every 1- and 2-star review in that period and give it one or two tags from a short list. Keep the list under about fifteen tags so counts stay meaningful.
  3. Tag the problem, not the mood: “reminder doesn’t fire”, not “angry user”.
  4. Write tags in one working language. “Ads”, “Werbung” and “publicité” all go under the same tag.
  5. Count tags per country and keep one example quote per tag.
TagTypical wording (translated) US DE UKTotal
Ads interrupt reading“Too many ads, I can’t see my week.”94619
Paywall / price“Everything is paid now.”37818
Wrong pregnancy week“It says week 12, I’m in week 13.”1067
Data lost after update“All my notes are gone.”2114
Crash on launch“Closes as soon as I open it.”0101
Illustrative example with made-up numbers, not real data: 1- and 2-star reviews of Meyu: Pregnancy Tracker over eight weeks. One review can carry up to two tags.

Read it row by row. Ads show up in every country, so they are a product-wide issue. The paywall complaints are concentrated in Germany and the United Kingdom, which points to price or communication in those markets. “Wrong pregnancy week” comes almost entirely from the United Kingdom, which smells like a bug in one locale’s date handling rather than a design problem. Data loss is rare but serious, which brings us to frequency versus severity.

Patterns in low-rated reviews

Most 1- and 2-star reviews fall into a few recognizable shapes, and each points somewhere different:

  • “It used to work.” A regression. Check which version it started with.
  • “Not what I expected.” Your product page promised something the app doesn’t do. Compare the wording with your name, subtitle and screenshots.
  • “Everything is paid.” Paywall timing or how clearly you explain what is free.
  • “I lost my data” or “I can’t log in.” Trust problems. Treat them as urgent even at low counts.
  • Download or billing problems. Apple says to direct these reviewers to Apple Support.
  • Offensive content or spam. Use Report a Concern in App Store Connect instead of replying; the reviewer isn’t notified.

Also read 3-star reviews. They often come from people who like the app and name the one thing holding them back.

Comparing reviews across app versions

In App Store Connect you can filter reviews by app version, by star rating, and by whether they were edited or responded to. That makes it possible to ask: did a complaint start, grow or disappear with a specific release?

Compare shares, not raw counts. A version that has been live for three weeks will always have more reviews than one released three days ago. “Paywall” tags in 20% of low-rated reviews for one version and 5% for the previous one is a meaningful comparison; 12 versus 4 reviews on its own isn’t. Use equal periods after each release and remember that something else may have changed at the same time; the same discipline is covered in how to measure ASO metadata changes.

When you release a new version you can also reset your overview rating. Apple recommends using this sparingly, and its documentation is clear about the limits: the reset applies to all countries or regions at once, written reviews stay on the App Store, and once the version is released you can’t restore the previous rating. A reset doesn’t hide complaints.

Individual complaints vs recurring problems

Sort what you find by two questions: how often does it come up, and how bad is it?

  • Recurring and severe (crashes, data loss, billing confusion): fix first.
  • Recurring and mild (an annoying screen, a missing small option): plan it into the next releases.
  • One-off and severe: investigate and reply asking for details through your support channel. One detailed crash report can be the first of many.
  • One-off and mild, or a matter of taste: note it and move on. Don’t rebuild the app for one loud review.

A useful working definition of “recurring”: the same tag from different people, in more than one week, and ideally in more than one country. Count feature requests the same way. A request that shows up across countries is worth more than a single eloquent one.

Turning feedback into product improvements

  1. Write a problem statement with evidence. “Since 3.2, the paywall is the most common tag in low-rated German and UK reviews; people expect the weekly content to stay free.”
  2. Decide how you’ll know it worked before you build: for example, that tag’s share of low-rated reviews in the same countries after the fix.
  3. Ship and say so. Apple recommends mentioning fixes for issues raised in older reviews in your release notes and considering a reply to the relevant reviews.
  4. Reply in App Store Connect. Responding requires the Account Holder, Admin or Customer Support role. The reviewer is notified and can update their review, only one response per review is shown, and it can take up to 24 hours to appear. Apple asks for concise, respectful replies without marketing language.
  5. Recount after the release with the same tag list and compare.

Don’t promise a fix in a public reply unless it’s actually planned.

Monitoring competitor reviews

Your competitors’ low-rated reviews show what their users looked for and didn’t find. Pick the three to five apps that keep appearing next to yours in search (finding keyword gaps walks through how to identify them) and tag their 1- and 2-star reviews with the same list you use for your own.

Say Competitor A’s low-rated reviews in Germany keep mentioning ads, and Competitor B’s complain that exporting data is paid. If Meyu handles either one better, say so clearly on your product page. If your own tally shows the same complaint, it is an unmet need in the whole category. Reviews show what bothers the people who chose to write, not how many users a competitor has.

If you use AsoGlass, it collects reviews for your apps and your competitors from every country you track into one list, with flag, stars and date, and highlights words that keep coming up in low-rated reviews. Those are simple word counts, not AI or sentiment analysis, and it doesn’t suggest product changes; the tagging and deciding stay with you. You get a notification when your average rating changes. The list covers recent reviews for each country, so very old reviews may not appear, and replies are made in App Store Connect, not in AsoGlass. Other common questions about the app are answered in the FAQ.

App Store reviews feature →

FAQ

Can I see reviews from every country in App Store Connect?

Yes. In Ratings and Reviews, choose the country or region from the menu at the top left. You see one country or region at a time.

Does resetting my overview rating remove negative reviews?

No. Apple says written reviews continue to display on the App Store after a reset, and the reset applies to all countries or regions at once.

Do ratings and reviews affect search ranking?

Apple says they can influence how your app ranks in App Store search. It doesn’t publish how much weight they carry.

Should I reply to every review?

Reply where it helps. If you can’t reply to all of them, start with the lowest ratings and with reviews about technical issues in the current version, as Apple suggests.

How many reviews do I need before tagging is useful?

There’s no fixed number. If you only get a handful of written reviews a month, use a longer period or combine countries that share a language, and treat the counts as hints rather than proof.

Sources Apple Developer, “Ratings, reviews, and responses” App Store Connect Help, “Ratings and reviews overview” App Store Connect Help, “View ratings and reviews” App Store Connect Help, “Respond to reviews” App Store Connect Help, “Reset an app overview rating” Apple Developer, “App Store search”
Competitors· 9 min read
How to Find Keyword Opportunities Through Competitor Analysis Discover how to identify keywords where competing iOS apps rank but your app does not, and turn those gaps into a short list of research opportunities.
Countries· 10 min read
Understanding App Store Keyword Rankings Across Countries Understand how App Store search rankings vary by country, why local search results matter, and how to evaluate international ASO performance.
Measurement· 10 min read
How to Measure ASO Metadata Changes Learn how to evaluate App Store name, subtitle and keyword changes using keyword rankings, historical comparisons and App Store Connect data.