How to Upload Your App on Amazon Appstore for Android

The phrase upload app on Amazon Appstore needs an important 2026 correction. Amazon discontinued its Appstore for general Android mobile devices on August 20, 2025. Developers can no longer submit or update apps for ordinary Android phones through that program. The Amazon Appstore remains available and supported on Fire tablets, Fire TV, and Fire TV built-in products.

That distinction changes the publishing plan. You are not adding a second phone marketplace. You are deciding whether your Android app can serve Amazon's supported device families, then preparing the correct Fire OS experience, binary, listing, testing evidence, and compliance details.

This guide covers that current workflow. It also explains where a WebInto.app Android build can provide a starting point and where device-specific development may still be necessary. Submission creates an opportunity for review, not a promise of acceptance.

Understand What the Amazon Appstore Supports in 2026

Amazon's official discontinuation notice says support for the Amazon Appstore on Android mobile devices ended on August 20, 2025. The submission release notes further state that developers can no longer submit or update apps for those devices.

Current targets include:

Fire tablets running Fire OS
Fire TV devices running Fire OS
Fire TV built-in products
Supported Fire TV products running Vega OS, which use a different package format

An Android APK or AAB does not automatically become a good television app. A touch-first ordering screen may work on a Fire tablet but be unusable with a Fire TV remote. Conversely, a streaming interface designed for a ten-foot display may not suit tablet navigation.

Fire OS and Vega OS are different targets

Amazon's current submission overview accepts an APK or Android App Bundle (AAB) for Fire OS. A Vega OS app uses a VPKG. Amazon allows Fire OS and Vega OS binaries in one listing when they represent the same app and follow its package and versioning rules, but the development processes are separate.

WebInto.app is an Android-focused website-to-app builder. It produces Android APK and AAB files, not a Vega OS VPKG. A WebInto.app build may therefore be evaluated for compatible Fire OS tablets, but it is not a one-click Fire TV or Vega conversion. Fire TV usually needs remote navigation, focus states, landscape layouts, media controls, and launcher declarations.

Before opening the Developer Console, choose one supported target and test that experience seriously.

Prepare the App, Account, and Publishing Materials

Amazon says a developer needs a developer account, app binary, descriptions, image assets, and a physical device for testing. Registration is available through the Amazon Developer Console, and Amazon's submission documentation describes the account as free.

Prepare these items under business-controlled credentials:

Amazon developer account with current contact and payment details
Final package name, such as com.example.reader
Signed release APK or AAB for Fire OS
App icon, screenshots, promotional artwork, title, and description
Privacy policy URL and support contact
Content rating and data-use answers
Release notes and supported-language copy
At least one physical target device

Protect the signing identity

Android updates must be signed consistently. Keep the app signing key, alias, and passwords in controlled backups. If an existing Google Play app uses Play App Signing, do not assume the upload key is the key that signs installed copies. Google's Play App Signing guidance explains options for obtaining a signed universal APK or supplying your own common app-signing key when distributing outside Play.

WebInto.app manages the keystore for builds created on its platform and provides APK and AAB outputs. Record which signing certificate belongs to the Amazon listing before the first production submission. Changing certificates later can break the update path.

Audit dependencies before porting

Fire OS is based on Android, but Google Mobile Services are not a safe assumption. Inventory every SDK and feature:

Google Sign-In
Firebase Cloud Messaging
Google Maps or Play Services location
Google Play Billing
Play Integrity
Advertising and analytics SDKs

Replace or gracefully disable dependencies that are unavailable on the target device. For a WebView app, test authentication, file uploads, downloads, geolocation, camera access, deep links, video playback, and payment redirects. A successful APK install is not proof that the complete user journey works.

Adapt and Test for Fire Tablets or Fire TV

Testing on a physical device is an explicit part of Amazon's current submission preparation. Choose hardware that matches the customers you intend to reach.

Fire tablet checklist

