Definition
A review burst is an abrupt spike in an app's review-arrival rate — typically defined as a single-day or 7-day review count that exceeds the trailing-90-day daily average by 3x or more. Review bursts often signal a triggering event: a feature launch driving early adopters to leave first impressions, a press mention or marketplace newsletter feature pulling fresh visitor traffic, or — less happily — a bug or pricing change concentrating user feedback into a narrow window. AppRanks distinguishes positive bursts (rating ≥ trailing average) from negative bursts (rating < trailing average) so the same magnitude metric reads differently depending on the underlying sentiment. Tracking burst patterns over time surfaces the cadence of product investment and incident response: a developer team running 6 launches per year with positive bursts each time is in a different operating rhythm than one with two large negative bursts and slow recovery between them.
Where you see it on AppRanks: App page "Ratings and reviews" section, audit page "Review velocity" timeline.
Why this metric matters
Review bursts are the only marketplace signal that maps cleanly to a specific real-world event, which makes them the highest-leverage data point for post-mortem and attribution. Unlike install velocity (which lags by attribution windows) or category position (which moves on competitor dynamics too), a review burst is a direct user-feedback impulse to a thing that just happened. Reading bursts retrospectively against your release calendar usually identifies which launches actually moved sentiment vs which shipped without users noticing.
How AppRanks computes it
AppRanks fetches review counts daily and computes a trailing-90-day baseline daily-arrival rate. Days exceeding 3x baseline are flagged as bursts and stored with the date, magnitude, and average-rating-of-burst-reviews. The magnitude threshold is fixed at 3x; positive vs negative classification compares burst-rating to the app's trailing-90-day average rating.
Use cases
- Launch attribution: cross-reference your release date with the burst chart on /apps/{platform}/{app} — a positive burst within 7 days of release is the cleanest evidence the launch reached real users.
- Incident detection: a sudden negative burst with no corresponding release usually signals a third-party integration broke or a marketplace policy changed; surfacing it within a day is much faster than waiting for support tickets.
See also: Review velocity: the underlying baseline metric · Review velocity (7-day): the most-sensitive burst window · Rating distribution: read sentiment behind a burst
External references: Shopify app quality + review guidelines (developer docs) · FTC proposed rule: fake reviews and testimonials (review legitimacy)