App Review Intel - Apple App Store & Google Play Reviews

Pull customer reviews from BOTH the Apple App Store and Google Play into one clean, normalized dataset - no account and no API key required. Point it at an app by store id, by URL, or by a search term, and get every review from each store behind an identical schema. Most review scrapers are single-store; this one unifies both, so you can compare iOS vs. Android sentiment for the same app side by side.

Built for product, CX, support and competitive-research teams doing review intelligence: release-regression tracking, feature requests, bug signal, star-rating trends, and competitor teardowns.

What you get (per review - identical fields on both stores)

field	notes
store	app_store or google_play
app_id	App Store numeric id, or Google Play package name
app_name	Resolved app title
review_id	Stable per-review id
rating	Integer 1-5
title	Review title (Apple only - Play reviews have no title, so null)
body	Review text
author	Reviewer display name
review_date	ISO-8601 timestamp
app_version	App version the review was written against (when present)
helpful_count	Apple: net "found helpful" votes; Google Play: thumbs-up count
country	Storefront the reviews were pulled from

Input

Give it any one of these ways to find an app (mix and match across stores):

• Apple App Store ID (e.g. 324684580) or App Store URL
• Google Play package ID (e.g. com.spotify.music) or Play URL
• Search term (e.g. spotify) - resolves the top match on each store you did not pin explicitly, so one term can pull both stores' reviews for the same app.

Plus country (storefront, default us), sort (recent / helpful / rating), and max reviews per store (default 200).

Example input

{
  "searchTerm": "spotify",
  "country": "us",
  "sort": "recent",
  "maxItems": 200,
  "proxyConfiguration": { "useApifyProxy": true }
}

Or pin each store precisely:

{
  "appStoreId": "324684580",
  "playPackageId": "com.spotify.music",
  "maxItems": 500
}

Example output records

{
  "store": "app_store",
  "app_id": "324684580",
  "app_name": "Spotify: Music and Podcasts",
  "review_id": "14283109848",
  "rating": 5,
  "title": "Spotify is my life support",
  "body": "Can’t live without",
  "author": "FlashD14",
  "review_date": "2026-07-09T11:40:40-07:00",
  "app_version": "9.1.62",
  "helpful_count": 0,
  "country": "us"
}

{
  "store": "google_play",
  "app_id": "com.spotify.music",
  "app_name": "Spotify: Music and Podcasts",
  "review_id": "76a45471-1f9e-4604-821b-4c4949227d37",
  "rating": 5,
  "title": null,
  "body": "best ever!",
  "author": "John Campbell",
  "review_date": "2026-07-09T21:39:51+00:00",
  "app_version": "9.1.62.1601",
  "helpful_count": 0,
  "country": "us"
}

How it works

• Apple reads the public RSS customer-reviews JSON feed (.../rss/customerreviews/id=.../sortBy=.../page=.../json) - ~50 reviews/page, up to 10 pages (~500 reviews) per storefront. Apps resolve by name via the iTunes Search API and by id via iTunes Lookup.
• Google Play drives the Play web UI's internal batchexecute RPC (UsvDTd) - the same technique the open-source google-play-scraper uses - walking Play's own pagination token page by page (~100 reviews/page). Apps resolve by package id, by URL, or by Play search.
• Every field is read straight from these structured responses, so there are no per-review detail requests (fast + cheap), and both feeds work through Apify's default datacenter proxy - no pricey residential proxy needed.

Notes & limits

• The App Store's mostHelpful feed is empty for some apps; when the chosen sort returns nothing, the Actor automatically falls back to most recent so a run is never silently empty.
• The App Store RSS feed caps at ~500 reviews per storefront. To go deeper, run the same app across several country storefronts.
• Google Play reviews have no title (title is null); the App Store has no per-review thumbs-up, so helpful_count there is Apple's net helpful-vote sum.

Export as JSON, CSV, or Excel, or pull via the Apify API.

This is public review data provided for research; it is not a consumer report and must not be used for any FCRA-covered purposes.