Starting today, developers have the opportunity to participate in a Developer Preview of Fire OS 5, the next generation Android-based operating system that powers Fire tablets, Amazon Fire TV and Fire TV Stick. And because Fire OS 5 is based on Android Lollipop, we can make this update while preserving even more compatibility with existing Android apps than ever before. This means that even more of your apps should work on Fire devices with no additional engineering effort. There are several ways you can participate in the Fire OS 5 Developer Preview.
To ensure your app is available to millions of customers on the next generation of Amazon devices, you can now participate in the Fire OS 5 Developer Preview. As an Amazon Developer, we’re offering you early access to Fire OS 5. You can now see your app running on a Fire HD 6 or Fire HD 7 tablet, and identify any app compatibility issues well in advance of our new Fire OS launch later this year.
To participate in the Fire OS 5 Developer Preview, click here.
Amazon Testing Service is a free tool that allows you to test your app for compatibility on Fire and Android devices. We’ve updated Amazon Testing Service to provide feedback on your apps compatibility with Fire OS 5 and Android Lollipop. To test your app, simply drag and drop your Android APK into the App Testing Service on the Amazon Developer Portal homepage page. In about 90 seconds, you will get compatibility results for Fire OS 5 and Android Lollipop.
Now is the time to get started. Check out the resources below to learn more about Fire OS5 and the Amazon Appstore
Want Amazon Developer blogs delivered to your inbox? Stay in the loop on the latest industry best practices, Amazon promotions, and new launches by subscribing to our weekly blog summary here.
Today we are pleased to release new Android and iOS SDKs for mobile developers interested in supporting Amazon Cloud Drive. These new additions are a part of the existing Amazon Mobile App SDK and can be downloaded directly from the Developer Portal. The updates will allow you to provide Unlimited Storage benefits for your customers using your apps more quickly and efficiently.
You can now quickly write new apps or make your existing apps interact with Amazon Cloud Drive using both the Android and iOS SDKs. With these updates you no longer need to understand and implement a separate instance of Login with Amazon. We’ve even taken care of the best practices of implementing a back-off strategy. Best of all, you can communicate with the Amazon Cloud Drive API without ever needing to worry about networking code.
Additional benefits include the ability to work exclusively with native Java and Objective-C object types, removing the need to ever parse JSON, as well as eliminating the need to refer back to the REST API documentation online. You also no longer need to explicitly use the Amazon Cloud Drive API to get Account endpoints, removing an entire step from your development workflow.
With the launch of the Amazon Cloud Drive mobile developer SDKs, we are also excited to announce new third-party apps supporting Cloud Drive through the Android and iOS SDKs.
A+ Gallery (Android): iPhone style photo gallery.
PhotoTime (iOS): Explore your photos at snapshot speed.
TextMaker HD Basic (Android): Create and edit documents on your tablet.
PlanMaker HD Basic (Android): Create and edit spreadsheets on your tablet.
Presentations HD Basic (Android): Create and edit presentations and slide shows on your tablet.
And, coming soon:
FiLMiC Pro (iOS): Turn your iOS camera into a broadcast worthy 2K HD video camera.
Vizzywig (iOS): All-in-one, movie-making application for iPhone, iPad, and iPod touch that lets you record, edit, and preview in real time.
Cleen (iOS): Clean up your camera roll and photos in your Amazon Cloud Drive account.
For more photo, video and productivity apps be sure to check out the Amazon Cloud Drive App Gallery. You can also visit the Developer Portal to download the Amazon Mobile App SDK or to learn more about the Amazon Cloud Drive API and SDKs for Android and iOS. If you have any questions about getting started you can visit our Developer Forum.
If you have published an app on Amazon that uses v1.0 of the Facebook Platform API, you have until April 30, 2015 to ensure your app works properly with v2.0 of the API. Beginning April 30, v1.0 API requests will be processed as v2.0 API requests. This may break your app’s functionality unless it is built with a recent version of the Facebook SDK or you have custom code that explicitly calls v2.0 of the API (or higher).
Detailed information about the nature and scope of this update by Facebook is available from their Facebook Platform Upgrade Guide. You can get specifics on the migration process from Facebook’s Upgrading from v1.0 to v2.0 page.
Whenever a public API is updated, there is the potential to break applications that rely on it. API providers want to avoid this, of course, so they usually do two things. First, they assign a unique version number to each release, so developers can be specific about which functionality we are requesting. Second, they support both old and new API versions simultaneously, for a time, allowing our apps to continue to function until we can upgrade them to use the newest API.
Facebook did both of these. They first released their Platform API in April 2010, updating it several times since then and always attaching a new version number to each release. They have also continued to support previous API versions, so even if a developer were slow to upgrade, his or her apps would continue to work as expected.
That finally changes on April 30, 2015. That’s the day that Facebook will officially turn off support for v1.0 of the Facebook Platform API. Versions 2.0, 2.1, 2.2, and 2.3 of the API are already available (and have been for some time), so starting April 30, new and existing apps will be expected to use one of these versions, if they don’t already.
Luckily for most developers, Facebook provides SDKs for several platforms and languages, which makes handling API versions largely automatic. If you develop your app using a recent version of one of these SDKs, chances are you will not be affected when the Facebook Platform API v1.0 is deprecated. See Facebook’s Platform Versioning page for more information.
If you did not build your app using a recent Facebook SDK, or you have custom code that constructs unversioned API requests, your app may break on April 30. There are several significant differences between v1.0 and v2.0 of the API besides functional changes and improvements, including updates to permissions and user login. You should review the complete list on Facebook’s Upgrading from v1.0 to v2.0 page. There you will find detailed documentation explaining the impact of every change, how to adjust your app to deal with them, and how to invoke versioned calls manually if you still prefer not to use a Facebook SDK.
Here are just a few of the areas affected by the migration:
Unless you know for sure that your app uses v2.0 or later of the Facebook Platform API, you should assume that it will require an update. However, API v2.0 is used by default by Facebook’s Android SDK starting with version 3.14, so if you built your app after April 2014 using that SDK or a later version of it, no update is needed.
Keep in mind that v2.0 of the Facebook Platform API is itself scheduled to be deprecated eventually; after April 30 it will simply be the oldest version still supported. Facebook has committed to maintain each API version for not less than two years after it is introduced. See the Facebook Platform Changelog for more information.
If you believe your Amazon mobile app or game may be affected by Facebook’s deprecation of it’s v1.0 API, it is highly recommended that you visit the version-specific upgrade page mentioned above, or the more general Facebook Platform Upgrade Guide.
- peter (@peterdotgames)