When it comes to smartwatches, Dick Tracy set a difficult standard.
Over the past few years, companies large and small have been struggling to convince us we need computers on our wrists. And let's not beat around the bush: Their efforts have all been pretty underwhelming.
From the Pebble to the Galaxy Gear (and all of their subsequent variations), no single smartwatch has managed to crack the code -- to establish a compelling use for the technology that's also stylish and simple to operate.
Now it's Google's turn to step up and take a swing. With its new Android Wear platform, Google is hoping to do for smartwatches what it's already done for smartphones: Create a massive and expandable platform that'll attract hordes of manufacturers, developers and, ultimately, consumers.
So what's Wear actually like to use in the real world -- and could it succeed where so many other efforts have failed? I've been living with the platform for the past two weeks to find out.
(Note: This review will focus specifically on the software side of the Wear experience. For a detailed look at the first Wear devices, click over to my separate Samsung Gear Live vs. LG G Watch: A real-world evaluation review.)
Getting to know Android Wear
When you walk around a city talking into your watch, you're bound to get a few quizzical glares. In that regard, wearing Android Wear makes you feel a bit futuristic and ahead of the curve -- kind of like living out a James Bond fantasy (minus all the explosions and scantily clad co-stars).
The best way to describe a Wear watch, I think, is as a device that makes it easier to keep up with the information you need. And thanks to all the data Google has collected about you and your world, Wear is in a unique position to provide that service.
Case in point: The heart and soul of Android Wear is Google Now, the intelligent virtual assistant Google has woven into Android and Chrome over the past couple of years. Google Now uses a combination of search data from your Google account, location data from your mobile device and cues from things like your Gmail messages to compile bite-sized tidbits of info -- known as "cards" -- that appear contextually throughout your day.
You might get a card in the morning alerting you to traffic on your route to work, for instance, or a card with directions to a business you searched for earlier in the day. Some cards are as simple as the number of steps you've taken so far that day or the weather for your area -- or for an area you'll be traveling to in the near future. Others are more surprising, like a card that might appear on a Friday evening with the current drive time to a bar or restaurant you tend to frequent on that day of the week.
An Android Wear watch face followed by some cards you might see.
What makes the info special is the fact that it shows up when you need it -- before you even think to ask. And while that same sort of info is available with a few swipes on an Android phone, having it on your wrist really does change the way you experience it.
This is because Wear puts contextual info front and center -- and consequently makes it feel like a natural extension of your body as opposed to an out-of-the-way interruption. Add at-a-glance access to notification-based cards like text messages and emails, and you've got a pretty compelling framework for a wearable-tech platform.
To be clear: Wear is very much meant to serve as a complement to your phone -- not a replacement for it. Wear watches connect to Android phones via Bluetooth; the phone runs a special Android Wear app that allows it to stay in contact and transmit data as needed. Without an active connection, the watch maintains its most basic functionality -- it keeps time, as you'd expect, and allows you to use a few non-data-dependent features -- but compared to its connected state, it's fairly limited in what it can do.
And on that note, be warned: You'll need Android 4.3 or higher on your phone in order for it to work with Wear.
Getting around Android Wear
An important thing to know about Wear is that, unlike the regular version of Android (which phone and tablet manufacturers are notorious for "skinning"), the software is almost identical on any device you use. Google is maintaining tight control of the core user interface to create a consistent experience (and thus also a more streamlined upgrade process) across the platform.
When you glance at any Wear watch, the first thing you see is a face design of your choice along with a peek at your top-ranking card for that particular moment. Wear constantly evaluates your cards and attempts to rank them in order of relevance based on where you are and what you're doing. The system isn't always spot-on -- I sometimes saw my footstep count as the top card instead of my flight status while I was in an airport, for instance -- but it does get the order right fairly often.
By default, Wear devices live in a dimmed mode most of the time, which means the screen is in a simplified black-and-white state. You can activate the watch and cause its display to become fully illuminated either by tapping the screen or raising your arm upward (an action made possible by an accelerometer that's standard in Wear watches). Pressing your palm over the display, meanwhile, causes it to go back to sleep.
Want to know how well the smartwatches work?
For a thorough, deep-dive examination of the LG G Watch and the Samsung Gear Live, check out our review Samsung Gear Live vs. LG G Watch: A real-world evaluation.
Once your watch is illuminated, getting around Android Wear is all about swiping. You swipe up once on the screen to get a full view of your first card; you swipe up again to move downward to the next card in your stack. Almost everything you do with Wear revolves around those basic gestures. It's a delightfully easy system to learn and use -- the exact kind of dead-simple interaction that makes sense for a wrist-sized screen -- and it's sprinkled with tasteful graphics and smooth animations that make for a polished overall experience.
In addition to the up-and-down swipe, you can swipe sideways toward the right on any card to dismiss it or sideways toward the left to get additional info and options. On a weather card, for example, swiping left brings up an extended multiday forecast. On a text message, swiping left once shows you a scrollable view of the full conversation thread; swiping left a second time presents you with a large icon to respond to the message by voice.
The anatomy of Android Wear cards
What's particularly interesting about commands on Android Wear cards is that, for the most part, they're already built into regular Android applications -- which means any notification that works on your phone will automatically work on your watch. Wear just takes the same action buttons you'd see on a phone-based notification and translates them into the watch's card-based interface.
At top: A Gmail notification on an Android phone. At bottom: The same notification as it appears in swipe-able cards on a Wear watch.
A good example of this is Gmail. When you get a new message alert on your phone, the Gmail notification there has two buttons with commands to archive or reply. On an Android Wear watch, those same buttons appear when you swipe to the left as large icons on a new mail card. No special watch-specific support is required for the app to be compatible; everything just works automatically out of the box.
That being said, there are things developers can do to make their notifications more smartwatch-friendly -- and the vast majority of apps aren't yet fully optimized for the form. If you tap the icon to respond to a tweet from Twitter on your watch, for instance, a reply window will open up on your phone instead of as a prompt on the watch itself. Evidently, developers have to manually enable support for watch-based text input before it'll work, and Twitter -- like many other app developers -- has yet to take that step.
Twitter's notifications, like those on some other apps, can also become cluttered and unmanageable on a watch's small screen. A notification from Twitter with a single piece of information works fine. But when a notification from Twitter contains multiple pieces of info -- more than one mention or a combination or mentions and direct messages -- all of the text ends up getting squished into a single card instead of being spaced out properly. As a result, it becomes impossible to read on the watch's display.
Other apps' notifications are even more confounding. Google's own Google+ app, for example, will show you that someone has commented on your post or left you a message -- but it won't let you view the actual comment or message from your watch. That's because the corresponding phone-based notification for that app shows the same limited amount of detail, and Google (rather ironically) has yet to optimize it to work more sensibly on the smartwatch form.
From left: A Twitter notification with a single piece of information; a Twitter notification with multiple pieces of information; a Google+ notification.
Beyond the basic notifications, Wear gives you the ability to control audio playback on your phone via your watch -- stopping or starting play, skipping tracks and so forth. Controls show up on the watch as a card any time audio is being played from an applicable app on the phone. They're also available when content is being streamed from the phone to any Chromecast dongle.
From left: A Google Play Music control card; two specific functions that appear when you swipe left on the Play Music card; a playback control card for Netflix content being streamed via Chromecast.
When you get a phone call, meanwhile, Wear shows you who's calling and allows you to swipe left or right on the watch to accept or reject the call. If you accept the call, it'll pick up on your phone. (By default, the phone will ring in addition to the watch vibrating, but there's a setting with which you can opt to silence the phone and receive all alerts on the watch only if you prefer (which actually makes more sense to me).
You can't actually conduct a call on the watch itself -- which, let's be honest, is just as well; it's refreshing to see a company opting to leave out the gimmicky stuff and deliver a device with purposeful focus.
Notifications on Wear are completely synced with all of your other Google devices, by the way, so if you dismiss a notification on your watch, it'll automatically disappear from your phone, computer browser and any other places where you're signed in.
When it comes to issuing commands and inputting text, Android Wear relies almost exclusively on your voice -- no microscopic on-screen keyboards or other such silliness. And by and large, Wear's voice input system works surprisingly well.
You can wake a Wear watch and start giving it commands by activating the screen and then either tapping the display or simply saying "Okay, Google." From there, you can speak a variety of commands for tasks like taking a note, setting a reminder, checking your agenda or sending a text or email (which you would then dictate by voice).
Again, that's all stuff you could do on an Android phone as well. But when you're walking around or in a moving vehicle, being able to quickly send a text or set a reminder by raising your arm and saying a few words into your wrist is insanely useful. I've gotten spoiled by telling my watch to remind me of things when I get home (yes, Wear can do that) or by sending quick texts by speaking into my wrist on the fly. There's no fumbling through your pockets or fussing with your lock screen; the process just feels natural and intuitive.
Basic commands aside, you can ask Wear for all sorts of information and the system will provide the answers on your watch's screen. You can ask about sports scores, calculations and conversions, or even general facts -- who's the mayor of a certain city, how many calories are in a particular food, how old is a certain celebrity and so forth. If Google has the data in its ever-expanding Knowledge Graph, it'll present it to you in a clean and concise card; if not, it'll give you the top few Web results with the option to read more via your phone.
Good as it's become, of course, Google's voice-to-text technology still isn't flawless -- so you do have to accept the fact that your Wear-based dictation will have the occasional misinterpreted word. I've also had some scattered instances where the system has returned an odd "Disconnected" error after I've attempted to set a reminder or send a message, but that seems to be more of an occasional glitch than any sort of regular occurrence.
Android Wear and apps
The core operating system and Google services may be the real stars of Android Wear, but apps play a critical supporting role on the platform. Like Wear itself, apps are generally designed to work as extensions of their smartphone counterparts, making it easier for you to accomplish certain tasks that make sense on the wrist.
Notably, Google isn't going to create a standalone store of apps for Wear devices; in fact, you'll never install an app directly to a Wear watch. Instead, certain Android apps offer watch-specific components -- and when you install any of those apps onto your phone, the watch elements automatically appear on your Wear device.