Google Play Review Pain Miner

Find product pain points and app ideas by mining low-star public Google Play reviews.

This Actor searches public Google Play results for a keyword/category, fetches recent public reviews for matching apps, filters to low-star reviews, classifies complaints with transparent deterministic rules, and outputs both review-level rows and grouped opportunity summaries.

What you can use it for

• Android app idea research
• Competitor complaint mining on Google Play
• Cross-platform niche validation alongside the App Store version
• Product backlog discovery
• Pricing/UX/support/reliability pain scans
• Lightweight market research before building or buying an app business

Low-star reviews often reveal paid-pain patterns: subscription resentment, unreliable sync, confusing workflows, missing integrations, poor support, or privacy concerns.

Why this Actor is useful

Most app research starts with top-line ratings and category rankings, but those hide the reasons users churn or refuse to pay. This Actor helps you quickly answer:

• Which competitors are frustrating users the most?
• Are complaints mostly about pricing, reliability, UX, support, or missing features?
• Are multiple apps in a niche failing in the same way?
• Is there a focused wedge for a simpler Android alternative?

Use it as a triage tool to spot candidate niches, then read the source reviews before making product decisions.

Example input

{
  "query": "habit tracker",
  "country": "us",
  "language": "en",
  "maxApps": 5,
  "maxReviewsPerApp": 40,
  "maxReviewRating": 3,
  "includeUnknown": false
}

Input fields

Field	Type	Default	Description
query	string	required	Google Play keyword/category to search, e.g. habit tracker, budget app, invoice maker.
country	string	us	Two-letter Google Play country code. Invalid values fall back to us.
language	string	en	Language code used for Google Play search/reviews, e.g. en, es, de.
maxApps	integer	5	Number of search results to inspect. Capped at 25.
maxReviewsPerApp	integer	25	Number of recent reviews per app to inspect. Capped at 100.
maxReviewRating	integer	3	Only include reviews at or below this star rating.
includeUnknown	boolean	false	Include low-star reviews that do not match a known pain category.

Output

Dataset: review-level pain points

Each dataset row is one public Google Play review with classification metadata:

{
  "reviewKey": "com.example.app:gp-review-123",
  "appId": "com.example.app",
  "appName": "Habit Hero",
  "developer": "Acme Apps",
  "appRating": 4.6,
  "appUrl": "https://play.google.com/store/apps/details?id=com.example.app",
  "reviewTitle": null,
  "reviewText": "Costs too much for a simple habit tracker...",
  "reviewRating": 1,
  "painCategory": "pricing",
  "confidence": 0.75,
  "severity": 1.0,
  "opportunityScore": 0.88,
  "matchedTerms": ["expensive", "subscription"],
  "painSummary": "Pricing pain: Costs too much for a simple habit tracker...",
  "opportunity": "Offer a clearer, cheaper, or one-time-purchase alternative with fewer ads and transparent limits."
}

Key-value output: grouped opportunities

The Actor also writes OPPORTUNITIES, a grouped list by app and pain category. This is usually the best starting point for research triage:

{
  "appName": "Strong Workout Tracker Gym Log",
  "painCategory": "reliability",
  "reviewCount": 7,
  "averageConfidence": 0.81,
  "averageSeverity": 0.87,
  "opportunityScore": 0.84,
  "matchedTerms": ["crashes", "sync", "won't connect"],
  "topPainSummaries": ["Reliability pain: ..."],
  "opportunity": "Differentiate on stability, fast bug fixes, dependable sync, and trustworthy data handling."
}

The SUMMARY key includes run metadata and the top 10 opportunity groups.

Pain categories

Category	Detects	Opportunity angle
pricing	subscriptions, expensive plans, paywalls, ads	clearer pricing, cheaper tiers, one-time purchase, fewer ads
reliability	crashes, bugs, broken sync, connection failures, lost data	stable sync, data safety, fast bug fixes
ux	confusing UI, clunky flows, too many steps	simpler workflow and opinionated defaults
features	missing features, imports/exports/integrations	focused workflow or integration gap
support	customer support, refunds, no response	responsive support and visible changelogs
privacy	privacy/tracking/permissions/personal data	privacy-first positioning and local-data options
unknown	unmatched low-star reviews	manual review when includeUnknown is enabled

How to read the scores

• confidence: how specifically the review matched the category keywords.
• severity: rating-derived pain score; 1-star reviews score highest.
• opportunityScore: average of confidence and severity, useful for sorting.

Scores are triage signals, not proof of market demand. Always read the source reviewText before making product decisions.

Dogfood results from MVP validation

The Actor found useful opportunity clusters in real Google Play scans, including:

• budget app: sync failures, deceptive trial/pricing language, support frustration.
• invoice maker: subscription creep, paywalls, business-impacting reliability problems.
• receipt scanner: annual-price complaints, feature/export gaps, simplified workflow opportunities.
• calendar: sync issues, ads/subscription resentment, import/missing-feature complaints.
• workout tracker: import/export gaps and repeated reliability/login issues.

Classifier pass #2 reduced several noisy false positives:

• generic need no longer implies a feature request
• generic tracking no longer implies a privacy complaint
• weak premium mentions lose to stronger reliability evidence
• generic wish phrasing no longer becomes a features complaint by itself

These results are promising enough for private beta, with the caveat that classification remains deterministic and should be used for triage.

Notes and limitations

• Uses public Google Play metadata and reviews via google-play-scraper.
• Does not log in to Google, bypass access controls, or collect private data.
• Classification is deterministic keyword/pattern matching, not LLM analysis. This keeps runs cheap and explainable.
• Broad search queries can still pull in adjacent apps.
• Some review text is ambiguous; always read the underlying review before making product decisions.
• Results are best for triage and pattern-finding, not as a standalone market-size estimate.

Suggested workflow

1. Start with a niche query such as habit tracker, invoice maker, or receipt scanner.
2. Review OPPORTUNITIES first to see which apps and pain categories cluster together.
3. Open the highest-scoring review rows in the dataset to verify whether the complaint is real and repeated.
4. Compare the same niche against the App Store Review Pain Miner to see whether the pain is Android-specific or cross-platform.
5. Convert repeated complaints into hypotheses for product positioning, pricing, or feature scope.

Local development

PYTHONPATH=. python -m pytest tests/test_pain_miner.py -q
apify validate-schema
apify run --purge

Deployment

$apify push

Status

This is a strong private-beta candidate derived from the published App Store Review Pain Miner pattern. It is not published yet.