For a tablet app, test portrait and landscape modes, different screen sizes, soft-keyboard behavior, low-memory recovery, back navigation, and offline errors. Confirm that touch targets remain readable and that the website does not force a desktop layout.

If the app wraps a website, provide a useful no-connection experience. The custom offline screen guide explains one approach for WebInto.app projects. Also verify every requested permission has a visible user benefit and matches the privacy policy.

Fire TV checklist

Fire TV requires more than resizing:

Every interactive element must be reachable with directional controls
Focus must be visually obvious
Back and Home behavior must be predictable
Text must be readable from a typical viewing distance
Video playback must work with remote media controls
Login must not depend on awkward text entry
Orientation should suit television displays

Amazon documents required manifest and launcher behavior in its submission materials. For Vega OS, the submission overview specifically notes the com.amazon.category.main category. Follow the platform documentation for the binary you are building rather than copying an Android phone manifest.

A realistic example

Consider Mira, who publishes a cooking-membership website. Her WebInto.app APK works well on a Fire tablet: members sign in, browse recipes, save favorites, and watch embedded lessons. Testing reveals that Google Sign-In does not work on the tablet, so she adds email login and updates her privacy disclosure.

Mira does not submit that same touch interface for Fire TV. She commissions a separate TV-oriented build with remote focus, large recipe cards, and media controls. Both products share a brand and backend, but they are tested and versioned as device-specific clients. This avoids treating compatibility as a checkbox.

Once the intended experience survives real-device testing, the Developer Console work becomes straightforward.

Create the Listing and Upload the App File

Sign in to the Developer Console, add a new app, and select the relevant app type and device support. Amazon's submission workflow organizes submission into four broad steps: app file, Appstore details, availability and pricing, and review and submit.

Upload the correct binary

In the app-file step, upload an APK or AAB for Fire OS. Upload a VPKG only for a Vega OS app. Amazon's app-file documentation says it can convert a Fire OS AAB into optimized APKs with bundletool. It also permits multiple binaries where device differences require them, such as separate Fire TV and Fire tablet APKs.

Check the processing result for:

Package-name accuracy
Version code higher than the previous Fire OS release
Supported architecture and screen declarations
Minimum and target SDK compatibility
Requested permissions
Device targeting
Errors or warnings generated from the manifest

If uploading an APK produced outside Android Studio, verify signing and zip alignment. Amazon notes that such an APK might need zipalign; this does not apply to an AAB or VPKG.

Write a device-specific store listing

The store listing should describe the product users will install on Amazon hardware. Do not recycle claims from Google Play if the Fire edition lacks a feature.

Use a clear title, concise feature bullets, truthful category, support email, and screenshots captured on the target form factor. Tablet screenshots should show tablet UI. Fire TV artwork should be legible at television scale. Localize copy only where support and in-app content are also usable.

For the focus keyword, use natural language such as "upload app on Amazon Appstore" in supporting content, not repeated blocks of awkward metadata. Accurate screenshots and benefits matter more than keyword repetition.

Complete Availability, Pricing, Privacy, and Compliance

Choose marketplaces based on content rights, customer support, legal obligations, and actual device availability. Amazon's console may expose country and region choices that do not correspond one-to-one with supported device marketplaces, so review the current console help before launch.

Pricing and in-app purchases

Decide whether the app is free, paid, or uses in-app purchases. A purchase flow built only around Google Play Billing will need redesign for Amazon distribution. Confirm current Amazon Appstore billing requirements before shipping digital goods or subscriptions.

Do not promise that an existing purchase transfers between stores unless your account system and terms support that behavior. If access is tied to a web subscription, test sign-in and entitlement restoration on the Fire device and explain the arrangement clearly to reviewers.

Privacy and data disclosures

Your privacy policy should name the data processed by the app and integrated services. Review login credentials, account identifiers, device information, analytics, crash logs, advertising identifiers, location, camera, microphone, and purchase history.

Store answers, privacy policy, and actual runtime behavior must agree. If your listing says the app does not collect location while the binary requests location at startup, expect questions. Remove unused permissions and document necessary ones.

