Analyze Reviews of Gaming Apps on App Store & Play Store

Mobile players review games the way they play them: often, quickly and with strong feelings. A review can be written a few minutes after the first session, after a frustrating level, after a purchase that felt unfair or after an update that changed something the player loved. Each one is short, but together they describe a game in more detail than any dashboard, because they say why players feel the way they do.

That makes App Store and Google Play reviews one of the most useful sources a game team has, and one of the most underused. Most studios read the latest reviews, reply to the angry ones and watch the star rating after each update. Far fewer read their own reviews, and the reviews of the games their players compare them with, as a body of research that shows which part of the game is costing them players and which update should come next.

This guide shows how a producer, designer or community manager at a small or mid-sized mobile studio can turn game reviews into real market research about their own game, its competitors and the genre it competes in.

Key Research Questions

Before collecting anything, it helps to know what the research is for. For a mobile game, the questions fall into three groups: questions about your own game, questions about the games your players compare you with, and questions about how the genre and its players are changing.

Your Game

The first questions follow the player. Where do new players lose interest: in the tutorial, in the first session, after the first difficulty spike or when progress starts to slow? What do players mention when they explain a five-star review, and what when they explain a one-star review? Which features keep coming up as the reason they play?

The second set is about balance and money. Do players feel the game is fair to people who do not pay? Which purchases, ads or timers do they accept, and which do they describe as the reason they stopped? After an update, what changed in the way they talk about the game?

Your Competitors

Your competitors are the games your players name, and the other popular games in your genre. What do their players praise that yours never mention? What makes their players leave, and could your game be where they go next? The reviews of competing games are as public as your own, and they show what players in your genre have come to expect before they ever open your game.

The Mobile Game Market

The third group concerns the genre. Which needs keep coming up that no game in the category seems to meet? How are expectations around ads, in-app purchases, offline play, social features and fairness changing? Which kinds of players are underserved? Players describe these shifts in reviews and community threads long before they show up in download charts.

Sources of Evidence

Evidence about a mobile game comes from four places: what your own players already tell you, what players of every game in your genre write in the app stores, what communities discuss in longer threads and videos, and what you can learn by asking players directly. Each answers the questions above from a different angle, and the strongest research combines them.

Your Own Player Feedback

Support tickets, in-game feedback forms, refund requests and bug reports are the most specific feedback a studio has. They often describe a problem at the moment it happened: a purchase that did not arrive, a level that could not be completed, a crash on a particular device. Collected in one spreadsheet, with columns for the date, the game version, the device and the source, they become the beginning of a customer feedback analysis practice.

App Store and Google Play Reviews

Reviews on the App Store and Google Play are the largest public source, and they cover your game and every competitor in the same detail. Because players review soon after something happens, store reviews follow updates, events and balance changes closely. The two stores do not always attract the same players or the same devices, so comparing them is itself informative.

Community Discussions

Reddit hosts long threads in which players explain how they play, what they spend money on and why they quit. YouTube comments under gameplay videos, guides and update announcements show how players react once they see a feature in action. These sources are slower and smaller than store reviews, but they add the reasons that a short review leaves out.

Playtests and Player Surveys

Traditional methods still have a role. A playtest with a handful of new players shows where they get stuck in a way that no review can, and a short survey with one open question at the moment a player lapses can explain why. Interviews with your most engaged players show what keeps them coming back. Playtest notes and survey answers are qualitative research data, and they need the same structured analysis as reviews to become more than a collection of opinions.

Researching Mobile Game Reviews with Kimola

Kimola is an AI platform that turns customer feedback into enterprise-grade market research. For a game team, that means taking reviews of your game and the games you compete with, together with your own player feedback, and turning them into a structured study of what players enjoy, what drives them away and what to change in the next update. The steps below follow the order a researcher would work in, and you can start with a free account, without a credit card.

Building the Dataset

After signing up, go to the Create your report area on the Home screen and paste the link to a game's page on the App Store or Google Play. Games can also be found by searching for their name. With the Add Multiple option you can paste several links, one per line, and Kimola collects the reviews from all of them into a single dataset. A practical first report includes your own game on both stores and three or four games in the same genre that your players mention. The support article on creating a report by adding links walks through each screen.

