Prerequisites
The following are prerequisites to submit a Vega OS app:- You must have a VPKG file available as an app binary.
- Your app must register the
maincategory (com.amazon.category.main) in the app manifest. Without themaincategory, your app can’t launch from the Fire TV Home launcher and will fail the Amazon Appstore submission process. For more information, see Manifest [components] Section.
Considerations for targeting Fire OS and Vega OS devices
If you plan to target both Fire OS and Vega OS devices, you can submit the binaries using the same app listing in the console. For example, if you have an existing Fire OS version of your app, you can add the Vega OS version to your existing app. An individual app listing can have separate release tracks. When you use release tracks, your Fire OS and Vega OS app still share the same Amazon Standard Identification Number (ASIN), but you manage the binary files separately. Metadata and other app features, such as in-app purchasing, are shared across both versions. Although not recommended, you can also choose to submit your Vega OS binary as a new app submission for Vega OS devices only, separate from the Fire OS version of your app. If you have a paid app, or use in-app purchases, this method would require a customer to separately pay for each app and any in-app purchases. The following table lists the differences between submitting the Fire OS and Vega OS version of your app as part of the same app listing, and submitting them as a separate apps.| Area for consideration | Same app listing with release tracks | Separate app submission |
|---|---|---|
| App metadata | Metadata like app title, description, pricing, and screenshots, needs to be completed only one time. | You must maintain metadata like app title, description, pricing, and screenshots, separately for Fire OS and Vega OS apps. |
| In-app purchases | In-app purchase items added in the Developer Console are automatically available for both Fire OS and Vega OS apps. | You must separately set up in-app purchase items for the Fire OS and Vega OS apps. A customer who is entitled to content on the Fire OS app won’t be entitled to the content in the Vega OS app. |
| Customer reviews | Customer reviews for the Fire OS app and Vega OS app are shown together. | Customer reviews for the Fire OS app and Vega OS app are separate. |
| App discovery | When you search for the app on the Amazon retail website, only one app is listed. | When you search for the app on the Amazon retail website, the Fire OS app and the Vega OS app are listed separately. |
| Pricing | You can maintain the same pricing for the app and in-app items for both Fire OS and Vega OS. | You can maintain same or different pricing for the app and in-app items for Fire OS and Vega OS. However, the entitlements will not be interchangeable. |
| App acquisition | If a customer purchased the app on another compatible Amazon device, they own the app and the in-app purchases associated with the app. Whether the customer downloads the app on a Fire OS or Vega OS device, they retain access to their purchases. | The customer must purchase the Vega OS app and in-app purchases separately from the Fire OS app. |
- Your package name for both the Fire OS binary and Vega OS binary are the same.
- If your app supports in-app purchasing (IAP), your app has Vega IAP libraries integrated.
Manage app updates and versions
You can submit updated versions of your Vega OS app in the Developer Console. Defining an app version helps the Amazon Appstore determine which version to show your users. Versioning is critical because:- Other apps—including apps you publish as a suite—need to query the system for your app’s version to determine compatibility and identify dependencies.
- Services where you publish your app might also need to query your app for its version so that they can display the version to users. A publishing service might also need to check the app version to determine compatibility and establish upgrade or downgrade relationships.
Guidelines for maintaining multiple APKs and VPKGs
You can submit both APKs and VPKGs in the same app listing and must maintain versioning for both binary types. Since each binary has a distinct development process, follow these guidelines for versioning your APKs and VPKGs:- The Fire OS version codes and Vega OS build numbers are independent of each other. When you submit both APKs and VPKGs for an app, the Appstore checks the new version code with the version code of the previous APK submission, and checks the new build number with the build number of previous VPKG.
- For app updates, both the version code and build number need to be greater than the previous version code and build number respectively.

