Does AppForShare roll out for me?

No. An Admin of your workspace chooses each step and confirms it. AppForShare sends it with your own Google Play connection and keeps a record.

Which plan do I need?

Pro for tracks, release notes and promoting between testing tracks. Team for production rollouts and testers.

Can I upload a new build here?

Builds reach Google Play from your GitHub Actions setup or your own pipeline. This page works with the releases already on Google Play.

AppForShare Create 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. Google Play then handles it as it would from Play Console.

Start free See plans

Example

Production

2.5 (121)Rolling out to 20%
2.4 (118)Live for everyone
Next stepRaise to 50%, halt or complete

Every change: an Admin, a confirmation, a line in the history.

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

How it works

Step 1
Pick the app
Apps shared from your Google Play connection are in the picker. Every track opens with its releases.
Step 2
Choose the action
Release notes or promote on testing tracks (Pro). On production: staged rollout %, halt, resume or complete (Team).
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.

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.

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

AppForShare does not watch crash rates or halt a rollout by itself. A person decides every step.
Internal testing testers are email lists in Play Console, and open testing has no tester list; Google's API only sets Google Groups on closed tracks.
New apps that were never published only take draft releases until the first release in Play Console.

Questions

Does AppForShare roll out for me?: No. An Admin of your workspace chooses each step and confirms it. AppForShare sends it with your own Google Play connection and keeps a record.
Which plan do I need?: Pro for tracks, release notes and promoting between testing tracks. Team for production rollouts and testers.
Can I upload a new build here?: Builds reach Google Play from your GitHub Actions setup or your own pipeline. This page works with the releases already on Google Play.