Mine reviews free

App feedback: where to collect it, how to read it, what to do next

By the App Review Miner team · November 9, 2026 · 4 min read

Short answer: good app feedback comes from three places: store reviews (public, many users, any competitor), in-app feedback (private, in the moment) and direct conversations (deep, few users). Collect from all three, ask at the right moment without leading questions, group what you hear into themes, and fix the biggest problems first. Then tell users you did.

Where app feedback comes from

Source Strength Weakness
Store reviews Public, many users, also for competitors Skewed to strong opinions
In-app feedback form In the moment, private, can include context Few users use it
In-app rating prompt Many ratings, low effort Little detail
Support tickets Concrete problems Mostly about failures
Interviews The “why” behind behaviour Slow, small samples

Asking for feedback without biasing it

In-app review prompts

Google’s In-App Review API shows a rating card inside your app. Google’s guidelines (Android Developers, read 12 November 2026) are strict:

  • trigger it after users have experienced enough of the app to give useful feedback;
  • don’t prompt excessively;
  • don’t ask questions before or while showing it, such as “Do you like the app?” or “Would you rate this app 5 stars?”;
  • show the card as it is, without changing its design or adding overlays.

A time-bound quota limits how often the dialog can appear, and Google advises against a button that triggers it, because users who hit the quota would see nothing. Send those users to the Play Store page instead.

Feedback forms

Keep them short: one open question (“What’s the one thing you’d change?”) beats ten checkboxes. Attach device and version information automatically so users don’t have to type it.

Reading feedback: from noise to themes

  1. Pool it. Put store reviews, form answers and tickets in one place, translated into one language.
  2. Group it into pain points, feature requests and praise.
  3. Weigh it. Count mentions; on Google Play, use the helpful votes as a signal of agreement.
  4. Check the version. Play Console breaks ratings down by app version, so a problem introduced by a release is easy to spot.
  5. Keep quotes for every theme you act on.

Doing something with it

  • Fix the top pain point first, even if a feature request is more exciting.
  • Look for cheap wins: wording, defaults, a missing setting.
  • Say no clearly to requests that don’t fit, so you can stop tracking them.
  • Close the loop. Reply to reviews when you ship a fix: Play Console allows one public reply per review, and the user is notified. They can update their review.

Use competitors’ feedback too

Your competitors’ reviews are app feedback you didn’t have to collect. They show what users in your category expect and which weaknesses you could win on. App Review Miner reads the most helpful Google Play reviews of up to five apps in 26 countries and lists, per app, the pain points, requests and praise, with quotes, plus where competitors fall short.

A monthly feedback routine

  • Week 1: collect and group last month’s feedback.
  • Week 2: share the top three pain points and requests with the team.
  • Weeks 3–4: ship fixes, reply to the reviews they answer.
  • Repeat, and compare with the previous month.

Turning a theme into a fix (illustration)

Say your monthly review read shows a theme: “progress lost after the update”, mentioned in many recent one-star reviews across several countries, with high helpful counts. A useful way to move from theme to fix:

  1. Reproduce it: which app version, which devices? The Play Console version breakdown points to the release.
  2. Size it: how many reviews mention it, and how many users agreed with them?
  3. Fix and ship.
  4. Reply to the reviews that described it, saying it’s fixed in the new version.
  5. Watch next month’s reviews: the theme should shrink; if it doesn’t, the fix didn’t reach the cause.

What to do with feature requests

Not every request deserves to be built. For each one ask: does it fit the product you want to make, how many users ask for it, and do competitors’ users ask for it too? Requests that appear across several apps in your category are often the strongest signals, because they describe a gap in the whole market, not just in your app.

Common mistakes

  • Prompting for ratings on first launch. Users haven’t formed an opinion yet.
  • Leading questions before the review card, which Google’s guidelines forbid.
  • Only listening to the loudest channel. Balance reviews with in-app feedback.
  • Never replying. Users stop giving feedback that seems to vanish.

FAQ

How do I get more app reviews? Ask at a good moment with the in-app review card, make the app worth rating, and reply to reviews. Don’t pay or incentivise reviews.

Should I answer negative reviews publicly? Yes, briefly and helpfully. Future users read your replies too.

How often should I read reviews? Weekly for your own app if you ship often; monthly for a deeper read of themes and competitors.

What if feedback contradicts itself? It often does. Weight by how many users raise each point and by who they are, then test the change with a subset of users if you can.

Related: Voice of customer for app teams and Reviews in Play Console.

Sources

Keep reading