The document provides an overview of the Android Wear 2.0 developer preview, highlighting key features such as Material Design for apps, standalone applications, new watch face capabilities, and messaging options. It also discusses technical details related to layout definitions, authentication methods, complications API for watch faces, and distribution changes for apps. The document emphasizes the importance of user ease in app design and briefly mentions resources for developers.

1. Peter Friese
Developer Advocate, Google
What’s New in Android Wear 2.0

3. Android Wear 2.0
Developer Preview

4. Android Wear 2.0
1. Material Design for Apps
2. Standalone
3. Watch faces
4. Messaging
5. Fitness

5. New User Interface

6. design.google.com

7. Material Design for Wearables
google.com/design/spec-wear
Components and app
design patterns
Vertical layouts Darker colors

8. Vertical layouts

9. Vertical layoutMulti-directional layout

11. Darker colors

12. Purple
500
App primary color

14. Purple
500
App primary color

17. google.com/design/spec-wear

18. Components and app
design patterns

25. A B C D

29. WearableDrawerLayout

30. <WearableDrawerLayout>
<FrameLayout
android:id=”@+id/content” />
<WearableNavigationDrawer
android:id=”@+id/top_drawer”
android:layout_width=”match_parent”
android:layout_height=”match_parent” />
<WearableActionDrawer
android:id=”@+id/bottom_drawer”
android:layout_width=”match_parent”
android:layout_height=”match_parent” />
</WearableDrawerLayout>
Defining the layout

31. Android Wear 2.0 Support Library
dependencies {
...
compile 'com.google.android.support:wearable:2.0.0-alpha3'
}
build.gradle

32. google.com/design/spec-wear
g.co/wearpreview

33. Don’t forget
Wear apps are “real” apps
Always On Apps

36. Standalone Apps

37. Cloud and data
Cloud DistributeAuth Notify

38. Direct network
access
HTTP
REST

39. Direct network
access
● Bluetooth to Phone
Bluetooth
Proxy
● Wifi
● LTE/Cellular
Wifi,
LTE/Cellular

40. Cloud and data
HTTP REST
Data
Items
HTTP REST

41. Authentication
Auth DistributeCloud Notify

42. Standalone apps
must manage auth Valid auth
DataItems
Valid auth

43. But time awaits no
one...
Don’t ask for auth if you
don’t need it
Or postpone auth, store data
locally
Else, focus user ease

44. Use a login activity
Input fields with
android:inputType set to
textPassword for password
keyboard.

45. Google Sign-in and Smart Lock for Passwords offer
seamless sign-in.
Google Sign-in
Smart Lock
for
Passwords

46. Pass tokens via
Data Layer
This is fast and easy for
user, but does not work on
iOS.
Valid auth
Valid auth
?

47. Coming soon: Pass the user to OAuth flow on phone
OAuth
Service

48. Choosing auth methods
Fast and easy
for user
Works with iOS Works without
phone
Available
Google Sign-in Soon
SmartLock for Passwords Soon
Token over Data Layer Now
OAuth URL Soon
Activity on watch Now

49. Notifications and push
Auth DistributeCloud Notify

50. Cloud messages
can go directly to
Wear
FCM FCM
● GCM -> FCM

51. Use FCM to send cloud
messages to watches
● Payloads can be user visible and/or data
● Works well with Doze
● Cross-platform

52. Android Notifications bridge from phone to watch

53. Disable bridging in AndroidManifest.xml
<manifest package="com.example.standalone"
xmlns:android="http://schemas.android.com/apk/res/android">
<application ...>
<meta-data
android:name="com.google.android.wearable.notificationBridgeMode"
android:value="NO_BRIDGING" />
...

54. Distribution and installation
Auth DistributeCloud Notify

55. No more bundled
APKs! Phone APK
Embedded
Wear APK
Phone
APK
Wear
APK
● Smaller phone apks
● Decoupled release process
● Per-architecture apks

56. Watch Feature in Android Manifest.xml
<manifest package="com.example.standalone"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-feature android:name="android.hardware.type.watch"/>
...
</manifest>

