Android Wear 2.0 introduces several new features including: - Increased independence from phones through standalone apps and LTE support - Dark theme notifications for improved readability - Messaging style notifications with smart replies - 1D layouts to improve small screen navigation over 2D pickers - Material design navigation drawers and dark theme interface - Expanded Google Fit APIs and activity recognition including gym activities

1. Android Wear 2.0
New level of freedom for your action
Докладчик: Constantine Mars
Senior Developer @ DataArt,
Co-Organizer @ GDG Dnipro
+ConstantineMars

3. David Singleton, VP Engineering at Google

5. So… What’s coming in Android Wear 2.0?

6. Problem No.1: Tethering

7. Freedom from tethering
means “freedom without phone”

8. Officially supported by:
● LGE Watch Urbane
2nd Edition
● Huawei Watch
Android Wear 2.0
Preview is available for

9. Upcoming: access Market directly from watch

10. What makes custom Watch Faces different
but at the same time similar?

11. Complications
- “any feature in a timepiece beyond the simple display of hours and
minutes” (Wikipedia)

12. ● Short text
● Long text
● Range of values
● Icon (small picture)
● Image (big picture)
Complication types:

13. Complications coding

14. Each complication should have unique id
private static final int LEFT_DIAL_COMPLICATION = 0;
private static final int RIGHT_DIAL_COMPLICATION = 1;
public static final int[] COMPLICATION_IDS = {LEFT_DIAL_COMPLICATION, RIGHT_DIAL_COMPLICATION};
// Left and right dial supported types.
public static final int[][] COMPLICATION_SUPPORTED_TYPES = {
{ComplicationData.TYPE_SHORT_TEXT},
{ComplicationData.TYPE_SHORT_TEXT}
};

15. ComplicationData type stores complication
info (text, icon, type)
onComplicationDataUpdate() is initiated by Data Provider
private SparseArray<ComplicationData> mActiveComplicationDataSparseArray;
…
@Override
public void onComplicationDataUpdate(
int complicationId, ComplicationData complicationData) {
Log.d(TAG, "onComplicationDataUpdate() id: " + complicationId);
// Adds/updates active complication data in the array.
mActiveComplicationDataSparseArray.put(complicationId, complicationData);
invalidate();
}

16. Rendering complications
private void drawComplications(Canvas canvas, long currentTimeMillis) { // onDraw()
for (int i = 0; i < COMPLICATION_IDS.length; i++) {
ComplicationData complicationData = mActiveComplicationDataSparseArray.get(COMPLICATION_IDS[i]);
if ((complicationData != null) && (complicationData.isActive(currentTimeMillis))
&& (complicationData.getType() == ComplicationData.TYPE_SHORT_TEXT)) {
ComplicationText mainText = complicationData.getShortText();
canvas.drawText( mainText, 0, mainText.length(),
complicationsX, mComplicationsY, mComplicationPaint);

17. Data Providers
will stand behind the scenes as sources of data for
complications

18. One complication may use different
providers as the data source

19. DataProviders coding

20. Extend ComplicationProviderService
and declare it in AndroidManifest.xml
android.support.wearable.complications.ACTION_COMPLICATION_UPDATE_REQUEST
android:icon
android.support.wearable.complications.UPDATE_PERIOD_SECONDS
android.support.wearable.complications.PROVIDER_CONFIG_ACTION
<meta-data
android:name="android.support.wearable.complications.SUPPORTED_TYPES"
android:value="SHORT_TEXT"/>

21. ComplicationProviderService
internals
onComplicationActivated()
onComplicationUpdate()
onComplicationDeactivated()

22. Exposing data from provider
in onComplicationUpdate()
@Override
public void onComplicationUpdate(int complicationId, int dataType, ComplicationManager complicationManager) {
int randomNumber = (int) Math.floor(Math.random() * 10);
String randomNumberText = String.format(Locale.getDefault(), "%d!", randomNumber);
switch (dataType) {
case ComplicationData.TYPE_SHORT_TEXT:
ComplicationData complicationData = new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
.setShortText(ComplicationText.plainText(randomNumberText))
.build();
break;
...

23. Exposing data from provider
Trigger update with ComplicationManager.updateComplicationData()
@Override
public void onComplicationUpdate(int complicationId, int dataType, ComplicationManager complicationManager) {
...
if (complicationData != null) {
complicationManager.updateComplicationData(complicationId, complicationData);
}

24. What whas really distracting
in AndroidWear 1.X notifications?
White light when you receive notification

25. Visual updates to notifications in 2.0
Dark theme, Material Design for Android Wear

26. Large dark notification
Easier to read, but less-distracting in everyday life

27. Notifications and messages

28. Notification MessagingStyle

29. Allow smart replies,
based on Google Assistant
NotificationCompat.Action action =
new NotificationCompat.Action.Builder(R.drawable.ic_reply_icon,
getString(R.string.label), replyPendingIntent)
.addRemoteInput(remoteInput)
// 1) allow generated replies
.setAllowGeneratedReplies(true)
.build();

30. Use MessagingStyle for notification
Notification noti = new NotificationCompat.Builder()
.setContentTitle(messages.length + " new messages with " + sender.toString())
.setContentText(subject)
.setSmallIcon(R.drawable.new_message)
.setLargeIcon(aBitmap)
// 2) set the style to MessagingStyle
.setStyle(new NotificationCompat.MessagingStyle(resources.getString(R.string.reply_name))
.addMessage(messages[0].getText(), messages[0].getTime(), messages[0].getSender())
.addMessage(messages[1].getText(), messages[1].getTime(), messages[1].getSender()))

31. Response to notifications in AndroidWear 1.X
“Voice input”

32. More input methods
Handwriting, suggestions, keyboard

33. 1.38-inch full circle
P-OLED
480 x 480
348ppi
How full-size keyboard
works on the small
screen?

34. “Magic button” - center
of navigation concepts

35. The most complicated UI pattern of
AndroidWear 1.X?
- “2D Picker”

36. The answer to this problem in AndroidWear
2
- Recommended pattern is “1D Layouts”

37. App Layout examples

38. Material Design: Navigation and Action
Drawers

39. WearableDrawerLayout
and it’s internals
<android.support.wearable.view.drawer.WearableDrawerLayout
...>
<FrameLayout
.../>
<android.support.wearable.view.drawer.WearableNavigationDrawer
.../>
<android.support.wearable.view.drawer.WearableActionDrawer
.../>
</android.support.wearable.view.drawer.WearableDrawerLayout>

40. Material Design: Navigation and Action
Drawers

41. Material Design:
Dark Theme

42. Android Wear Area at Google I/O

43. GoogleFit infrastructure

44. Well known
GoogleFit APIs

45. GoogleFit: upcoming APIs

46. GoogleFit: upcoming features of existing APIs

47. GoogleFit - gym activity recognition

48. GoogleFit live demo on Google I/O

49. Activity recognition accuracy

50. Thank you!
+ConstantineMars
constantine.mars@gmail.com
Bring The Action!
and it’s only beginning of IT NonStop ;)