AppForShareCreate a free account

Every Google Play track, and the rollout controls, on one page

Pro (testing tracks) and Team (production and testers)

Play Console spreads a release across several pages: the track, the rollout, the notes, the testers. The releases page shows every track of your app with its releases and what each one is doing right now, and puts the common actions next to them.

Every change is made by an Admin of your workspace, after ticking a confirmation, with your own Google Play connection, or by a rollout schedule an Admin set and confirmed. Google Play then handles it as it would from Play Console.

Example

Production

  • 2.5 (121)Rolling out to 20%
  • 2.4 (118)Live for everyone
  • Rollout scheduleNext: 50% on Nov 6, 10:00
Every change: an Admin, a confirmation, a line in the history. Anyone in the workspace can pause the schedule.

Made for

  • Teams that move builds from internal to closed testing every week
  • Agencies that run production rollouts for client apps
  • Anyone who wants a record of who raised a rollout and when

What it ends

  • Clicking through Play Console to find which release is on which track
  • Raising a rollout without a record of who did it
  • Copying release notes into each language by hand on every track
  • Remembering to raise a production rollout every couple of days

How it works

  1. Step 1

    Pick the app

    Apps shared from your Google Play connection are in the picker. Every track opens with its releases.

  2. Step 2

    Choose the action

    Release notes or promote on testing tracks (Pro). On production: staged rollout %, halt, resume, complete or a rollout schedule (Team).

  3. Step 3

    Confirm and send

    Tick the confirmation naming the app and the track. The change goes to Google Play and into the history on the page.

Upload your store build to AppForShare once: testers get an install link, and the same file goes on to TestFlight or a Google Play track from the build page, with your own App Store Connect key or Google Play service account. Watch on YouTube

Pro and Team

Pro reads every track, edits release notes and promotes releases between testing tracks: internal, closed, open and your own closed tracks. Team adds production: promote a release to production as a draft, a staged rollout or for everyone, raise the rollout, halt it, resume it, complete it, and set the Google Groups that test your closed tracks. A release is never pushed off a track silently: if production already has a draft or a rollout, you finish or halt that one first.

Scheduled rollouts (Team)

When a production release is already rolling out to a share of users, an Admin can press Schedule rollout and set a rollout plan instead of coming back to raise it by hand. Up to 10 steps, each a percentage above the one before (100% completes the rollout) and a wait of 1 hour to 30 days after the step before. Presets: 7 days like the App Store phased release (2, 5, 10, 20, 50, 100%), 3 days (10, 50, 100%) or 14 days. The Admin ticks a confirmation, and each track has one open schedule.

At each step AppForShare reads the track on Google Play first and only then sets the percentage the schedule names, with your own Google Play connection. It never lowers a rollout and never sets a percentage the schedule does not name. The step goes into the history on the page, and the workspace owner and the Admin who set the schedule get one email.

The schedule stops itself, without writing anything, and emails the owner when the rollout was halted or completed on Google Play, when Google Play shows a percentage AppForShare did not set (for example after a change in Play Console), when the release is gone or when the app is no longer shared. A change by hand on the releases page stops it too. Anyone in the workspace can pause or stop a schedule at any time, also from the CLI; resuming needs an Admin and a confirmation and carries on from the current percentage.

Saved release defaults (Pro and Team)

Save the release notes you use every time, per language (up to 500 characters each, as Google Play allows), the track you usually promote to and how: as a draft, as a staged rollout with a percentage, or for everyone. The promote form and the release notes then fill in from the defaults in one click, and you check them before you confirm. The defaults only fill in forms; nothing is sent to Google Play from them on their own.

Crash and ANR rate per version (Team)

For apps shared from your Google Play connection, the release page of a version and the rollout schedule emails show Google Play's crash rate and ANR rate for its version code, read from the Play Developer Reporting API. They are there so you decide with the numbers in front of you. AppForShare only reads them: a schedule never pauses, halts or raises a rollout because of them.

Send a new build to a track

Upload the .aab you built anywhere, then an Admin sends it to an internal, closed or open testing track with a confirm tick (Pro), or to production as a draft release you roll out from this page (Team).

Google's rules stay in place

Google Play only raises a rollout percentage, never lowers it; to stop a rollout you halt it. Changes still go through Google's review when Google reviews them, and AppForShare never cancels changes that are already in review.

Good to know

Questions

Does AppForShare roll out for me?
Only on a schedule an Admin of your workspace set and confirmed, on Team. Without a schedule, an Admin chooses each step and confirms it. Either way AppForShare sends it with your own Google Play connection and keeps a record.
Will a schedule stop a bad release?
No. On Team each schedule email shows the crash rate and ANR rate Google Play has for the release, but the schedule never acts on them. It stops itself only when the rollout was changed somewhere else, for example halted in Play Console. Deciding to pause the schedule stays with you.
Can I set a schedule from the CLI?
Yes, an Admin can: appforshare play rollout-plan com.example.app --steps 5@1d,20@2d,100@3d --yes. pause, stop and resume work there too. AI tools connected through the MCP server can only read a schedule.
Which plan do I need?
Pro for tracks, release notes, promoting between testing tracks and saved release defaults. Team for production rollouts, rollout schedules and testers.
Can I upload a new build here?
Yes. Upload the .aab to AppForShare and an Admin sends it to a testing track (Pro) or to production as a draft (Team). Builds from your GitHub Actions setup can go to Google Play straight from the runner.

Read next

Try it on your own app

Free account in a minute. Pro starts with a 7 day free trial.

More features