Skip to content
NewMeet RADAR, the AI agent

See what users want fixed next.

See which complaints are growing, what changed after a release, and where users struggle. AppReply groups reviews by topic and links each finding to the reviews behind it, so you can check the evidence before choosing what to fix.

Full Analytics included on Pro

Topical analysis: 22 review topics sized by volume, from General satisfaction at 5.1K reviews down to Login and accounts, each with its own volume trend line.

Trusted by teams behind apps with 1.7B+ combined downloads

VivaldiKFCRappiStoriMatryoshkaPromovaARdrawingMapy.com

See the complaints behind a rating drop.

Our review analytics, called RADAR, groups feedback into topics such as crashes, payments, or login problems. See how often each issue appears and whether feedback is positive or negative. Open a topic to read what users actually said.

A review topic opened to its evidence: 476 reviews at 2.5 stars, the volume trend, the country breakdown, and the five reviews behind it.

Give your next product meeting a clear starting point.

Share a weekly summary of the topics that changed, with links to the original reviews. Start with common topics or add your own feature names, so the team can discuss specific problems without reading the whole inbox.

The period summarised in words: the four themes that ran through it, then what improved and what regressed against the period before.

Customer feedback analysis, from trend to problem.

Compare releases and shape the topics to your product. Every finding keeps a path back to the customer feedback behind it.

Coming soon

Ask questions in plain language

Ask what changed since your last release or what users in one market keep mentioning. Read the answer, then open its linked reviews to check the details.

A plain-language question asked of the feed, answered in four themes with the share of reviews behind each and a link to the sample reviews.

Five app stores

App StoreGoogle PlaySamsung Galaxy StoreHuawei AppGalleryRuStore

Where the brief lands

SlackMicrosoft TeamsTelegramDiscord

Custom topics and review sentiment

Start with a set of common review topics or add your own features and product terms. Check which reviews belong to a topic and correct mistakes within your account.

Thirty-three review topics in one manager, the team’s own ones such as buggy lobbies and cannot join matches sitting beside the built-in set, each with its own toggle.

App version comparisons

Compare feedback across two app versions. See whether crash complaints fell after a fix, or whether a new issue appeared with the latest release.

Six app versions compared: reviews, sentiment, rating and the top category for each, with the change against the period before.

Investigate once. Keep the team updated.

  1. Choose the apps, dates, ratings, and languages you want to investigate. Summarize that selection or ask about an issue such as login failures.

    Review analytics for the period: average rating, 8.5K reviews, five-star rate, sentiment and reply effect, with the period summarised in words beside the response-metric trend.
  2. Start with one complaint and find reviews about the same issue, even when users describe it in different words. See whether others have run into the problem too.

    Fifteen reviews found from one complaint by semantic similarity, each scored for how closely it matches and carrying the topics it shares.
  3. Break ratings and rating changes down by country and language. Find the market behind a drop that would be hard to spot in the overall average.

    Store ratings split by language across ten markets, from German at 4.04 down to Korean at 3.21, each with its change over the period.
  4. Add competing apps from Google Play and the App Store to explore their reviews with the same filters you use for your own. Competitor reviews trigger alerts only when a rule includes those apps.

    Three competing games attached to the two owned listings, each with its own analytics, reviews and alert routing.
  5. Send daily, weekly, or monthly summaries to your team’s channels. Reports keep arriving on your schedule, with links to the original feedback.

    A weekly report being built: the cadence set to Monday to Sunday, four of eight sections switched on, and the email preview beside it showing the TL;DR, the period stats, the urgent issues and the themes behind them.

Start with a question about your latest release.

Use the review history loaded for your app to explore feedback and check your first finding.

Full Analytics included on Pro

  1. Connect an app and let its history load

    AppReply loads available review history for your app. You can start exploring that feedback while new reviews arrive.

  2. Start from the common topics

    Use the 15 built-in topics to see the most common complaints and positive feedback.

  3. Add topics for your own features

    Create topics for your feature names and user journeys. Correct topic assignments when needed; those corrections stay in your account.

  4. Compare releases and open the evidence

    Compare topics across app versions, then open the reviews behind a change before you take it to the team.

  5. Send the brief where the team reads it

    Route the weekly summary to the channel that owns the product, so the analysis reaches people who are not opening a dashboard.

FAQ

Questions about analytics

How do you analyze thousands of app store reviews?

Not by reading them. AppReply groups every review into topics such as crashes, payments, or login problems, scores whether the feedback is positive or negative, and tracks how each topic moves week to week. You read the shape of the feedback first, then open a topic to see the reviews it was built from before deciding anything.

Does AppReply analyze review sentiment?

Yes, and it stays attached to the topic rather than sitting on its own. Each topic carries the sentiment of the reviews inside it, its average rating, and its change against the period before, so you can tell a topic that is growing because users like it from one that is growing because it is broken.

Can we analyze competitor app reviews too?

Yes. Add competing apps from Google Play and the App Store, then explore their reviews with the same topics and filters you use for your own. Competitor reviews trigger alerts only when a rule explicitly includes those apps.

What is AppReply RADAR?

RADAR is the name of AppReply’s review analytics. It groups reviews by topic, shows whether feedback is positive or negative, and compares apps, releases, and markets. You can open a finding to read the reviews behind it.

Can we analyze topics specific to our product?

Yes. Start with a set of common app-review topics, then add custom topics based on your own product language and review history.

Are our corrections shared with other customers?

No. Your topic corrections stay within your account. Customer data is not used to train shared AI models.

Find out what your latest reviews are telling you.

10-day Pro trial · No credit card