For Reddit threads or YouTube comments, Kimola's browser extension, Airset Generator, collects the posts or comments from a page and sends them to your account as an Airset, which you can turn into a report. Your own data, such as support tickets, bug reports or survey answers, can be uploaded as an .xls, .xlsx, .csv or .tsv file. If the file contains columns like game version, device, player level or spending tier, Kimola reads them, and you can filter and compare the results by those values.

By default, Kimola finds the themes in the data itself. If you prefer a classifier built for game feedback, the Advanced option lets you choose the Mobile Game Feedback Classifier, one of Kimola's pretrained models.

Choosing Dimensions

Dimensions are the research questions Kimola asks of every piece of feedback. You choose them when you create the report or add them later, and the guide to Dimensions explains each one. For a mobile game, five are especially useful.

Pain Points asks what goes wrong, which in game reviews usually covers ads, prices, energy and timers, difficulty spikes, matchmaking, bugs, crashes and lost progress. Motivations asks why players play and why they chose this game: the story, the challenge, competition, collecting, playing with friends or simply a way to relax for a few minutes.

Experience Stages places each comment at a moment in the player's journey: the first session, the progression through the game and the endgame, when players have seen most of what the game offers. Seeing where negative feedback concentrates tells you whether the problem is the first impression, the pacing of the middle game or the lack of things to do for your most committed players.

Personas groups players by how they play: casual players with a few minutes a day, competitive players, collectors, social players who play with friends and players who spend money regularly. The same change can delight one group and drive away another, which is why game reviews need to be read by segment.

Substitutions asks which other games players compare yours with or say they are moving to. It shows who you are really competing with for your players' time, which is not always the game with the most similar mechanics.

Reading the Report

The Overview shows the main themes in the feedback and how sentiment is distributed. Kimola finds those themes in the data itself instead of sorting comments into a fixed list of categories, so a review can be tagged with something as specific as a boss level that needs a paid booster or rewards that stopped arriving after the latest event.

Each review can mention several themes, and each theme gets its own sentiment. A player who loves the art and the characters but finds the energy system too strict contributes positive mentions of the art and the characters and a negative mention of the energy system, which a single star rating would hide.

The Performance screen ranks themes with a Satisfaction Score and a Dissatisfaction Score. These scores account for how many reviews mention a theme as well as the percentage, so a theme backed by five reviews does not outrank one backed by fifty. For a game with a modest number of reviews, this protects against the most common mistake in small-scale research, which is drawing confident conclusions from a handful of comments.

Signals

Signals are findings that have passed a statistical test. Kimola crosses every theme and Dimension with the columns in your dataset, such as game, store, star rating or date, and checks whether a topic is discussed more often or more negatively in one group than in the others (Differences) or more often recently than before (Trends). Only significant results become Signals, and they are ranked so the most important ones come first. The explanation of how Signals are tested covers the method in more detail.

Trends are the most useful Signals for a game team. A Trends Signal can show that complaints about a specific mechanic, such as matchmaking or the price of an item, have increased since the latest update, so the team can react before the rating follows. A Differences Signal can show that crash complaints are concentrated on one store, or that a theme is discussed far more negatively in one competitor's reviews. Signals need enough feedback and at least some selected Dimensions. When the data does not contain a pattern strong enough to report, the report shows none, which is an honest result.

Compare

Compare puts segments of a report side by side: different games, different stores, or one-star and five-star reviews. Up to five can be compared at once, without using extra queries. For a game team, the most valuable use is placing your game next to the games your players compare it with and seeing the volume of feedback, the sentiment, the themes they share and the themes that appear for only one of them. If players of a competing game keep praising its daily rewards or its fair matchmaking and your reviews never mention either, that is a design question worth asking.

Action Plans

Action Plans turn the findings into steps. You start by choosing or creating a Profile that describes your game, its genre and the players it is made for, then select a perspective: Our own offering, A rival or Our market. These match the three groups of questions at the beginning of this guide. A sensible first plan uses Our own offering with the Product Development goal. Once you have a report that includes competing games, a second plan with the Competitive Strategy goal focuses on how to position your game against them.

Kimola builds hypotheses from the report, tests each one against the feedback and drops the actions the evidence does not support. Each remaining action comes with a confidence level and explains why it matters, who it is for, when and where to act, the risk involved and how to see that it worked, along with the evidence behind it. A plan contains up to 12 actions. Plans work best when the report already has Signals, as the support article on how actions are built explains.

From Findings to Decisions

Research is only useful if it changes a decision. For a mobile game the decisions come with every update, and each one connects to a specific part of the report.

Update Priorities

