App Store Scraping: What Works, What Breaks, and the Limits We Hit
We are not going to pretend that app store scraping is flawless. It is useful, it works most of the time, and it can save you real money compared to paid alternatives. But there are limits, and you should know about them before you rely on the data.
Rate Limits Are Real
Both Apple and Google throttle how fast you can pull reviews. Hit the stores too hard and your requests start failing or returning empty results. ReviewMaxxing handles this by running a maximum of 5 concurrent requests and adding small delays between batches. You will not get blocked, but large scrapes across many countries take time.
If you are scraping all 50+ countries for multiple apps, expect it to take several minutes. That is the tradeoff for staying under the radar.
You Get a Sample, Not the Full Archive
Neither store exposes every review ever written. The App Store surfaces up to about 500 reviews per country per app. Google Play gives you around 750. These are the most recent reviews, not a random sample. Older reviews are simply not accessible through the public interfaces.
For most use cases — competitor analysis, post-launch monitoring, regional sentiment checks — this is plenty. But if you need historical data going back years, scraping alone will not get you there.
API Changes Can Break Things
App stores do not offer official, stable APIs for review access. The scraping libraries that ReviewMaxxing relies on work by reverse-engineering the stores' internal endpoints. When Apple or Google changes something on their end, things can break until the libraries are updated.
We maintain support for both stores and keep our dependencies updated, but occasional hiccups are part of the deal. If a scrape fails for a specific country, the system skips it and moves on rather than stopping everything.
What You Do Not Get
Scraping gives you publicly visible review data: the text, rating, date, author name, and vote counts. What it does not give you:
- Install or download numbers
- Revenue estimates
- Private analytics or crash reports
- Developer responses (in some cases)
- Reviews that users have deleted
If you need that kind of data, you will need the stores' official developer consoles or a paid analytics platform.
Why Transparency Matters
We would rather tell you upfront what the tool can and cannot do than have you find out mid-project. ReviewMaxxing is great for getting review data into a spreadsheet quickly and for free. It is not a replacement for a full-featured analytics suite.
Try it yourself and see if it fits your needs. For most teams doing regular review analysis, it does.