Wearables are one of the hot topics of the year. No – I am not talking about T-shirts with embroidered flashing charts. Rather, let’s consider gadgets like Pebble, Oculus Rift, and Google Glass. Besides being geeky pieces of technology (and who of us wouldn’t enjoy playing around with gadgets), they mark the beginning of a whole new era of computing.
Until now, using a computer usually meant interacting with a conglomeration of metal, silicon and other materials that could more or less clearly be perceived as a computer. Even smartphones – the latest step in the evolution of computers – are rather clumsy to use, if you think about it.
Perhaps the most striking way to see the difference between regular computers and wearables is the user’s posture when using the computer. Using a computer results in a more or less non-natural posture or – even worse – behaviour (see Curious Rituals for a look in the mirror).
Wearables change this. By being attached to or located closely to your body, they allow you to take up a much more natural posture and eventually (in the more or less distant future), people around you will no longer notice them.
Granted, in their current incarnation, many wearables are still a long way from this vision and it is remains to the readers imagination how long you can wear a VR device like the Oculus Rift without getting a sore neck or becoming nauseous. However, this is only just the start and we will see great progress in the following years.
On March 18th, Google announced Android Wear and released the Android Wear Developer Preview. Shortly after that, Motorola announced their Moto 360 watch which generated quite some excitement on the internet. On the same day, LG announced their LG G watch – a rectangular model.
Android Wear is Google’s second platform for wearable devices (Google Glass being the first one). The theme for both platforms is to bring useful, contextual information to users when they need it. Ultimately, the goal is to empower users without distracting them.
If you’re excited about Android Wear as well, here are some ideas for you to try out.
First of all – watch the videos
- Introducing Android Wear Developer Preview with +DavidSingleton
- Android Wear Developer Preview with +JustinKoh
- Android Wear: receiving Voice Replies with +JustinKoh
If you’re a developer
Sign up for the Developer Preview. Head over to our developer site and sign up for the Developer Preview. When signing up, please make sure to use the same Gmail account you use on your Android device – this will make it much easier for you to download the Android Wear Preview beta app to your phone or tablet. As soon as you’ve been accepted to the preview, you will receive a confirmation email that outlines how to opt-in to the Android Wear Preview app beta program. You’ll need this app in order to connect your Android Wear simulator to your device.
Follow the instructions for setting up the Developer Preview on your developer machine as described in Getting Started with the Developer Preview. Here are a few things to make sure it all works out fine:
- use the same Gmail account for signing up that is connected to your test device
- make sure to use a device running Android 4.3 or better, as this is a prerequisite for the Preview app
- after installing and starting the Android Wear Preview on your Android device, make sure to tap the blue note on the preview app to register the app as a notification listener
The great thing about Android Wear is that your app’s notifications will show up on any connected Android Wear device (or emulator, for that matter) without any further effort. So, if you have an app that uses notifications to alert the user, you should be able to see those notifications on the Android Wear Emulator as soon as you have connected the Emulator to your Android device (phone or tablet) running your app. If you don’t have an app that uses notifications, you can quickly check this out by sending an email to the Gmail account cyou use on your device so the notification for the email pops up in the notification center.
Notifications are one of the two major design principles of Android Wear: Suggest and Demand.
Suggest: The Context Stream
All notifications will end up on the context stream, which is a vertical list of cards, much like Google Now on Android phones. The user can interact with the cards by swiping them vertically, thereby navigating the stream of important information. Due to the limited screen real estate, only one card will be displayed at a time. You can add cards to the context stream by creating and delivering notifications. Use NotificationCompat.Builder to create basic notifications (make sure to use the one in the Android Wear Preview SDK, otherwise some features will not work). To use Android Wear specific features like pages or actions, or to customize the look of cards on the context stream, use WearableNotifications.Builder. Here is a short snippet that shows how to create a notification:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Whenever you create notifications, be sure to follow the [Android Wear Design Principles](http://developer.android.com/wear/design/index.html. In particular, you should make sure all information you deliver follows the principle of being timely, relevant, and specific.
Demand: The Cue Card
Android Wear is not just about displaying notifications that the user can then interact with. In addition, users can initiate an interaction with their device by using the cue card. The cue card is brought up by saying “OK Google” or tapping on the “g” icon on the home stream of the device. Swiping up on the cue card will reveal a number of actions that can be executed by tapping them or speaking them. Voice actions are not yet available in the current preview SDK.
A word of caution
As the name implies, the Android Wear Developer Preview is not intended for creating production apps at this time. The APIs might change significantly prior to the official release of Android Wear. The preview is intended for development and testing purposes only. Also, we’re interested in your feedback, so make use of the Google+ community and Stack Overflow.
If you’re a designer
(or a developer who wants to understand the design ideas behind Android Wear)
Read the Android Wear Design Principles.
Become a member of the Android Wear Google+ Community to get in touch with fellow developers / designers and share your ideas.
A few people have created some great design resources for Android Wear. If you’re interested in creating some mock-ups, check out +TaylorLing’s Android Wear UI Design Kit for Photoshop. If you want to add some more glitz, head over to +SpiderflyStudios and download their Moto 360 mockups. Photoshop is not your thing? Check out Frank Erlich’s OmniGraffle stencil.
Please note that the current SDK focusses entirely on notifications. Refer to the Design Principles of Android Wear for a good overview of the Notifiaction UI Patterns available. Let this be your guide when using the design resources I linked. Not everything that’s possible in Photoshop might be possible with the current SDK.
…here is the link to the music used in the video: Chromeo – Jealous (I Ain’t With It)