Every retro is a 2-minute read
4.6 to 4.3
Sample · v4.2
Closed beta
Release retros
on autopilot.
Every time your app ships, Mobrev reads the reviews and writes the retro. You never hand it a store login.
Request a beta invite
Delivers to
- Slack
- Linear
- ChatGPT
- Claude
- Cursor
mobile-team
Slackv4.2 retro · rating 4.6 to 4.3
The rating slid from 4.6 to 4.3 while review volume doubled.
Top driver: a dark mode rendering bug on iOS 18. 43 reviews, average 1.8 stars.
- Theme · dark mode
- 127 reviews
- 14 countries
Mobrev · sample retro
How it works
From store link to shipped retro in one paste.
01
Paste a store link
Any public App Store or Google Play URL
02
Mobrev writes the retro
The morning after you ship
03
It lands where you work
Slack · Linear · email · MCP
Read-only over MCP
Your agent reads the retro too.
You
What did our last release do to the rating?
Agent
Agent
Reading the latest retro from Mobrev.
Tool call
{ appId: "app_example" }
→ v4.2 · rating 4.6 to 4.3 · 127 reviews
Agent
v4.2 took the rating from 4.6 to 4.3 on 127 reviews.
The theme behind it is a dark mode rendering bug on iOS 18, 43 reviews at 1.8 stars.
Five tools. Four read paths, and the fifth refuses to run.
Sample retro, same made-up numbers. Auth is a per-workspace key prefixed
mbrv_.
What each retro gives you.
No store credentials
It runs on any public store URL, yours or a competitor's.
Numbers you can cite
Every claim points back at the reviews it came from.
The beta
Mobrev is not open yet. Invites go out a handful at a time.
Reading how a release landed takes 2 to 4 hours in App Store Connect and Google Play Console. Mobrev takes that job off you.
- Invite based
- A person reads every request. There is no queue number and no referral link.
- No account yet
- Your email goes on the beta list and nowhere else.
- One email, at most
- We write to you if a spot opens. Every email has an unsubscribe link.