The first 3 interviews are free · Start free or see the prices

App Store Review Analysis: Codebook for App Reviews

Use this codebook on reviews from the App Store and Google Play. It links each problem to an app version, so you can tell a new bug from an old complaint.

Analyze a transcript free

Use it for

  • Review exports from App Store Connect and the Google Play Console, with star rating, date and text.
  • The app version, the device and the OS version for each review, where the store gives them.
  • Your release dates, so you can link a change in reviews to a release.

Steps

  1. Export reviews for a fixed period

    Export reviews from both stores for the same period, for example the last 90 days. Keep the app version on each review. Remove duplicate reviews that a person posted twice.

  2. Code all ratings, not only low ones

    Code reviews with 1 to 5 stars. Many 4-star reviews name one problem. Five-star reviews tell you which features to protect.

  3. Give each review up to two codes

    Most reviews name one main problem. Give the main problem the first code and a second problem the second code. Short reviews with no topic get no code, but keep their star rating.

  4. Group by app version

    Count each code per app version. A code that jumps after one release points to a regression. A code that is the same in every version is a lasting problem.

  5. Split by platform and device

    Compare iOS and Android for each code. Crashes and compatibility problems often affect one platform or one device family. Name the devices in the report.

  6. Check the reviews against your own data

    Compare crash codes with your crash reports and paywall codes with your subscription data. A review shows the user's view. Your data shows how many users the problem affects.

Codebook

Copy the codebook as a table. It pastes into a spreadsheet with one row for each code.

Crash or freeze

The app closes, stops responding or does not open.

Include
The review says the app crashes, freezes, goes black or will not start.
Exclude
The app works but loses or does not save data. Use Data loss or sync for that.
Example
“Crashes every time I open the camera. Uninstalled and reinstalled, still crashes.”

Update made it worse

A recent update removed, changed or broke something that the user liked.

Include
The review mentions an update, a new version or a redesign and says it is worse than before.
Exclude
The review describes a crash with no link to an update. Use Crash or freeze for that.
Example
“The new update moved everything around and I cannot find my saved lists anymore.”

Login or account access

The user cannot sign up, sign in, reset a password or reach their account.

Include
The review mentions verification codes, sign-in loops, locked accounts or social login failures.
Exclude
The user can sign in but cannot restore a purchase. Use Paywall or subscription for that.
Example
“Never get the verification email so I am stuck on the first screen.”

Paywall or subscription

Complaints or praise about what is paid, the price, the trial and the subscription terms.

Include
The review mentions a paywall, a price, a free trial, an unexpected charge, a refund or restore purchases.
Exclude
The review is about ads in the free version. Use Ads for that.
Example
“Says free but you cannot do anything without the 9.99 a week plan.”

Ads

The number, type or placement of ads in the app.

Include
The review mentions ads, pop-ups with offers, videos that cannot be skipped or ads for other apps.
Exclude
The review is about prompts to buy the app's own paid plan. Use Paywall or subscription for that.
Example
“An ad after every single level. I spend more time watching ads than playing.”

Data loss or sync

User data is lost, not saved, duplicated or does not move between devices.

Include
The review mentions lost progress, missing notes, failed backup or data that differs on two devices.
Exclude
The app crashes and the data is fine after a restart. Use Crash or freeze for that.
Example
“Lost three years of journal entries after switching phones. Backup said it was done.”

Device or OS compatibility

The app does not work, or looks wrong, on a specific device, screen size or OS version.

Include
The review names a device or OS version, or describes layout problems on a tablet or a small screen.
Exclude
The problem happens on all devices. Use the code for the problem itself.
Example
“Does not support iPad landscape, the buttons are cut off on the right.”

Performance and battery

The app is slow, drains the battery, uses much storage or makes the phone hot.

Include
The review mentions slow loading, lag, battery drain, phone heat or app size.
Exclude
The app stops responding completely. Use Crash or freeze for that.
Example
“Drains 30 percent of my battery in an hour even in the background.”

Missing feature

A function that the user wants and that the app does not have.

Include
The review asks for a function, or gives a star rating that depends on a function being added.
Exclude
The function existed before and an update removed it. Use Update made it worse for that.
Example
“Please add a dark mode and I will give 5 stars.”

Feature praise

Positive comment about a specific function or quality of the app.

Include
The review names something that the user likes, such as a feature, the design or the content.
Exclude
The review is positive with no specific thing named. Leave it uncoded and keep the rating.
Example
“The sleep timer is perfect, I fall asleep to it every night.”

Developer response

Comments about how the developer answers reviews, emails or support requests.

Include
The review mentions a reply from the developer, a missing reply or a support email.
Exclude
The review is only about the app with no mention of contact with the developer. Use the code for the topic.
Example
“Emailed support twice about the charge, no answer. Changing my review to 1 star.”

Report outline

  1. Average rating and review volume per app version and platform for the period.
  2. Top problems by platform, each with the versions and devices it affects and 2 quotes.
  3. Regressions: codes that increased after a specific release, with the release date.
  4. Monetization feedback: Paywall or subscription and Ads, apart from product bugs.
  5. What users praise, so the team can protect it in the next redesign.
  6. Actions, each with an owner and the rating or crash metric to watch.

Mistakes to avoid

  • Do not code only 1-star reviews. They show what is broken, but 3-star and 4-star reviews show what holds back good users.
  • Do not count a review spike without the release date next to it. Reviews follow releases, so the version is the first clue.
  • Do not mix the two stores in one number without checking. iOS and Android users often report different problems.
  • Do not treat review volume as user volume. People who write reviews are a small and angry or happy subset of all users.

Guides that use it

Questions

Export the reviews from both stores with version and rating. Code each review with up to two codes. Then count codes per version and per platform to find regressions and lasting problems.

Code all reviews for the last 90 days if there are fewer than 500. If there are more, code a random sample of 300 and all reviews for the latest version.

Yes, but keep the two tasks apart. Reply from the store console. Code the review text before the reply, so your reply does not change how you read it.

You can upload an export of reviews as a CSV file to the Library. Then you can ask Eva questions about the file. Code the reviews with this codebook to get counts you can check.

Ask real people your question

The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.

Start free