ANVILNINE

MOBREV / HOSTED

Pre-launch

A retro for every release, whether anyone remembers or not.

Ship a version and Mobrev reads that release's store reviews. It always computes the rating delta, review volume, themes, and keyword trends. The written story on top only runs when there are enough reviews to support one.

mobrev.app has no DNS record yet. There is no app to open and no private beta to join. The screenshot is the real UI, and every number on this page is read off the code.

  • 15

    reviews before a story runs

  • 57

    Apple storefronts, plus Google Play

  • 0

    store credentials

mobrev.app
The Mobrev homepage: paste an App Store or Google Play URL to get a release retro, with a sample retro card delivered to Slack

15 reviews before anything gets written.

Mobrev will not write a narrative about four reviews. The AI stage is gated on two numbers checked before it runs: at least 15 reviews on the release, and at least 24 hours since it shipped. Miss either one and you still get the retro, just the measured half of it.

Under the line

Fewer than 15 reviews, or less than 24 hours old

  • Rating delta against the previous version
  • Review volume for the release
  • Themes pulled out of the review text
  • Keyword trends across the window

No narrative. Mobrev does not write filler to cover the gap.

Over the line

15 reviews or more, 24 hours or more

The same four measurements, plus the narrative layer written on top of them: what moved, which themes drove it, and what the release looks like next to the one before.

The numbers stay the source, and the story sits on top of them.

Nothing to add to your release pipeline.

Mobrev works out that a release shipped by watching the review data itself, with a version detector. There is no Fastlane step, no Bitrise job, and no Xcode Cloud hook to wire up. Nothing in your build has to know Mobrev exists.

Delivered to

Slack email

Two targets, and that is the whole list. Mobrev pushes a retro to one or both.

Read in

web console MCP client

Both let you go and read a retro Mobrev has already written.

Five tools, all read paths.

Agents read past retros. Runs stay scheduled.

An agent can fetch what Mobrev has already written and reason over it. Nothing on this server starts a retro run: runs stay on the release schedule, where the threshold applies.

Auth is a per-workspace bearer key, prefixed mbrv_.

  • list_apps read

    The apps in the workspace.

  • list_retros read

    Every retro written for an app.

  • get_retro read

    One retro in full.

  • get_latest_retro read

    The most recent retro for an app.

  • run_competitive_retro throws

    Defined, and it refuses. There are no measured numbers behind it to return.

No store credentials, which is why it runs on anyone's app.

Mobrev reads public store data: 57 Apple storefronts plus Google Play. No OAuth, no App Store Connect, no Play Console. You never hand over a login, and that same public access lets Mobrev run a retro on a competitor's app.

Pricing is not settled, so this page will not quote it.

When mobrev.app opens, the way in is an anonymous one-shot demo: paste an App Store or Google Play URL, get one retro back, no signup. A Free $0 tier exists but cannot fetch a new app, so start with the demo. The paid numbers on the current plan sheet are placeholders. Mobrev is proprietary and run by Anvil Nine, so there is nothing to self-host.