Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Devices
Build
Test
Publish
Connect
Documentation
Skip to main content
The following sections cover common concepts related to staged rollouts. For instructions on how to start and monitor staged rollouts, see Staged Rollout Process.

Advantages of staged rollouts

When you release an update to an existing app, you can publish your new version in a staged rollout. Staged rollouts let you limit your app’s release to a subset of users to test the new binary file. You can gradually ramp up the percentage of users until the release is available to all of your users for a specific release track. Staged rollouts provide a way to limit the scope of issues introduced with new versions of your app file. For example, if your release performs poorly on user systems, it’s better if only 5% of users experience the issue rather than your entire user base. You can fix any issues in your app and push out a new version to the users, continuing to test each new app file. The testing you perform in your staged rollout should be performance testing rather than functional testing. Because you’re rolling out the app to a percentage of your entire user base, you should have already caught major issues such as frequent app crashes or other bugs. In addition to performance testing, you can also use staged rollouts as a means of experimenting with new features, or as a way to do A/B testing. For example, suppose you have a new feature in your game or app. You can include the new feature in an upcoming version and push out the version in a staged rollout to a subset of users. You can then evaluate the performance of your app with the new feature and compare it to the performance of your app without the feature. In this way, you can see what’s working with the audience in a controlled, measurable way rather than pushing releases out to every user at the same time. A staged rollout lets you be more strategic with your app releases and enhancements.

Requirements and limitations for staged rollouts

There are several requirements and limitations with staged rollouts:
  • Limited to new versions for existing apps: Staged rollouts can be used only for upcoming releases of existing, live apps. You can’t use staged rollouts for a new app that has never been published to the Amazon Appstore.
  • Existing device support only: Staged rollout versions are pushed out only to the same devices that your existing, live app already supports. For example, if you create a staged rollout and add support for devices that your live app doesn’t already support, those devices won’t be able to discover the staged rollout. However, the Appstore ingestion team tests your staged rollout version against the new devices before approving your app.
  • Only the app file is included: Metadata from the live app version continues to be displayed to the staged rollout recipients. Metadata can include the description, images and multimedia, availability, and pricing. Users receive only the binary file in your staged rollout.
  • Live app must not be suppressed: If the live version of the app is suppressed or in the process of suppression, staged rollout is not available.
  • 10,000 unique downloads minimum: Staged rollout is available only when the live version of your app has had at least 10,000 unique downloads (“unique app purchases”) in the past three years. You can see your app downloads in the Reporting section of the Developer Console. The 10,000 minimum establishes enough volume for the staged rollout data to be meaningful.
  • Updates to price or IAP items not allowed: Updates to your app’s price or in-app purchasing (IAP) items are not allowed in the staged rollout version.
  • Content rating cannot change: You can’t change the content rating of your app in a staged rollout. If your staged rollout version requires a more mature content rating than your existing, live app, your staged rollout version won’t be approved.

How the staged rollout audience is selected

When you start a staged rollout, you can select the percentage of users you want to include. When submitting a new version of your app for review, you select the rollout distribution. You then see a dialog box with rollout percentage options, with radio buttons for 1%, 5%, 10%, 20%, 50%, and 100% (Full release). The rollout percentage is calculated based on the existing user base of your live app. For example, if your live app has 20,000 installs on user devices and you choose 10% as the rollout percentage, the 10% is calculated against your 20,000 users, which would mean 2,000 users are included in the staged rollout distribution. Note the following about how users are selected:
  • Users are randomly selected from (1) the existing base of users who already have the live version of your app and (2) prospective users who are eligible to install your app (eligible because their devices support your live app). The same device support options of your live app are used to define the potential audience for your staged rollout version (regardless of the device support options you select in your staged rollout). For example, suppose your currently published live app doesn’t support Fire TV Gen 1, but your new app in staged rollout does support Fire TV Gen 1. The prospective customer base in the staged rollout will not include users with Fire TV Gen 1 devices.
  • Users are selected randomly. You can’t specify which particular users are included in the rollout, unlike Live App Testing (LAT), which lets you curate a list of specific testers. For more information on LAT, see Get Started with Live App Testing for Fire OS and Get Started with Live App Testing for Vega for Vega OS.
  • Users are selected from the same countries that you selected in the Availability section of the App Setup screen for your live app.
  • If your app is available on multiple devices for the same release track, users are randomly selected related to the binary you’re replacing. For example on a Fire OS release, if you target both Fire tablets and Fire TV devices, if you’re replacing the Fire TV app, users who installed the Fire TV APK (or who are eligible to install it) might receive the staged rollout version. Tablet users would not receive the new version unless you were also replacing the tablet APK.
  • You can’t use staged rollouts to test on new devices. If you have multiple binary files for your app on the same release track, users are selected among the users who have the binary file you are replacing, or who are eligible to install the binary file you are replacing. For example for Fire OS, if your app has APK1 and APK2, and your staged rollout replaces APK2, only users who already installed APK2 (or who are eligible to install it) are included in the staged rollout distribution.

