App Store + Google Play Reviews Scraper

Both mobile stores. One run. One schema.

Most review scrapers cover a single store, so tracking one app across iOS and Android means running two Actors, learning two output formats, and writing glue code to stitch them together. This one returns Apple App Store and Google Play reviews as identical rows — same 17 fields, same field names, same date format — so you can group, filter and chart them the moment they land.

What you get

• 🍎 Apple App Store — via Apple's own public review feed. No scraping tricks, no proxies, no breakage when a page layout changes.
• 🤖 Google Play — full pagination, so you can pull far more than the first page.
• 🌍 Any market — pass as many country codes as you like; reviews are region-specific and this treats them that way.
• 💬 Developer replies — captured with their timestamps, not dropped.
• 🎯 Filters that save you money — restrict by star rating, or by date. With sinceDate and newest-first sorting, the run stops early instead of paging through history you already have.
• 📦 App metadata too — title, developer, overall score, total rating count, price, version, icon.

Input

Field	What it does
apps	App Store links, Google Play links, numeric Apple IDs, or Android package names — mixed freely in one list. The store is detected for you.
countries	Two-letter codes, e.g. ["us","gb","de","jp"]
language	Google Play review language (the App Store ignores it)
maxReviewsPerApp	Cap per app per country
sort	newest · most_relevant · rating
minRating / maxRating	e.g. 1–2 to read only the angry ones
sinceDate	ISO date. Only reviews after it.
includeAppInfo	Adds one metadata row per app

{
  "apps": [
    "https://apps.apple.com/us/app/facebook/id284882215",
    "com.facebook.katana"
  ],
  "countries": ["us", "gb"],
  "maxReviewsPerApp": 200,
  "sort": "newest",
  "minRating": 1,
  "maxRating": 2,
  "sinceDate": "2026-01-01"
}

Output

Every row — from either store — looks like this:

{
  "platform": "app_store",
  "type": "review",
  "appId": "284882215",
  "appName": "Facebook",
  "country": "us",
  "language": null,
  "reviewId": "https://itunes.apple.com/us/review?id=284882215&type=Purple%20Software",
  "userName": "Hannmillwood",
  "rating": 1,
  "title": "Why are you trying to charge me 20 to get Facebook back",
  "text": "After i accidentally deleted it??!?! I want my Facebook back!",
  "appVersion": "575.0.0",
  "submittedAt": "2026-08-21T09:14:33-07:00",
  "thumbsUp": 0,
  "voteCount": 0,
  "developerReply": null,
  "developerReplyAt": null,
  "url": "https://itunes.apple.com/us/reviews/id123456789",
  "scrapedAt": "2026-08-22T04:11:02+00:00"
}

title is always null for Google Play (that store has no review titles) and developerReply is always null for the App Store (Apple's public feed does not expose them). Everything else is populated by both.

Good for

• Competitor teardowns — pull your rival's 1★ reviews across both stores and read what their users actually hate.
• Release monitoring — filter by appVersion and sinceDate to see what a ship did to sentiment.
• Support triage — feed reviews into an LLM to cluster complaints.
• ASO research — compare the same app's reception market by market.

Honest limits

• Apple's public feed returns at most 500 reviews per app per country (10 pages × 50). Setting a higher cap will not get you more from that store — widen countries instead. Google Play has no such wall.
• Google Play is not partitioned by country the way the App Store is. Ask it for us and gb and it largely replays the same global review stream. This Actor deduplicates across the whole run, so you never receive — or pay for — the same review twice, and it stops paging a country once it is only replaying reviews you already have. For Google Play, vary language rather than countries. The App Store is genuinely per-country, and there more country codes really do mean more reviews.
• Apple's feed does not include developer replies. That is Apple's limitation, not this Actor's.
• Google Play review text is what the user typed; emoji-only reviews are common and are returned as-is.

Pricing

Pay per event — you pay for rows you actually receive, not for runtime:

Event	When
actor-start	Once per run
review-scraped	Per review row
app-info-scraped	Per app metadata row

Filtered-out reviews are not charged. Neither are duplicates — see the Google Play note above.