App Store & Google Play Intelligence

Reviews, metadata and keyword rankings for iOS and Android apps, in one common schema, across every storefront. One input, both stores, no login, no cookies.

Why most iOS review scrapers quietly return nothing

Apple's public RSS review feed is capped and, worse, it lies. Whole pages come back empty, scattered between full ones, and page one is always empty. A scraper that paginates the normal way, stopping when a page is empty, returns zero reviews on real apps. Check it yourself in thirty seconds:

App	Storefront	RSS feed (what most scrapers use)	This actor
Spotify	US	0 reviews across all 10 pages	1200+ reviews
WhatsApp	US	100, or 0 if it stops on the first empty page	600+ reviews
Doctolib	FR	150	full depth

This actor reads Apple's real store API instead of the RSS feed. It sweeps every page to the true end, so it collects reviews where RSS-based tools collect nothing. Same discipline on Google Play: it follows the continuation token to the end rather than stopping at an arbitrary limit.

What you get

• Reviews from both stores in a single schema. An iOS review and an Android review come out with the same field names, the same types, the same date format. No post-processing to merge two formats.
• App metadata per storefront: name, developer, average rating, rating and review counts, version, genre, installs.
• Keyword rankings: for a search term and a storefront, the ranked list of apps. The segment nobody serves well.

How to scrape the App Store and Google Play

1. Open the Input tab. Two apps are already filled in, one from each store, so you can press Start immediately and see the output shape.
2. Replace them with your own apps. Paste the store URL straight from your browser, or use the App Store numeric id (310633997) or the Google Play package name (com.whatsapp). Mixed lists are fine.
3. Pick the storefronts. Each store is partitioned by country: a US review never appears in the French store. One storefront to start, more when you need the comparison.
4. Leave Reviews and App metadata ticked. They are covered by the same billable unit, so taking both is strictly better than taking one.
5. Press Start, then download the dataset as JSON, CSV or Excel.

Which fields should I fill?

If you want to...	Fill in	Leave alone
Read what users say about an app	apps, one storefront	everything else
Compare an app across markets	apps, several countries	everything else
Monitor new feedback daily	mode: new-only and a schedule	everything else
Track App Store search positions	tick rankings, fill keywords	apps can stay empty
Benchmark competitors	all competitor apps in one list	everything else

Only apps really matters, and even that can stay empty if you run keyword rankings alone.

Input

Field	What it does
apps	iOS ids (310633997), Android packages (com.whatsapp), or full store URLs. Mixed lists are fine.
countries	Storefronts to sweep, e.g. US, FR, GB. Each app is swept on each storefront.
include	Tick reviews, metadata, rankings independently.
keywords	Search terms to track, for ranking mode. Apple in this version.
mode	all returns every review. new-only keeps a persistent registry and returns only reviews unseen since the last run, for recurring pipelines.
maxReviewsPerApp	Upper bound per app and storefront.

Example:

{
  "apps": ["310633997", "com.spotify.music", "https://apps.apple.com/fr/app/id925339063"],
  "countries": ["us", "fr"],
  "include": ["reviews", "metadata", "rankings"],
  "keywords": ["music streaming"],
  "mode": "all",
  "maxReviewsPerApp": 500
}

Output

Every record carries a type: review, metadata or ranking. Reviews share these fields across both stores:

{
  "type": "review",
  "store": "apple",
  "app_id": "310633997",
  "country": "us",
  "review_id": "13657831289",
  "rating": 5,
  "title": "WhatsApp not bad",
  "body": "WhatsApp's not bad at all...",
  "author": "Ed Bradway",
  "version": null,
  "posted_at": "2026-01-21T04:48:38Z",
  "is_edited": false,
  "reply_body": null,
  "reply_at": null
}

Pricing

Pay per event. The review itself is never billed by the unit, that market is a race to the bottom. You pay for the collection work:

• Actor start: once per run.
• App on a storefront: one app swept on one storefront, metadata and full review sweep included, however many reviews that returns.
• Keyword ranking: one keyword tracked on one storefront.

Notes

Both stores are reached over plain HTTP. No proxy is needed in normal use. For very high-volume sweeps you can enable an Apify proxy in the input. The actor degrades cleanly: one failing app or storefront never stops the rest of the run.