Google Wear OS, formerly Android Wear, is the platform for wearable devices, watches primarily. In this talk, I would like to present what kind of applications may be developed for this platform, how it differs from regular Android development, what are the limitations, pitfalls and caveats.
In the deck I plan to cover the next topics:
- Kinds of applications available
- API available on the watch itself
- API for communication with a connected phone
- Watch face development specifics
http://uamobile.org/uk/topics/google-wear-os-watch-faces-and-applications-development
23. Ambient mode
Burn-in protection
• OLED and AMOLED screens
• EXTRA_BURN_IN_PROTECTION flag
in onEnterAmbient(…)
• Avoid having solid blobs
16x16 size in ambient
• Avoid placing elements or
frame on the edge
25. Low-bit Ambient mode
• EXTRA_LOWBIT_AMBIENT flag in
onEnterAmbient(…)
• When on, only few colors
available in ambient mode
• Anti-aliasing must be
disabled
27. Wear OS app on phone
• Wear OS watch must be paired
with phone
• Pairing happens through Wear
OS app
• Android & iOS versions available
• Watch is connected via BLE
28. Connected app
• Applications shares package
name
• Distributed in one app on Play
Store
• … but in separate APKs
• Play Store on the watch and
phone downloads own package.
29. Connected app API
• Data Layer API
• DataClient
• DataMap <—> DataMapItem <—> DataItem
• MessageClient
• Only for connected nodes
• <100k of data
• ChannelClient
• Transfer data using streams
• Media data
35. iOS Connected app API
• BLE 4.0 Services & Characteristics (GATT)
• BLE 4.1 L2CAP Connection-oriented Channels
✓ iOS since 11 version
– Android announced in Q