Release Radar

Catch a bad release from your app reviews

When a new version breaks login or confuses users, App Store and Google Play reviews say so within hours. Review Expert sends those reviews to Slack or Linear as they arrive, so the mobile team hears about a regression before the rating does the talking.

Slack and Linear on every plan · 14-day free trial · cancel anytime

What works today, and what's coming

Honest scope
Review Expert does not yet detect regressions by version on its own. There is no automatic "version 4.2 is worse than 4.1" alert and no clustering of complaints into issues today. What it does do is get every low-star or release-related review in front of the right people within minutes of sync, and give you the dashboard to compare before and after.
SignalStatus
1–2 star reviews posted to Slack, Linear, Teams or Zendesk as they syncLive
Keyword alerts ("update", "latest version", "crash", "login")Live
Rating, volume and distribution before vs after a releaseLive (dashboard date ranges)
App version on each reviewLive for Google Play (review details)
Edit replies to tell reviewers a fix shippedLive
Automatic alert when a version's 1–2 star share jumps vs baselineComing soon
Complaints grouped into issues (e.g. "login loop on Android 15")Coming soon
AI reply drafts for affected reviewersComing soon

A release-day setup that works now

Ten minutes of setup before your next release.
  1. 1

    Connect both stores

    Add your App Store Connect API key and Google Play service account under Apps & Businesses. Review Expert imports history (Google Play up to 36 months from Play Console exports), then syncs roughly every 5 minutes.
  2. 2

    Send every 1–2 star review to a release channel

    In Automation, add a Slack destination with a maximum rating of 2, pointed at a channel like #release-watch. A sudden burst after a release is hard to miss.
  3. 3

    Turn release complaints into issues

    Add a Linear destination with keywords such as update, new version, since, crash, login and a maximum rating of 3. Each matching review becomes an issue the team can assign.
  4. 4

    Compare before and after

    24–72 hours after release, set the dashboard date range to the days since launch and compare average rating, 1–5 star distribution and volume with the period before.
  5. 5

    Close the loop

    When the fix ships, edit your replies to the affected reviews to say which version fixed it. Users can update their rating, and the reply is posted to the store.

Why reviews are a release signal

What crash tools miss
Login loops, paywall confusion, broken flows and silent sync failures show up in reviews, not crash logs.
History beyond 7 days
The Google Play API only returns recent reviews. Review Expert keeps them, plus older history from Play Console exports, so you can compare releases.
Official APIs, your keys
Reviews come from App Store Connect and the Google Play Developer API with credentials you control.
Alerts where you work
Slack or Microsoft Teams for visibility, each with its own rating and keyword filters.
Tickets, not screenshots
Linear issues on every plan; Jira or GitHub Issues through webhooks.
Version-aware alertsComing soon
Per-version baselines and automatic regression alerts are in development.

Keyword ideas for release regressions

  • Release wording: update, new version, latest version, since, after updating, used to work.
  • Breakage: crash, freeze, black screen, won't open, stuck.
  • Account and money: login, sign in, logged out, charged, subscription.

Keywords ignore case and match inside longer words, so crash also catches "crashing". Start narrow and widen after a release or two.

Frequently asked questions

Hear about a bad release from reviews, not from your rating

Slack and Linear are on Starter. Try it free for 14 days, and ask us about Release Radar early access.