The Amazon Mobile App Distribution Portal now offers the ability to submit separate APKs for Kindle Fire, Kindle Fire HD 7", Kindle Fire HD 8.9", and general Android (all non-Amazon) devices. You can find a brief overview of device targeting use in the Distribution Portal here. Below is a more detailed example of exactly how this new feature can be used.

In this example we will target all non-Amazon devices with one binary, and all Amazon devices with another binary. In order to accomplish this using our device targeting, you should create two APKs, following these steps:

Create your first binary—let’s refer to it as Binary1. Edit the Binary1 manifest.xml file so that it conforms to standard Android device targeting naming conventions. Let’s use a version name of { 1.0 } and a version code of { 1 }. Your package name stays the same for both binary(s).

NOTE: Binary1 is your non-Amazon device binary. Regardless of whether you will be updating this binary in the future, you will need to keep it as part of your future submissions for backward compatibility.

Create your second binary—let’s refer to it as Binary2. Edit your Binary2 manifest.xml file so that it conforms to device targeting naming conventions – this is done in your apps manifest.xml file. Let’s use a version name of { 1.0 } (note that version names must be the same) and a version code of { 2 } (note that version codes must be different). Your package name stays the same. Make sure that your version names for Binary1 and Binary2 are the same, and that your version codes for Binary1 and Binary2 are different.

NOTE: Binary2 is your Amazon device specific binary { xx.apk, 1.0 , 2 }. This will be submitted along with Binary1 later in the process.

You now have everything ready to submit your new app version to the Distribution Portal for testing.

1.     Sign into the Distribution Portal

2.     Go to My Apps > [choose your app]

NOTE: If you are creating a new app, you will need to select Add a New App and complete all of the tabs prior to the Binary File(s) before you will be able to upload your binaries. If you are simply creating a new version to an existing app, Add Upcoming Version (your metadata will be copied from the prior version).

3.     Fill out the fields for Binary1 (your non-Amazon version) and upload Binary1

a.     You will need to complete the prior tabs before being able to access the Binary File(s) tab

b.     Select whether or not you wish to have Amazon DRM applied to your app

c.     Click into the Binary File square to upload Binary1

d.Check/uncheck the appropriate boxes for which devices you want Binary1 to support—in this example, we unchecked all but the top box for All non-Amazon Android devices based on my manifest

e.     Select the languages your binary supports

f.      Be sure to check the Export Compliance checkbox

g.     The binary alias will default to Binary1—change the name as desired

4.     Select Save and Add a Binary

5.     Fill out the fields for Binary2 (your Amazon device version) and upload Binary2

a.     Select whether or not you wish to have Amazon DRM applied to your app

b.     Click into the Binary File square to upload Binary2

c.Check/uncheck the appropriate boxes for which devices you want Binary2 to support—in this example, we left the boxes checked for all Amazon devices: Kindle Fire (1^st Generation), Kindle Fire, Kindle Fire HD, Kindle Fire HD 8.9

d.     Select the languages your binary supports

e.     Be sure to check the Export Compliance checkbox

f.      The binary alias will default to Binary1—change the name as desired

NOTE: The server will automatically fill in any devices that are not yet supported in the Device Support section. If you do not have any further devices to support, the Save and Add a Binary button is no longer active. This is a good check to make sure you have addressed all available devices and everything has been accounted for.

6.     Select Save

If you update an app, make sure you are targeting (at least) the same set of devices as you did with your original version. For example, if you were supporting Kindle Fire (1st Generation), Kindle Fire, and Kindle Fire HD before, ensure that between Binary1 and Binary2 you are still supporting Kindle Fire (1st Generation), Kindle Fire, and Kindle Fire HD.

If you are switching to multi-binary in an app update, it is a good idea to add a release note (the Release Note tab will appear when you update an app) indicating that you are addressing backward compatibility to set proper expectations for your users. Something like the following would be appropriate: “This update addresses backward compatibility for non-Amazon devices in the Amazon store.”

Don’t forget to Submit Your App for testing after making your updates in the Distribution Portal!