Your users already told you what broke.
RevyLens reads every App Store and Play review, groups the repeats into named issues, and tells you within hours when a release starts drawing complaints — in whatever language they arrive in.
No account needed. The demo is a full workspace with real review data from four sample apps.
- Reviews
- 4,164
- Read across 4 apps, last 90 days
- Languages
- 13
- Translated and grouped together
- Clusters
- 37
- 6 moved this week
Face ID sign-in fails after the 6.4.0 update
- Mentions
- 40
- Languages
- 6
- Days old
- 4
Four steps, and only one of them makes the pile smaller.
Most tools stop at a sentiment score. The useful work is grouping the repeats — that's where a few thousand reviews turn into a list you can act on before lunch.
100% of the arriving volume
Everything, from both stores
App Store Connect and Play Console, backfilled 90 days on connection and polled hourly after that. Ratings, versions, devices and countries come with it.
100% of the arriving volume
Translated, never discarded
Each review is translated and read in full rather than keyword-matched. Nothing is filtered out here — this step reduces the pile by exactly nothing.
0.9% of the arriving volume
Repeats become one issue
The same complaint written twelve ways collapses into a named issue or request, carrying the versions, devices and reviews that formed it.
0.1% of the arriving volume
Only what changed reaches you
A cluster crossing your threshold becomes a Slack message, a Linear issue or a line in Monday's digest. The rest waits in the workspace.
You'll know before the rating does.
Store ratings average everything you have ever shipped, so they barely move when a release goes wrong. Complaint volume moves the same day. RevyLens compares the days since a release with the same stretch before it and names what changed.
New authentication stack
- Rebuilt sign-in on the new authentication stack
- Shorter idle session window for compliance
- Card controls moved into the account tab
- Review volume
- +62%
- 81 → 131
- Mean rating
- -1.23
- 4.17 → 2.94
- Negative share
- +38pt
- 11% → 49%
Reviews per day, 4 days either side of 6.4.0
- Negative
- Neutral and positive
- Face ID sign-in fails after the 6.4.0 update36 mentions in 4 days
- Session expires roughly every two minutes15 mentions in 4 days
- Opening an account took minutes14 mentions in 4 days
- Card freeze switch turns itself back on9 mentions in 4 days
- Spending categories with monthly budgets4 → 1 mentions
- Export statements as CSV4 → 1 mentions
- Payment notifications arrive hours late3 → 1 mentions
Every number opens to the reviews behind it.
A cluster is not a summary you have to take on trust. It's a list of real reviews in the language they were written in, with the version, device and country attached to each one.
Transfers sit on “Processing” for hours
- 2 out of 5 starsLarissaPortuguese · BR6.4.022h ago
I made an instant transfer and it stayed in processing for almost a day. The balance had already been debited.
Fiz uma transferência instantânea e ficou em processamento por quase um dia. O saldo já tinha sido debitado.
- 2 out of 5 starssam.pEnglish · US6.4.02d ago
Instant transfers to other banks sit on Processing for hours. The receiving bank shows nothing, so I have no idea whether to send it again. Support told me to reinstall, which only helped for a day.
- 1 out of 5 starsD. FuentesSpanish · CL6.3.01w ago
The transfer has been in Processing for six hours and the money has already left the account. There's no way to know if it arrived.
La transferencia lleva seis horas en Procesando y el dinero ya salió de la cuenta. No hay ninguna forma de saber si llegó. Por lo demás la app está muy bien.
Showing 3 of 123 reviews in this cluster. The full list is filterable by version, device, country and rating.
Built for the questions a mobile team actually asks.
Not a dashboard of averages. The things you need on the Monday after a release, and on the Thursday when someone asks what users want next.
Recurring issues, named
The same complaint written twelve different ways collapses into one issue with a title you can put in a ticket. Counts, first seen, last seen, and the reviews that formed it.
Requests ranked by demand
Feature requests are kept apart from defects, because the decision is different. Each one carries how many people asked and whether that number is still growing.
Attributed to a build
Every cluster knows which versions it appears on. When something starts on one build and nothing before it, that is stated plainly rather than implied.
Device and country breakdown
See whether a crash is everywhere or on two device families, and whether a complaint is global or coming from one market.
Every language, kept intact
Reviews are translated for reading and grouped across languages, so a German and a Turkish report of the same bug land in the same cluster. Originals are always one tap away.
Alerts with a threshold you set
Choose what counts as a spike for your app. When a cluster crosses it, the message arrives with the evidence attached, not just a number.
Priced on reviews read, not on installs.
A team on the Team plan reading 75K reviews a month pays less than one engineer-day. Every plan includes clustering, translation and release comparison.
Starter
One app, one team, everything that matters.
- Reviews
- 10,000
- Apps
- 1
- Seats
- 3
- 10,000 reviews a month
- Issue and request clustering
- 90 days of history
- Weekly email digest
- CSV export
Team
Most teamsFor teams shipping on a release cadence.
- Reviews
- 75,000
- Apps
- 6
- Seats
- 10
- 75,000 reviews a month
- Release comparison and spike alerts
- Slack and Linear handoff
- 24 months of history
- Scheduled reports with custom sections
- Translation for every review
Scale
Portfolios, regions and compliance requirements.
- Reviews
- 400,000
- Apps
- Unlimited
- Seats
- Unlimited
- 400,000 reviews a month
- Cross-app portfolio view
- Webhooks and full API access
- SAML SSO and audit log
- Custom cluster taxonomy
- Priority support with a named contact
Volume is counted on reviews read in a month, not on installs. Going over the cap pauses ingestion rather than charging you — you choose whether to upgrade.
The parts people ask about first.
Still deciding? The demo workspace is the fastest answer — it runs the full product against four sample apps, including a release that went wrong.
Point it at your listing and see what the last 90 days were actually about.
Connecting an app takes a set of store credentials and about two minutes. The first analysis covers 90 days of history, so there is something to read before you finish your coffee.