A live game always has more to fix and build than one update can hold. The Performance screen shows which themes cost the most satisfaction, Personas shows which players they affect, and Trends shows whether they are growing. A problem that hurts your most engaged players and is getting worse deserves a place in the next update ahead of a popular request from players who are happy anyway.

Game Economy and Monetization

Players rarely complain about paying as such. They complain when a purchase feels necessary to progress, when ads interrupt at the wrong moment or when an offer feels unfair to those who do not pay. Pain Points shows which of these dominate, and Compare shows how players describe the economy of competing games in the same genre. Reading these themes by Persona separates the complaints of players who will never pay from those of players who would pay for something that felt fair.

Difficulty and Progression

Experience Stages shows where in the game frustration concentrates. A cluster of negative feedback in the middle game usually points to a difficulty spike or a slowdown in rewards, while complaints in the endgame usually point to a lack of content. Reviews often name the exact level, mode or event, which makes these findings unusually easy to act on.

Bugs and Performance

Crashes, lost progress and battery drain end a player's relationship with a game faster than any design decision. Trends Signals after each release show whether a new version introduced problems, and store comparisons show whether they affect one platform more than the other. When your own bug reports include device and version columns, the same analysis can point to the devices where the problem is concentrated.

Player Retention

Players who leave often say why in their last review. Experience Stages shows when they leave, Pain Points shows what pushed them and Substitutions shows where they went. When the same reason appears in both your own feedback and in public reviews, it is a strong candidate for a real cause of churn. Reviews of competing games show the same story in reverse: what made their players look for something new.

Ongoing Research

A single report gives you a snapshot, and a live game changes with every update, event and season, while its competitors do the same. Repeating the research at regular intervals, for example after each major update or at the end of each event, shows whether the changes you made actually moved the themes they were meant to move.

On paid plans, Feeds keep the research running continuously. A Feed collects public mentions from social media, news sites, blogs, forums, YouTube and review sites, based on the keywords and links you define. Alerts email your team when something important happens, and Mailings send a regular summary. Over time, Trends Signals show which topics are rising and which are fading.

Game Publishers and Multi-Title Studios

Publishers and studios with several games face the same questions at a larger scale, with one more added: why does the same approach work in one title and fail in another? On the Enterprise plan, each game, store or feedback channel can become a Space, a continuously growing source of feedback classified with the same Funnel, which is a shared set of custom models and Dimensions. Because every title is analyzed the same way, results stay comparable over time and across the portfolio, so a monetization problem in one game and a progression problem in another can be seen side by side. Spaces also calculate an NPS from what customers write, on a scale from -100 to 100. It is derived from the positive and negative share of written feedback, so it is not the same as a Net Promoter Score from a 0 to 10 survey, and NPS targets can be set for each title.

When a finding needs action, Tasks assign it to a member of the development or live operations team, with the underlying feedback attached as evidence, and Tasks can be sent to Jira. After a Task is closed, Kimola measures feedback on the same topic again two and four weeks later, so a balance change or a bug fix can be checked against what players say afterwards. Executive summary screens give leadership a single view of what players are saying across the portfolio. Enterprise accounts are set up together with a dedicated Account Manager, and you can request a demo to discuss your setup.

Frequently Asked Questions

A few practical questions come up when a game team starts researching with player reviews for the first time.

Should App Store and Google Play reviews be analyzed together?

Usually yes. Putting both stores in one report gives you a larger dataset, and the store column lets Signals and Compare show whether players on each platform describe the game differently, which often points to device-specific problems or different player groups.

Can I research a genre before my game is released?

Yes. Any game's App Store or Google Play page can be added to a report, so you can study what players of similar games enjoy and complain about before your own launch. The market research guide for game studios covers this earlier stage in more detail.

How many reviews do I need before the findings mean anything?

There is no fixed threshold, and the ranking on the Performance screen is designed to protect you from small samples by weighing how many reviews support each theme. Adding a few competing games to the same report is the easiest way to reach a dataset large enough for Signals, especially for a new or niche game.

Getting Started

Your players, and the players of every game in your genre, have already described much of what your game needs to know, often within minutes of the moment that mattered. Create a free Kimola account, put your game next to the games your players mention most, and see what changed after your latest update. For the research a studio does before and around a launch, the market research guide for game studios continues where this guide ends, the guide for photo and video apps applies the same approach to another app category, and the market research guide for small businesses covers the method for any industry.