This document provides an overview of Android Wear development for beginners. It discusses Android Wear 2.0 features like standalone apps, expanded notifications, and new input methods. It also covers common wearable devices, designing watch faces, and uploading wear apps to the Google Play Store. Tips are provided for avoiding common problems in wear development like connecting devices and testing wear applications.
4. Say “Ok Google” to ask questions and get stuff done
Get glanceable information throughout the day
Wide range of available sensors
Make the most of your time
A style for every mood
Works with your Android Phone or iPhone
5. Android Wear 2.0 Developer Preview
New User Interface
Material Design for wearables
Expanded notifications
Darker UI
6. Android Wear 2.0 Developer Preview
Standalone Apps
Direct network access to cloud
Apps run on watch even when your phone (Android or iOS)
isn’t with you
7. Android Wear 2.0 Developer Preview
Watch Face
Complications API: any watch face can show data from any
app
9. Android Wear 2.0 Developer Preview
Fitness
Google Fit Platform: automatic activity recognition and data
API
10. Range of devices...
LG G Watch (first development platform for Wear, first Qualcomm platform)
Samsung Gear Live (Samsung brand, OLED display)
Moto 360 (first TI platform, heartrate sensor, round LCD)
Sony Smartwatch3 (first Broadcom platform, first GPS, reflective LCD)
LG Watch R (first round OLED, WiFi development platform)
LG Watch Urbane (launched with WiFi, more compact size)
Huawei Watch (price challenger for US)
11. Why is there no fragmentation on Android Wear Devices? 🤔
16. Uploading your Wear app to Google Play
Currently...
Package the wearable .apk file inside the mobile module
Sign the mobile and wear module in release mode
Upload only the mobile-release apk since the wear module is
packaged with it
17. Uploading your Wear app to Google Play
With Android Wear 2.0 Developer Preview…
No need to package the wearable .apk file inside the mobile
module
No need to sign the mobile and wear module in release
mode
18. Common Android Wear Dev problems
Connecting the mobile device to an Android wear device
Connecting the mobile device with a wear emulator
Seeing changes in the watchface
Testing the wear application
Android Wear is a wearable platform designed for small, powerful devices, worn on the body. It is designed to deliver useful information when you need it most, intelligent answers to spoken questions, and tools to help reach fitness goals.
Maximize your everyday tasks at work or play. Google smarts deliver your commute info, directions, timely reminders, and more. Just say "Ok Google" to ask any question and check off to-dos – right from your wrist
Android Wear requires a phone running Android 4.3+ or iOS 8.2+
Available for sale at the Google Store, Best Buy or Amazon
Android Wear consists of a (open) Android OS and a (closed) Wear framework running on top of it, in charge of running the user interface, managing apps and communicating with the companion device (your phone).
This framework is owned and managed by Google as closed-source.
Google takes it very seriously to avoid fragmentation on this platform, and takes the ownership to maintain the Wear framework for ALL devices by themselves.
There are three different Ambient modes in Android Wear. The first is the regular ambient mode where the display is dimmed but it still supports antialiased text. There’s the low-bit Ambient mode that limits the colors displayed. There’s also the burn-in protection mode that shifts the screen contents a few pixels so the same pixels aren’t being used over and over.
Tell story of rejection on Google Play
Navigate to ~/Library/Android/sdk/platform-tools (This is the default path on Mac OS) and type ./adb -d forward tcp:5601 tcp:5601 to establish a connection on port 5601