High-level review of submission prerequisites
Publishing to the Amazon Appstore requires the following:- Amazon customer account: If you do not have an Amazon customer account, create one at Amazon.com.
- Amazon developer account: If you do not have an Amazon developer account, go to the Amazon Developer Console, and sign in with the same email address as your Amazon customer account. The console will guide you through the account creation process.
- An app that you want to publish to the Amazon Appstore: Each app that you submit must comply with Amazon’s content policy. If Amazon determines that an app contains, facilitates, or promotes content prohibited by these guidelines, Amazon will reject the submission. For details, see Amazon Appstore Content Policy.
- Image assets for product promotion. You must provide screenshots and large and small icons for promoting your app on the Amazon Appstore. You may optionally provide a promotional image and videos. For details, see Image asset guidelines.
- Intellectual Property (IP) Documentation (if needed): If your app uses intellectual property (IP) from a third party, be prepared to submit documentation that you have obtained the proper license or permission to use that IP in your app.
Overview of the app submission process
The following high-level overview can help you understand the general process for submitting an app to the Amazon Appstore:- Develop or Port: Develop your app from scratch or port an existing Android app for publishing in the Amazon Appstore. For details, see Port Existing Android App to Fire OS. Keep in mind the Amazon Appstore Content Policy as you design your app.
- Test: Make sure that your app meets the Test Criteria for Amazon Appstore Apps. You can also use one of Amazon’s testing services to validate your app’s functionality. For details, see App testing tools and services.
- Submit Your App: Sign in to your developer account, enter the appropriate information for your app’s listing in the Amazon Appstore, and upload your app. For details, see Submit Your App to the Amazon Appstore.
- Respond to any failure notifications (if needed): If your app fails any submission criteria, you will receive a notification that the app has been rejected. Fix your app as directed, and resubmit your app. For details, see Overview of the app approval process.
- Update your app (as needed): If you need to make changes to an app that has already gone live in the Amazon Appstore, see Update a Published App.
General tips for successful app submission
Use the following recommendations to make your publishing experience as smooth as possible.Accounts and email communication
- Your Amazon customer account is tied to your Amazon developer account. Any changes you make to the sign-in credentials of your Amazon customer account are propagated to your Amazon developer account, and vice versa.
- Amazon sends email to only the address associated with the account owner when corresponding with you about your app’s status. When you set up a new Amazon developer account, you are the default account administrator and the designated owner for the account. You can add other people in other roles to the account, such as analyst, developer, or marketer. You can also add other administrators. Although any developer or administrator can submit an app, Amazon sends correspondence to only the email address associated with the account owner. That means Amazon does not send messages to the email account associated with the person who submitted the app, unless it’s the same as the account owner’s email. To confirm the account owner email address, anyone with administrative permissions can go to My Settings > User Permissions and review the Roles column. The account owner is indicated as “Administrator (owner)”.
App preparation for Fire OS
- Version Name: In your
AndroidManifest.xmlfile, use theandroid:versionNameattribute for version information to display to users. On the Amazon Appstore, theandroid:versionNameis required, can be any string, and must be fewer than 50 characters. - Version Number:
android:versionCodemust increase for each successive version of your app. As per the Android documentation on <manifest>, theandroid:versionCodeinAndroidManifest.xmlmust be an integer whose value increases each time a new version of your app is released. If your app’sandroid:versionCodedoes not follow this convention, customers will not receive the new version of your app. - Device filtering: In your
AndroidManifest.xmlfile, specify which Android devices you are targeting with your app. For details, see Device Filtering and Compatibility on Fire OS.
Devices supporting only 64-bit apps
Some devices no longer support 32-bit apps, including any 32-bit apps currently available on Amazon Appstore. Customers attempting to download a 32-bit app on one of these devices will receive a notification alerting them that the app is not compatible with system requirements. To make your app available to customers using one of these devices, add 64-bit (arm64-v8a) support to your app and submit an update using the Amazon Developer Console. Do not remove support for 32-bit (armeabi-v7a) while building your app, as it may impact current Amazon device selection.Best practices for 64-bit file submission
The Amazon Appstore accepts hybrid 32-bit/64-bit binary file submissions for some Fire tablets (11th generation and above). This means to reach all Amazon devices, you should develop with 64-bit in mind. These two library folders must have the correct files:- 32-bit folder: lib/armeabi-v7a/
- 64-bit folder: lib/arm64-v8a/
Preparing your binary file
This section discusses Amazon’s recommendations for creating the binary file that you will submit for your app.Zip-aligning your APK
This section applies only to APKs, not app bundles or VPKGs. When you generate your APK from Android Studio, your APK is aligned by default. (Alignment refers to optimization of the APK files.) However, if you’re not using Android Studio to generate your APK, you might need to zip-align your APK before you upload it during app submission. For details, see zipalign in the Android documentation. If you submit an unaligned APK, the Developer Console will reject it, with a message saying, “The submitted APK does not appear to be zip-aligned. Please zip-align your APK and resubmit your application.” If you see this message, you can zip align your APK with Android Studio by running the following command:[Android SDK location] with a path such as /Users/johndoe/Library/Android/sdk.)
In addition to zip-aligning your APK, if you’re using AndroidX library for multidexing, keep the AndroidX library unobfuscated in your code by adding this line to your Proguard file:
Amazon app signatures
When you submit your app, Amazon removes the signature you used to sign your app and re-signs it with an Amazon signature that is unique to you, does not change, and is the same for all apps in your account. You can find the Amazon signature hashes for your account when you create an app in the Developer Console. The SHA-1, MD5, and SHA-256 hashes for your account are listed with your app release. To access Appstore certificate hash values- Sign in to the Developer Console.
- Go to Apps & Services > My apps and open your app listing.
- From the sidebar, click Release Tracks, and then click View on a release track.
- At the top of the screen, click Appstore Certificate Hashes.
Amazon’s code wrapper
When you submit an Android binary file to the Amazon Appstore, Amazon adds a wrapper to your code that includes metadata and an application signature. This code has the following purposes:- To collect analytics relating to the app
- To evaluate and enforce Amazon program policies
- To share aggregated information with you and others regarding the program
- To modify and add to your binary so Amazon can (at your option) enforce digital rights management (DRM)
- To add metadata to your binary so Amazon can improve your its compatibility with Amazon devices
App size limitations
Uploaded binary files can be up to 2.5 GB in size. Amazon recommends that you deploy small apps that download and install quickly. Then, upon first launch, your app can download additional resources and save them on the user’s local file system. For Android binary files, expansion files or Binary blobs (.obb) are not supported by the Amazon Appstore. If you’re submitting an APK, you must do so without .obb files. Make sure your app installs external resources in the proper path after downloading them at runtime.App size warning messages
Consider minimizing the size of your app to 50 MB or less. Reducing the app size increases accessibility by allowing more users to install it and decreases the installation time. Additionally, when dealing with storage constraints, users are less likely to uninstall smaller apps. If you upload a binary file that is greater than 50 MB, or has increased in size by greater than 10 percent from your previous submission, the Developer Console displays one of the following warning messages when you upload your binary. For guidelines on how to reduce your Fire OS app’s size, see App size reduction guidelines.App size reduction guidelines
To reduce your Fire OS app’s size, use the following guidelines:- Fonts: Consider using system-provided fonts instead of bundling fonts as part of your app. Fire TV supports system fonts for all supported regions.
- Audio: Audit whether you must bundle uncompressed audio WAV files in the APK or whether they can be downloaded on demand. If these files must be in the APK, convert them to a compressed format such as MP3. Also, re-encode these files with mono, VBR, and a lower bit rate. These techniques help reduce the size of the audio files without any customer perceived quality loss.
- Images: Audit your app’s use of image files and remove unnecessary images. For required images, use the WebP image format, which gives higher compression efficiency. You can convert images using Android Studio by right clicking on the image and selecting “convert to WebP”.
- Code: Enable Proguard or R8 to optimize the build process. Make sure to use code minification and resource shrinking flags during compilation.
-
Native libraries:
- Make sure you bundle only armeabi-v7a binaries as part of the APK.
- Make sure to properly strip all debug symbols from the final build.
- Carefully audit and limit exported symbols to only those essential for the library’s intended functionality.
Screen resolutions
When creating your app, you should consider multiple screen sizes and resolutions. The primary screen size categories are:- Small screen
- Normal screen
- Large screen
- Extra-large screen
- Low density (120 dpi)
- Medium density (160 dpi)
- High density (240 dpi)
- Extra high density (320 dpi)
Designating apps as high density (HD)
To ensure that customers have a great HD experience on Fire tablets, your app must meet the following requirements to gain an “HD” designation in the title of your app:- The app is designed for high-density screens (hdpi or xhdpi) and declares this support in the manifest
- The app’s drawables are optimized for high-density screens (images can be rendered at native resolution)
- The app uses the entirety of the screen (without letterboxing)
- Video content in the app (if applicable) must be at least 24 frames per second and 720p (in video-focused applications)
Specifying an installation location for your Fire OS app
On Fire OS, your Android Manifest file specifies the installation location for your app on Fire TV and Fire tablet devices. For most apps, setting this value to External Storage (preferExternal) will provide a better experience for your app’s users. For more information, see the following:
- Specifying Your App’s Installation Location (Fire Tablets)
- Specifying Your App’s Installation Location (Fire TV)

