Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Devices
Build
Test
Publish
Connect
Documentation

Staged Rollout Process

The following sections cover the staged rollout process, including how to start, monitor, update, and complete the rollout. For an overview of staged rollouts, see Staged Rollouts Overview.

Start a staged rollout

In a staged rollout, you follow the same initial process for adding an upcoming version of your app.

To start a staged rollout

  1. Sign in to the Developer Console.
  2. From the Dashboard (the default homepage), under the Amazon Appstore section, click App List.
  3. Select the app you want to update. You can use staged rollouts only with existing, live apps.
  4. On the sidebar, click Release Tracks, and then click Add upcoming version on the release track you want to update.
  5. Replace your existing app file with a new version. For more details on how to upload your app file, see Add Release Details.

  6. Enter information about this update in the required Release notes field.
  7. If you need to update the metadata for this version of your app, such as the description or image assets, go to the App Setup section in the sidebar and make updates to correspond with your new release.

    You can't make updates to the Content rating section for a staged rollout.

    Understanding which updates are included in a staged rollout

    Any updates you make to metadata aren't included in the staged rollout. Metadata refers to all submission information other than the app file. For example, updates to the description of image assets won't be included. Users who receive the staged rollout see the same images and description as shown in your live app. Only the app's binary file is pushed out during the staged rollout. Metadata updates won't be released until you update the staged rollout to a 100% full release.

    Even though updates to metadata aren't included during a rollout, you can still update the information when you first begin your staged rollout. Having complete information for your upcoming version can help the Appstore team identify any potential issues early on. Later, when you decide to publish your app to 100% of your users, your app won't need to undergo testing and approval again. When you do fully publish your app to all users, they will see the new description and images (and other details you might have changed). However, keep in mind that metadata updates apply to all release tracks, so make sure the changes to your metadata apply to both release versions if you have multiple tracks.

    For more information about completing the submission screens, see App submission in the Developer Console.

  8. Click Submit for Review.
  9. In the staged rollout dialog box, select the percentage of users who should receive the update. Options are 1%, 5%, 10%, 20%, 50% and 100% Full release.

    For more information about how users are selected, see How the staged rollout audience is selected. You can't lower the percentage—you can only increase it.

  10. Click Submit for Review in the dialog box.

    Your app goes into the submission queue for Appstore testing and approval. After the Appstore approves your submission, the staged rollout is pushed out to the rollout percentage you selected.

    During the transition of your app from submitted to live, the staged rollout version can have several stages: Submitted, In Review, and Approved. These statuses appear on the Release Tracks screen. For more details on viewing the progress of the rollout, see Monitoring the progress and performance of your app file.

View details of your staged rollout

You access details about your staged rollout similar to viewing any upcoming version in the Developer Console.

To view staged rollout details

  1. Sign in to the Developer Console at https://developer.amazon.com.
  2. From the navigation bar, choose My Apps.
  3. Find your app, expand the row, and then select View to open the app listing.
  4. On the sidebar, select Release Tracks.

    On the release track with the staged rollout, you can see the current rollout percentage.

  5. For more details on the status, select App Status.

Monitor the progress and performance of your app file

To view the rollout distribution percentage, go to your staged rollout version in the Developer Console, and follow the steps in View details of your staged rollout. If you are performing staged rollouts on different release tracks at the same time, you can independently monitor the progress for each track.

The percentage shown reflects the distribution size you selected. On the App Status screen is the time when the rollout distribution was initiated (or when it will be initiated).

You can leverage third-party analytics tools and in-app instrumentation to gather information about the number of installs and crash metrics in your staged rollout version. The Developer Console shows the selected rollout distribution percentage only.

Increase the staged rollout percentage

If the binary file is performing well, you'll likely want to increase the rollout percentage.