The scope and workflow with staged rollouts

When you submit an upcoming version of your app for review, a dialog box appears where you can choose the rollout percentage.

Initial rollout

When you first create a staged rollout, you update the information on the app submission screens as usual, except you can’t edit the information in the Content rating section. However, during the staged rollout, users receive only the binary file, not any other metadata updates. For example, suppose you create a staged rollout and edit the description to explain a new feature in the release. Users who are included in the staged rollout won’t see the updated description. They receive only your updated binary file because only the app file is included in the staged rollout. When you initiate your staged rollout, the new version must be approved by the Appstore (as per compliance policies). It typically takes 1–2 days for the version in your staged rollout to be approved and go live. The Release Tracks screen indicates the percentage of users selected for the staged rollout and displays the rollout status.

Increment the rollout percentage

After your staged rollout is live, you can increment the percentage (ramping up from 1% to a full release at 100%), but you can’t lower the rollout percentage. No approval is needed for each incremental increase. The rollout percentage goes into effect immediately based on your selections. When you increase the rollout percentage, you can’t make changes, not even to your app’s binary file. After a staged rollout is underway, you can only increase the rollout percentage for the app file that has already been approved by the Appstore. This makes sure that customers install only tested binary files.

Halt a rollout

If you want to make changes (including replacing the app file), you must halt the staged rollout by selecting Halt Rollout from the Release Tracks screen. You then confirm that you want to halt the rollout. When you resume the rollout, your app will need to be tested and approved by the Appstore. After you halt the staged rollout, choose View on the release track that you’re updating. Now you can update your app’s binary file (perhaps replacing it with a file that fixes some issue you detected). When you’re ready to resume the staged rollout, click Submit for Review. Your app must go through testing and approval with the Appstore again, just as with the first version of your staged rollout. Users who have already downloaded the previous version of your binary file keep the version they downloaded. The Appstore never reverts versions of binary files that users already downloaded to their devices. However, these same users who were already targeted for the staged rollout (and who downloaded a previous binary file) get the new version of your binary when you resume your staged rollout.

Publish the version to all users for a release track

When you’re ready to publish your staged rollout app version to all users for the targeted release track, go to the Release Tracks screen and click Update Rollout. In the staged rollout dialog box, select 100% Full release. Then, click Submit. After the publishing process finishes, your app exits the staged rollout and goes live for all users for that specific release track. If you have other release tracks, their binary file status is unaffected. For example, if you perform a staged rollout for the Vega OS version of your app, it doesn’t affect the status of your Fire OS app. Your app doesn’t need to be retested by the Appstore before going live. Retesting and approval are needed only if you halt and edit your staged rollout.

Testing performed on staged rollouts

During staged rollouts, Appstore testing is performed during two periods only:
  • When you start a staged rollout: The Appstore tests and approves your app when you initially begin a staged rollout. For details, see Start a staged rollout.
  • If you halt, edit, and resubmit a staged rollout: If you halt and edit a staged rollout, and then republish your app’s binary file to resume the staged rollout, the Appstore will also test and approve your app file. For details, see Update the app file during a staged rollout.
When you increase your staged rollout percentage, such as from 1% to 5%, or from 5% to 10% or more, the Appstore does not need to test and approve your app.

FAQ for staged rollouts

The following are frequently asked questions (FAQ) related to staged rollouts.
Last modified on November 16, 2026