Review Gap Finder — Apps Losing Rating Points, Ranked avatar

Review Gap Finder — Apps Losing Rating Points, Ranked

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Review Gap Finder — Apps Losing Rating Points, Ranked

Review Gap Finder — Apps Losing Rating Points, Ranked

For a list of apps, get recent reviews, find the ones dragging the rating down, and rank every app by its review gap — the negative reviews with nobody answering. Built for reputation agencies and app teams.

Pricing

from $1.00 / 1,000 results

Rating

0.0

(0)

Developer

alaudin burki

alaudin burki

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Review Gap Finder — Apps Losing Rating Points, Ranked for Outreach

Give it a list of apps and get back which ones are losing rating points and have nobody answering — ranked worst-first, ready to work through.

The point is the gap, not the rating. An app sitting at 4.7 lifetime but averaging 2.9 in its most recent reviews is in trouble right now and its team may not have noticed. That difference is the whole product.

What you get

Dataset gaps — one row per app, worst first. This is the deliverable.

FieldDescription
app, developer, appIdWhich app
reviewsSampledHow many recent reviews were read
negative / positiveCounts of 1–2★ and 4–5★
negativeSharePercentage of the sample that is negative
recentAvgRatingAverage of the sampled reviews
storeAvgRatingThe app's lifetime average
ratingGapstoreAvgRating − recentAvgRating — positive means it is slipping
gapnegative count — the ranking number, because volume matters
lowestRatedReviewThe worst recent review, quoted
urlApp Store link

Default dataset — one row per review

id, appId, store, rating, title, body, author, version, updatedAt, voteCount, voteSum, scrapedAt.

Sample output

{
"app": "Instagram",
"developer": "Instagram, Inc.",
"reviewsSampled": 100,
"negative": 49,
"positive": 40,
"negativeShare": 49,
"recentAvgRating": 2.94,
"storeAvgRating": 4.69067,
"ratingGap": 1.75,
"gap": 49
}

Read that row: half the most recent reviews are one or two stars, the recent average is 2.94, and the app's public rating still says 4.69. That is a 1.75-point gap — and a conversation.

Default input

Runs with no editing: ["WhatsApp Messenger", "Instagram", "Spotify"], US storefront, 3 pages (150 most recent reviews) per app.

Limitations — read this before you buy

  • Apple App Store only, right now. That is the one store with a clean public review feed.
  • Google Play is NOT implemented. Its app page is a ~1.1 MB JavaScript blob and reviews load from a signed internal call. Not faked, not estimated — absent.
  • Google Maps, Trustpilot and Yelp return HTTP 403 or a JavaScript shell with no data. The local-business version of this idea — the big one — needs a real browser runtime and is recorded as blocked rather than shipped broken.
  • Apple's feed has no developer replies, so unanswered cannot be computed there. The gap score is used instead, which is a different and defensible signal: negative volume plus a recent-vs-lifetime divergence.
  • This samples the most recent reviews, not all of them. A long-established app with millions of reviews will show a small sample. Treat it as "what people are saying now", not a full audit.
  • No sentiment model. 1–2★ is negative, 4–5★ is positive, 3★ is neither. That is deliberate: it is explainable, and it cannot hallucinate.

Notes

  • Two datasets on purpose. The ranked prospect list would be buried under thousands of review rows if they shared one dataset.
  • The app's own entry is the first item in Apple's feed and carries no rating — it is skipped by that field rather than by index, so a change in feed order cannot corrupt the sample.