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 Rollouts Overview

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.

Q: Can the staged rollout percentage increase automatically, based on a schedule I set?
No, you must go into the Developer Console and manually adjust the rollout percentages.
Q: Are there any country limitations or types of apps not allowed to participate in staged rollout?
Any app can participate in staged rollout. There are no restrictions around OS versions or device support. However, see the Requirements and limitations for staged rollouts section for details about app restrictions due to the minimum number of app installs, limitations regarding price or IAP changes, and more.
Q: My app has multiple binary files on the same release track. Can I create a staged rollout for one of the binary files?
Yes. Multiple binary files target different devices. The binary file you replace in a staged rollout will target the same devices and users as its corresponding live binary file. To maintain the same device support options, make sure you replace your existing binary (rather than deleting and then adding the new binary).
Q: Can I include specific users in my staged rollout?
No, the audience for staged rollout is randomly selected from your existing app's user base as well as prospective users whose devices support your app. For more details about audience selection, see How the staged rollout audience is selected.
Q: Does staged rollout work for both tablets and TV?
Yes, you can create a staged rollout for any app in the Appstore as long as it meets the requirements as outlined in Requirements and limitations for staged rollouts (for example, your app must have a minimum of 10,000 unique app installs to participate in staged rollout).
Q: Will I be notified by email when the staged rollout status changes?
There are several different email notifications sent: (1) When you submit your app, (2) If the Appstore rejects your app, (3) If you suppress your app, (4) When your app is live. You will not receive email notifications when changing the staged rollout percentage.
Q: If a customer doesn't already have the app, can they participate in staged rollout?
Yes, the list of users targeted for staged rollout is drawn from both your existing user base (those who already downloaded your app) and prospective users who are eligible (because of device support) to install your app. For details, see How the staged rollout audience is selected.
Q: For my Fire OS release track, should I complete the metadata fields prior to submission, even if customers won't see this information during the staged rollout?
Yes. If the Appstore ingestion team identifies an issue with the information (for example, you might have an image asset that has issues), they can identify this issue early so that you aren't delayed when you decide to go fully live. After your app is approved for staged rollout, you won't need to undergo testing and approval again when you decide to publish your app to all users.
Q: Can I use the future release date feature on the Release Tracks screen in combination with staged rollout?
Yes, you can set a future release date and still use staged rollouts. If you enter a future publish date (such as two weeks in the future), the staged rollout won't begin until that date.
Q: If I expand the country availability, will my staged rollout target users from that newly added country?
No, your staged rollout uses the same metadata information as your live app. If you select a new geolocation, no users in that location receive the update because your live app is not available in that geolocation.
Q: How can I see ratings and comments from users about my staged rollout version?
You have to use your own instrumentation and third-party app analytics to gather this information. Currently, no segmentation data is provided from Appstore for staged rollouts.
Q: Can I lower the staged rollout percentage?
You can't lower the rollout percentage. For strategies on how to downgrade the app version that users have, see Abandon the staged rollout version.
Q: How does staged rollouts differ from Live App Testing?
Live App Testing (LAT) is intended more for functional testing. With LAT, you have to manually specify the users who should test your app, and you're limited to 1,500 users max. LAT doesn't require your app to already exist on the Appstore, and you can push out the whole app (including the metadata information), not just the app file. In contrast, staged rollouts are intended more for performance testing. With staged rollout, users are randomly from the user base of your existing app or from prospective users who can install your app, based on the rollout percentage you select. You aren't limited to the number of users included in the staged rollout. Users receive the binary file only; apart from that, they continue to see the metadata from the live app. For more details, see How the staged rollout audience is selected.
Q: Can I leave an app in staged rollouts forever?
You should always complete the staged rollout, eventually submitting the app to all of your users for the release track. However, nothing in the Developer Console enforces that you complete the staged rollout. For more details, see Abandon the staged rollout version.
Q: What happens if I change the device support selections for the staged rollout app file?
Nothing adverse happens because the staged rollout gets pushed out only to users who either installed your live app or who are eligible to install your live app. In your staged rollout version, if you select a new device that your app supports, such as a new tablet device, the existing user base for your live app won't include any users with that new tablet device. Therefore, the staged rollout won't be pushed out to those tablet device users. Your staged rollout version uses the same device support options as your live app. If you select new devices for your app, the Appstore team tests your app on these devices, but the new devices aren't included in staged rollout distribution.
Q: When users are randomly selected, do the selections maintain the same geolocation ratios as the live app? For example, if the app was installed by 1,000 users (500 from the US, and 500 from the UK), does the staged rollout maintain the same proportion (that is, out of the 200 users, 100 are in the US and 100 in the UK)?
No, ratios of selected users are not balanced with on existing geolocation densities. The selection is purely random, independent of geolocation factors (except for matching the live app's geolocation availability).
Q: After the staged rollout, do you have to add an upcoming version of your app to make it available to all users?
No, you can submit the staged rollout version directly, without needing to create another upcoming version.
Q: Is the originating developer included in the staged rollout by default?
No, the originating developer is not included by default.
Q: After I submitted my app, the screen says "App Submission Successful" but the status is still "submitted" and I see an option to "Cancel App Submission." Since my app was already approved, why isn't it immediately live?
The publishing process can take as long as 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.
Q: With my app's staged rollout binary file, I selected a device that my live app doesn't support. Since staged rollout won't include any users with that new device, how will this new device be tested in the staged rollout?
The Appstore team tests your app against all supported devices you select, regardless of whether your staged rollout includes those devices.
Q: When selecting device support options for my staged rollout version, are there any indicators in device support that let me know my app won't be tested for that device?
No, there are no indicators in the UI letting you know this.
Q: If I make updates to my live app metadata, would the staged rollout version receive these updates as well?
Yes, your staged rollout version receives the same metadata as your live app, so any allowed updates you make to the live app would apply to your staged rollout as well. However, only certain updates to your live app are allowed, such as editing your description and images. You can't change the content rating or your app's binary file without creating a new version of your app. In your live app, you're unable to edit fields that would require a new version of your app. You can't create a new version in addition to the existing staged rollout version that you already created. For example, you can't change your live app's device support options because doing so would require you to create a new version. If you already have a staged rollout version for a release track, you can't create another new version that lives alongside the existing staged rollout version for that track.
Q: Is the user base for the staged rollout dynamic?
Yes, as a percentage, the rollout distribution can grow if your user base grows. For example, if 5,000 new users download your app, your staged rollout grows proportionally.
Q: Are users who haven't downloaded the latest version of the app (they have an older version) eligible for the staged rollout?
Yes, anyone who is eligible for the update receives it.

Last updated: Nov 16, 2026