To increase the rollout percentage

  1. Go to your staged rollout version in the Developer Console. For details, see View details of your staged rollout.
  2. Go to the Release Tracks screen, and then select Update Rollout.
  3. In the staged rollout dialog box, choose the percentage of users who should receive the update.

    For example, suppose you initially chose a 10% rollout, and now you decide to increase the percentage to 20%. If you have 20,000 users total, the staged rollout distribution would increase from 2,000 to 4,000 installs.

    No testing or approval is required from Appstore to increase the staged rollout percentage. However, you can't make any changes (including updating your app's binary file) as you increase the percentage. If you want to update your app file, see the steps in the next section, Update the app file during a staged rollout.

  4. Select Submit.

Update the app file during a staged rollout

If you find an issue and want to update your binary file during a staged rollout, you must halt the rollout before you can update the app file.

To update your app's binary file during a staged rollout

  1. Go to your staged rollout version in the Developer Console. For details, see View details of your staged rollout.
  2. Go to the Release Tracks screen, and then select Halt Rollout.
  3. In the Halt staged rollout dialog box, click Halt.

    When you halt a staged rollout, no additional users receive the app version. Users who already received a rollout version keep that version (the Appstore doesn't remove or adjust any binary file the user already downloaded).

  4. Select View on the release track and replace your existing app file with a new one.

    Remember to give your new app file an incremented build number for Vega OS apps or versionCode for Fire OS apps. The build number or android:versionCode value must be greater than both the previous staged rollout and live versions.

  5. Complete the fields as described in Add Release Details.
  6. Click Submit for Review.

    When you republish your app's binary file, your new app file needs to go through the submission process for testing and approval again. A date and time for the approval appear at the top of the screen. When the new version becomes available, users who already received a staged rollout version of your binary file automatically get the updated binary.

  7. In the dialog box, click Resume Rollout.

Complete the staged rollout

A staged rollout is specific to an individual release track, such as your Fire OS or Vega OS release. The staged rollout only affects the version of your app on the release track where you have the staged rollout configured. When you're ready to push your staged rollout version out to 100% of your users for the affected release track, you update the rollout to a full release.

To fully release the staged rollout version of your app

  1. On the Release Tracks screen, click Update Rollout.

    By submitting your app, you will be publishing this version out to all your users for the release track. Submitting your app will also complete the staged rollout for this release track.

  2. In the staged rollout dialog box, select 100% Full release. Then, click Submit.

    You see a message that says "App Submission Successful." Your app is now in the process of being published to the Appstore. The publishing process can take between 30 minutes to several hours to complete. During this time, you will see your app's status as "Submitted." When your app is approved, the status changes to "Approved." After publishing is successful, your app will be live.

Abandon the staged rollout version

Suppose the new binary file isn't performing as well as you hoped, and you want to completely abandon it. You want all users who received the staged rollout binary to downgrade, returning to the original binary file.

To "abandon" the version used in your staged rollout, you cancel your staged rollout; then you replace your app's binary file with your original app file (but with a higher build number or versionCode) and submit the new version to all your users for the release track.

To abandon the staged rollout

  1. Go to your staged rollout version in the Developer Console. For details, see View details of your staged rollout.
  2. Go to the Release Tracks screen, and then select Halt Rollout.
  3. In the Halt staged rollout dialog box, click Cancel Rollout.

    At this point, the staged rollout process is canceled and no more users will get the staged rollout version of your app. However, to downgrade the users that already have the staged rollout version installed, you must resubmit the original binary file as a higher version.

  4. To replace the binary, select View on the release track.
  5. Replace the staged rollout app file with your original app file. Make sure the build number or versionCode is higher than the version in the previous staged rollout app file.

    Although you could resubmit the app file to resume the staged rollout with a new file, in this scenario, you abandon the staged rollout workflow and publish the app to all users directly.

  6. Click Submit for Review.

    By submitting your app, you will be publishing this version out to all your users on this release track. Your app will need to undergo testing and approval from the Appstore.

  7. In the dialog box, click Submit for Review to confirm that you want to publish your app. You see a message that says "App Submission Successful."

    Your app is now in the process of being published to the Appstore. The publishing process can between 30 minutes to several hours. After the publishing process finishes, your app then exits the staged rollout and goes live for all users.


Last updated: Nov 16, 2026