61. Turn off phone app bundling of wear apps
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
wearApp project(':wear')
compile 'com.google.android.gms:play-services:8.4.0'
}

62. Complications API

63. Introducing complications
Sub Title

64. What’s a
complication?
In Horology, the study of
clocks and watches, a
complication refers to any
feature in a timepiece
beyond the simple display of
hours and minutes.
Source: Wikipedia

65. Bits Legacy

66. Watch faceData provider
Complications API

67. Watch face

68. Data provider

69. Design Guidelines

70. Short text Icon Ranged value
Long text Large imageSmall image

71. Where to position complications

72. Containing form factors

73. Building a strong relationship with
the watch face

74. Multiple complications

75. More opportunity to get creative

77. Using the API

78. Watch faceData provider

79. Watch face
Update request
Data provider
ComplicationData ComplicationData

83. watchface
complicationid = 2
watchface
complicationid = 1
Ranged Value
Long Text
Short Text
Icon
Ranged Value
Short Text
Icon

85. MyWatchFaceConfigActivity.java
Intent intent = ComplicationHelperActivity.createProviderChooserIntent(
getActivity(),
watchfaceComponentName,
watchFaceComplicationId,
new int[] {
ComplicationData.TYPE_RANGED_VALUE,
ComplicationData.TYPE_SHORT_TEXT,
ComplicationData.TYPE_ICON
});
startActivityForResult(intent, REQ_CODE);

89. MyWatchFaceService.Engine
@Override
public void onCreate(SurfaceHolder holder) {
...
setActiveComplications(watchFaceComplicationId1, watchFaceComplicationId2);
}
@Override
public void onComplicationDataUpdate(
int watchFaceComplicationId, ComplicationData data) {
// do something with the data
}

90. MyWatchFaceService.Engine
@Override
public void onDraw(Canvas canvas, Rect bounds) {
...
if (complicationData.isActive(currentTimeMillis) {
// draw the complication
}
...
}
@Override
public void onTapCommand(int tapType, int x, int y, long eventTime) {
// check if a complication was tapped
}

91. The watch face must have permission to show the
provider chooser and to receive data.
But these cases don't require permission:
Safe system providers
Provider and watch face from same app
Provider whitelists watch face as safe watch face
Permissions

92. AndroidManifest.xml
<uses-permission
android:name=
"com.google.android.wearable.permission.RECEIVE_COMPLICATION_DATA"/>

93. Watch faceData provider

94. MyComplicationProviderService.java
@Override
public void onComplicationUpdate(
int complicationId, int type, ComplicationManager manager) {
if (type == ComplicationData.TYPE_SHORT_TEXT) {
ComplicationData data;
data = new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
.setShortText(ComplicationText.plainText("hello"))
.setIcon(Icon.createWithResource(
getPackageName(), R.drawable.icon))
.build();
manager.updateComplicationData(complicationId, data);
}
}

95. AndroidManifest.xml
<meta-data
android:name="android.support.wearable.complications.SUPPORTED_TYPES"
android:value="RANGED_VALUE,SHORT_TEXT,ICON"/>
<meta-data
android:name="android.support.wearable.complications.UPDATE_PERIOD_SECONDS"
android:value="300"/>

96. TimeDifferenceText
TimeFormatText

97. MyComplicationProviderService.java
data = new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
.setShortText(new ComplicationText.TimeDifferenceBuilder()
.setReferencePeriodStart(startTime)
.setReferencePeriodEnd(endTime)
.setStyle(ComplicationText.DIFFERENCE_STYLE_SHORT_DUAL_UNIT)
.build())
.setEndTime(endTime)
.build();

102. Watch faceData provider
Complications API

103. Introducing complications
Sub Title

104. Android Wear 2.0
1. System UI and Material Design
2. Standalone
3. Watch faces
4. Messaging
5. Fitness

105. g.co/wearpreview

106. g.co/wearpreview
Bugs, API suggestions?
Android Wear Developer Preview Issue tracker
g.co/wearpreviewbug
Discussion
Android Wear G+ Community
g.co/androidweardev

107. Peter Friese
@peterfriese
Thank You!