Content and intellectual property

Confirm rights to logos, video, music, books, streams, and user-generated content. Explain moderation and reporting controls where users can publish material. For streaming products, verify territorial rights before selecting broad availability.

Compliance work is not a one-time form. Save a copy of every answer so future releases can be checked against it.

Submit for Review and Operate Future Releases

Use the review step to inspect the binary, device support, listing, availability, pricing, and declarations as one package. Provide working reviewer credentials and concise test instructions for gated content. If a feature needs special hardware or an account state, explain how to reach it.

Amazon evaluates submissions against technical and content policies. Review duration varies, and a complete submission does not guarantee acceptance or a particular date. Monitor the console and account email for questions.

Handle feedback methodically

When Amazon reports a problem:

Identify whether it concerns the binary, listing, policy, or test access.
Reproduce it on the targeted Fire device.
Fix the smallest complete cause.
Increment the required version value for a new binary.
Update disclosures or screenshots if behavior changed.
Reply with exact reproduction and resolution notes.

Avoid repeatedly uploading speculative builds. A focused response is easier for both the publisher and reviewer to verify.

Maintain releases after publication

Track the Amazon version separately from Google Play and other channels. Fire OS version codes must increase relative to previous Fire OS submissions. If one listing also includes Vega OS, Amazon says Vega build numbers and Fire OS version codes are independent, and each must increase relative to its own prior binary.

Use staged internal QA even if the app's content is mostly remote. Test security updates, SDK changes, certificate expiry plans, OS updates, and backend compatibility. Keep the store listing and release notes current. For broader Android operations, the Google Play upload guide provides a useful comparison, but its AAB, testing, and policy workflow does not replace Amazon's rules.

Conclusion: Upload an App on Amazon Appstore for the Devices It Still Serves

To upload app on Amazon Appstore in 2026, start with the supported destination: Fire tablets, Fire TV, Fire TV built-in products, or a qualified Vega OS target. General Android mobile distribution through Amazon ended on August 20, 2025.

Prepare the right binary, preserve the signing identity, remove incompatible service assumptions, test on physical hardware, and make the listing and privacy answers match the delivered product. WebInto.app can supply an Android APK or AAB for evaluation on compatible Fire OS use cases, especially tablet-oriented website apps, but it does not generate a Vega OS package or automatically create a remote-ready TV interface.

Treat Amazon as its own release channel with its own users, compatibility matrix, and update history. That approach produces a stronger submission and a maintainable product without implying that review acceptance is assured.

FAQ

Can I publish an Amazon Appstore app for ordinary Android phones in 2026?

No. Amazon discontinued the Amazon Appstore for Android mobile devices on August 20, 2025, and its release notes say developers can no longer submit or update apps for those devices. The store remains supported on Fire tablets, Fire TV, and Fire TV built-in products.

Does Amazon Appstore accept APK or AAB files?

For Fire OS, Amazon currently accepts a signed APK or Android App Bundle. Amazon processes an AAB into optimized APKs. Vega OS uses a VPKG, so an Android APK or AAB is not a substitute for a Vega build.

Can a WebInto.app build be submitted to Amazon?

WebInto.app produces Android APK and AAB files, which may provide a starting point for a compatible Fire OS tablet app. You still need to test dependencies and behavior on real Fire hardware. It does not produce an iOS binary or Vega OS VPKG, and a touch-first wrapper is not automatically suitable for Fire TV.

Should I use the same signing key on Google Play and Amazon?

Using one app-signing identity can preserve compatibility for users moving between channels, but the setup must be planned before release. If Play App Signing generated the key, follow Google's official options for downloading a signed universal APK or configuring a common key. Never confuse the Play upload key with the installed app-signing key.

How long does Amazon Appstore review take?

There is no reliable universal timeline. Complexity, first-time account checks, device compatibility, reviewer access, and policy questions can all affect review. Submit complete materials, watch the Developer Console, and plan launch communications only after the release status is confirmed.