Working Around Google Features

Because the Kindle Fire isn’t a “true” Android device (it doesn’t use the official Google Android source code but instead uses its custom version), it doesn’t have access to any of the closed-source Google services that you might already be using. In addition, the device itself may not have certain features that you’re accustomed to:

Google Maps: If you’re using the Google Maps library to bring maps to your Android application, you can’t use this library on the Kindle Fire.

Location services: You cannot use Maps, and neither do you have access to location services on the Kindle Fire. It has no GPS or Wi-Fi–based location services, so you have no way to tell where the device is physically located.

Google Play Store in-app purchasing: If your app uses in-app purchasing to allow users to purchase from inside it, you can’t use this same API in your Kindle Fire app. Luckily, Amazon has a version of in-app purchasing that you can use on the Kindle Fire.

Camera, microphone, Bluetooth, 3G, external storage: The Kindle Fire has none of these items, so if your app uses them, either find a way around the limitation or consider not releasing your app on the Kindle Fire.

Honeycomb, Ice Cream Sandwich, Jelly Bean: Amazon uses the version of Android source code before Honeycomb was released, so the Kindle Fire has no access to any of the features in these three versions. In particular, you’ll notice that the Kindle Fire has a unique look and feel that is unlike any other Android tablet. See Chapter 1 for the features that come with these three Android versions.

Even without these features and services, many Android applications work on the Kindle Fire with little or no modification. If this includes your app, read on.