/ writing / voice-of-customer

Every crash report your users never filed is sitting in the Play Store.

2026-08-25 · cynix · 3 min read

Mobile teams instrument analytics, yet the richest bug reports arrive voluntarily in review form: "crashes since the update," "battery drain on Samsung," "login loop after v4.2." The problem is extraction — the Play Store renders reviews client-side behind infinite scroll.

The Google Play Reviews Scraper takes package names and returns reviews as typed rows through a real browser render:

{
  "packageNames": ["com.example.app"],
  "maxResults": 300
}
{
  "appName": "Example",
  "rating": "2",
  "text": "Force closes on startup since yesterday",
  "reviewedAt": "2026-08-19",
  "appVersion": "4.2.1"
}

Where it earns its keep

Release triage: diff review themes between versions to catch regressions within hours of a rollout. Competitive analysis: what do users beg a rival app to add? ASO research: mine review language for store-listing keywords that mirror real user vocabulary.

The honest limit: Play shows the most helpful and most recent reviews first, not literally all of them — very old deep history may be partial. For regression detection you're watching recent windows anyway, so this rarely bites.

Try it: app play reviews on Apify — ratings, versions and verbatims per app.