- Posted by Hoi Lam, Developer Advocate
Today, we are releasing the fifth and final developer preview for Android Wear 2.0. In this release, we have added iOS support and included a number of bug fixes and enhancements. Apps compiled with this preview are now ready for final submission to the Google Play Store, so it's time to publish your apps. As Android Wear 2.0 approaches its final release in early February, we would like to thank you for your continued feedback during the developer preview program. Your input has helped us uncover bugs as well as drive critical product decisions. Thank you!
<application …> <meta-data android:name="com.google.android.wearable.standalone" android:value="true"/> … </application>
The available network bandwidth for standalone apps can be lower than expected, as the platform balances battery savings vs network bandwidth. Make sure to check out these guidelines for accessing the network, including accessing Wi-Fi and cellular networks on watches paired with iPhones.
Also with this developer preview release, Android Wear apps running on watches paired with iOS devices will be able to perform phone hand-off flows such as OAuth and RemoteIntent for launching a web page on a paired iOS device.
Uploading Your App to the Google Play Store
Other Enhancement and Bug Fixes
- Navigation Drawer: Flip a flag to toggle to the single-page, icon-only navigation drawer, which provides faster, more streamlined navigation to different views in your app.
- NFC HCE support: NFC
Host Card Emulation
FEATURE_NFC_HOST_CARD_EMULATIONis now supported.
- ProGuard and Complication API: New ProGuard configuration means complication data container classes will no longer be obfuscated. This fixes a ClassNotFoundException when watch faces are trying to access data supplied by a complication data provider.