Skip to main content

Android Wear 2.0 review: A massive upgrade for the wrist

Are smartwatches dead? Are smartwatches the future? Is my sock drawer full of smartwatches? Over the last year, we've seen a lot of hand wringing and hot takes about the future of wrist computers. It doesn't really matter who the manufacturer is or what operating system is running on it, you can find opposing opinions on the future of this tech category. For Google's part, smartwatches started out as an extension of a larger wearables strategy. Android Wear wasn't going to just be for watches, it was going to be on anything connected that you wore. Why, Google Glass may one day be considered part of Android Wear.

For Google's part, smartwatches started out as an extension of a larger wearables strategy.

Plans change, and Android Wear has since become an OS for many different manufacturers to explore what people want in a wrist computer. It turns out there isn't one answer. Some of us want a thin, svelte notification portal to occasionally glance at. Some of us want a standalone phone on our wrist with Android Pay, storage for music, and a full fitness tracking experience. Some of us want to leave our phones in the water-tight box and use our watch as a fish finder. The point is, it became clear there was never going to be a single hardware design and feature set for everyone, and while Android Wear had made this diversity clear over the last two years in terms hardware, the software hasn't kept up.

Welcome to Android Wear 2.0, an almost-modular watch operating system built to make it easier to build a unique software experience on top of the hardware of your choice. But does that make this the watch OS for everyone... or for no one?

Hungry for more?

Android Wear 2.0 is a complete overhaul of Google's wearable platform, but the hardware is just as important. Check out what LG and Google have done together with two new watches built specifically for Android Wear 2.0!

About this review

I'm writing this review after months of using Android Wear 2.0 in its Developer Preview form, with particular focus on the final build of the preview for two weeks. This review was written alongside the release of the LG Watch Sport and LG Watch Style, the first watches made with Google specifically for Wear 2.0.

Read more: These are the watches being updated to Android Wear 2.0

Android Wear 2.0

Assistant and Passwords and Play Store and More

Android Wear 2.0 Initial setup

In most situations, Android Wear is still very much a tethered platform. You connect it to your phone via Bluetooth, and through that connection the phone serves information to and receives instructions from the watch. In previous versions of Android Wear this relationship was always primary-secondary; the watch did nothing without information from the phone. Android Wear 2.0 changes this relationship quite a bit, turning the watch into a largely standalone platform that relies on the phone for a data connection to process instructions entirely on its own.

The initial pairing process for Android Wear hasn't changed much, but it is now step one in a much larger process. Your phone pairs to the watch, checks for software updates, and now asks you for your Google Account as though you were logging in to a new phone. You can move multiple accounts to the watch if you have more than one on your phone, allowing you to switch between work and personal if desired, and when the data is transferred you get a resting notification on your phone letting you know that a Google account was sent over. You know, just in case someone moved your account to a watch in order to steal your data.

Android Wear 2.0

Unlike previous versions of Android Wear, you're far from done. No app icons have been moved from your phone to the watch, because apps don't exist simply as secondary access terminals to the app on your phone anymore. Android Wear apps are separate from Android phone apps, installed and in many cases used independently of the phone. This is great for keeping your watch free of a long list of icons you may never use, but it also means Google's staple apps aren't yet on your watch. If you want Hangouts or Google Maps, for example, you need to install them from the Play Store on the watch, or from the web straight to your watch.

If you want Hangouts or Google Maps, you need to install them from the Play Store on the watch.

Activating the Play Store and installing apps is simple enough, but now you need to enable any other features you may want to use on your watch before you're fully set up. Want to use Google Assistant from your wrist? You need to enable the feature on the watch, then go back to your phone and confirm on your phone you want Google Assistant on your watch. Android Pay, if your watch supports it, has a similar setup. You can only enable it on the watch if you have a lock screen set up on your wrist — yeah, you read that right — and then you can confirm on your phone you want Android Pay.

Android Wear Pattern Lock

Android Wear security is just like Android security now. You can use pin unlock, password unlock, or pattern unlock. When this security measure is in place, you're asked to "unlock" your watch any time it leaves your wrist thanks to the heart rate monitor. Neither of these unlock mechanisms on your wrist is particularly convenient, but the pattern lock allows you to unlock your phone without using a keyboard on a 1.3-inch display. If you aren't using Android Pay, it's not a requirement to have the feature enabled.

The one great part about this setup process is the lack of prompts. After the setup tutorial to show you how to swipe notifications and choose watch faces, you don't have to to enable any of this. If all you want is a way to see notifications on your wrist and respond with your voice when you can, you never have to worry. If you do want these features, it means setting up an Android Wear 2.0 watch is considerably more complicated than it has been in the past. But it can also do much more.

Android Wear 2.0

Hope you like buttons and knobs

Android Wear 2.0 Interface

By the time you get to the end of setting up Android Wear 2.0, something about the user interface becomes abundantly clear — you're going to be doing a lot of scrolling. Previous iterations of Android Wear avoided interfaces that were more than a single swipe, unless it was an email or some other form of message. The interface itself was largely contained to single "cards", and that experience is now almost entirely gone.

Android Wear 2.0

Every app scrolls; the app launcher scrolls; and of course your messages still scroll. The amount of swiping in Android Wear is significant, unless of course your watch has a rotating button on the side to scroll as you turn. It's clear from this design change Google anticipates a lot of future watches to include Gear S3-style rotating bezels or LG Watch Sport and Style rotating side buttons.

In an attempt to prepare for the future of Android Wear, there's some weirdness in using a hardware scrolling mechanism right now. As far as the OS is concerned, this rotating piece of hardware can be programmed to do multiple things. In most menus it scrolls up and down. In Google Maps it zooms in and out. Developers have the freedom to make this piece of hardware do whatever they want, and because not every app has been updated to support Android Wear 2.0 sometimes the thing you can do with the rotating hardware is nothing at all. It's a little confusing to spin the crown on the LG Watch Sport and, in some apps, have nothing at all happen, but this is likely to be a temporary frustration.

Developers have the freedom to make the rotating piece of hardware do whatever they want.

Perhaps more important than directly encouraging users to turn a button on the side of the watch is how much more frequently you'll be pressing them. In the past, the button on the side of your Android Wear watch was used to return you to the watch face or back out of a menu. The interface was a single large cascading menu for you to interact with, but with Google Assistant replacing Google Now, and your App Drawer living behind a button press, the physical button on the watch is now the primary interaction mechanism, which is significant.

Android Wear 2.0

From the watch face, you can swipe down for quick settings, swipe up to see unread notifications, and swipe left and right to swap watch faces to whatever is stored on the watch. The button on the side accesses your app drawer, an alphabetical list of apps you have installed with the most recently used app at the top. Each app is standalone now, so you navigate to the app you want just like you would on your phone. If your Android Wear watch has multiple buttons on the body, these buttons can be programmed to launch specific apps so you're not stuck frequently swiping through the app drawer to get to them.

Notifications for Android Wear 2.0 are one of the best reflections of how Google's visual design has changed over the last two years. As a user, you are no longer sorting through a stack of digital cards as you triage notifications from your phone. Instead you have flat panels with muted colors and bright text filling the display. This new design increases information density, ensures the cards are easier to read in just about every environment, and there's some improved control over notification priority that has been desperately needed for a long time. Status notifications, like uploading something to Facebook, are sent to the bottom of the stack to disappear instead of placed on top to show you the thing you're already doing on your phone.

Overall, Android Wear 2.0 is a great deal simpler to navigate than its predecessors.

Quick Settings exists mostly to replace the features you lose on the watch button by moving the App Drawer and Google Assistant there. You can no longer double-click the button in order to activate Theater Mode, so instead you swipe down and tap on the sun in your Quick Settings. You can no longer triple-click to access the brightest mode the screen has to offer, so you swipe sown and tap the sun icon again. This section is a little more useful if you're able to turn cellular on and off on watches with LTE support, or if you regularly use the watch to control notifications in Do Not Disturb, but that's about it. It's a quick alternative, not really any better or worse than what was there before.

Overall, Android Wear 2.0 is a great deal simpler to navigate than its predecessors. You're unlikely to ever get lost in this interface, because everything is a direct action. If you're using apps, you press the button and go there. If you're checking notifications, they're always right in front of you. Gesture controls still work exactly the same as they always have, and the number of actions you take to complete most tasks is limited to one or two taps. This design can become as complicated as you choose depending on how many apps you use on a daily basis, but the overall design approaches simplicity from a new position and it works well.

LG Watch Sport

Okay, so we're doing this

Android Wear 2.0 Features

Visually, the face of Android Wear is going to appear very similar. Watch faces are available by the truckload in the Play Store, and that's not going to go away anytime soon. What you will start to see is an effort to make those watch faces a great deal more customizable, and useful, than we've seen in the past, thanks to Google's new Complications API.

This setup has been cribbed right from the Moto 360, and it's fantastic. Watch face creators can now designate areas on the face for users to plug in information from all over the watch. Any app that supports complications can feed data to the face, and users get to choose how that information fits. We're already seeing several watch face creators moving to implement this API in the Developer Preview, which means tons of new options for the already massive list of watch faces.

The biggest feature changes in Android Wear 2.0 fall into place when you go to use the watch as though your phone is just there to serve data. Some of this sounds downright silly when you say it out loud — replying to emoji by drawing on the screen, swiping on a teeny tiny virtual keyboard when voice alone is insufficient, or scrolling through the Play Store on your wrist in search of new apps.

Existing Android Wear owners may frown on these kinds of interactions, due to the size of the display and the kind of latency expected with these experience, and in some cases they'll probably be right. But Android Wear 2.0 does not exist for a single kind of user. If you're someone who has no interest in keyboards and emoji, there's never a situation where you're forced to use it. Everywhere you find handwriting and emoji writing, you'll also find voice and quick replies.

Android Wear features

The same can be said for Google Assistant. You can choose to have your watch always listening for the Assistant launch phrase, but it's frequently not as fast to launch as your phone or Google Home. Being able to say "OK Google" while your phone sits on the table or in the cupholder of your car is not the same as pressing and holding the button on your watch until the four colorful orbs show up, either. The important thing about Assistant being on your wrist is that it's there just in case. It's a way to fill the gap for some interactions, and for others it could very well become the default way to use the service.

Android Wear 2.0 does not exist for a single kind of user.

In the quest to create individual Googles for everyone, Assistant needs to be everywhere and work identically. The biggest challenge associated with Assistant on the wrist right now is lag. If Assistant isn't immediately available, like it is elsewhere, it's simply less useful on the wrist. It's likely this will be where we see older Android Wear watches running the 2.0 update appear less optimized.

Google's big shift in Android Wear with the 2.0 update is apps. Being able to install apps on your watch and have them run entirely independently of your phone is significant. People who almost never use Google Keep on their phone but love having lists on their wrists can accomplish this without cluttering up the primary app drawer. Fitness apps can be built specifically for Wear that require no phone at all. This is how Google creates the same Android Wear experience regardless of the phone platform you're using. If the app is on the Play Store, and the Play Store is on the wrist, it won't matter that you have an iPhone connected.

Android Wear Play Store

But there are things missing from this isolated experience that complicates Wear in ways that aren't entirely necessary. Play on Android Wear is slow, often taking anywhere from 3-5 seconds to fully load. The auto-update feature that is enabled by default doesn't tell you when an app has been updated or why, and choosing to do so manually is tedious. You also can't really tell from the watch how much data you're using in any meaningful way, which means you have to check with your phone.

This is by far the most complete feeling version of Android Wear to date.

An important part of any OS that doesn't get nearly as much attention as it deserved most of the time is the Accessibility section, and the biggest addition to Android Wear in this particular category is that it now actually has an Accessibility section. Magnification gestures allow you to triple tap on the screen and zoom in, text-to-speech and TalkBack modes use the speaker to read content to you, Select to Speak will call out menu options, and you can even set the power button to end a call.

These features combined make it clear Google is thinking about watches as more than just luxury items. This now becomes an emergency communication tool for the elderly, an assistive device for the blind, and a functional alternative to a large phone when that simply isn't an option for someone.

We know that Google is still working with developers to do more with Wear as 2.0 is adopted by more manufacturers as well. The ability to launch apps based on behavior — fitness apps launching when the watch detects a significant amount of movement — is something we'll see a lot more of in the coming year. In previous versions of Android Wear it felt like Google had created a lot of options and then waited for developers to wander in and create things for users. Android Wear 2.0 is a lot more focused on letting users build their own experience, which allows developers to help users adjust that experience as the need arises. It's a big shift, and it requires a little more work on behalf of the user than previous attempts at wearables, but this is by far the most complete feeling version of Android Wear to date as a result.

Android Wear

Go make it your own

Android Wear 2.0 Bottom line

So what is this new version of Android Wear, exactly? Is it an attempt to put a phone on your wrist? Could this be a way to sneak the Play Store onto the wrists of iPhone users? Is this an attempt to fight off stagnation by stuffing in every feature your relatively small user base demands? In a way, it's probably all of these things. But in the process, it's actually none of these things.

Android Wear 2.0 is the perfect encapsulation of "Be Together, Not the Same" in hardware form. Google was already ahead of the pack with personalization in the form of watch faces, and by enabling hardware manufacturers to offer more unique watches there's a lot of potential for this platform moving forward. No two people are going to have the exact same experience, but at the same time there's a consistency that can be appreciated by anyone interested in having a computer on their wrist that also tells time.

Russell is a Contributing Editor at Android Central. He's a former server admin who has been using Android since the HTC G1, and quite literally wrote the book on Android tablets. You can usually find him chasing the next tech trend, much to the pain of his wallet. Find him on Facebook and Twitter

51 Comments
  • It's almost like Google just needs to let Samsung make all their interfaces and features. Looks much cleaner. Guess I'll need to update my Huawei watch to play with it. Don't think it's enough to even make me rethink my Gear S3.
  • Is this released to the Huawei watch yet?
  • I doubt it. I'm sure there will be a delay or will have to sideload it to get it earlier.
  • The Developer Preview is available now, but the full update hasn't shipped yet.
  • Somewhere I read that updates for non Google watches will be after February 15th.
  • I'm not going to rethink my Gear S2 I just got, but damn it would be nice to have a watch that can control a lot of the apps in the PlayStore. Guess I'll be getting the LG Sport too.
  • Apps like what for a watch?
  • Can't wait for AW 2.0 for my Huawei!
  • Bottom line. throw away any previous android watch and start over from this point.
  • Do people throw away their other tech when new OS versions appear? Seems a tad wasteful.
  • have you ever used an apple product?
  • Yes. Why do you ask? I have no clue what using an Apple product has to do with discarding an older Android Wear device. Here are Android watches that will update...
    Huawei Watch
    Huawei Watch for ladies
    Moto 360 (2015)
    Moto 360 Sport
    Moto 360 for Women
    LG Watch Urbane 2nd Edition LTE
    LG Watch Urbane
    LG G Watch R
    Polar M600
    Casio Smart Outdoor Watch
    Casio PRO TREK Smart
    Nixon Mission
    Tag Heuer Connected
    Asus ZenWatch 2
    Asus ZenWatch 3
    Fossil Q Wander
    Fossil Q Marshal
    Fossil Q Founder
    Michael Kors Access Bradshaw Smartwatch
    Michael Kors Access Dylan Smartwatch
    New Balance RunIQ And the others do not become non-functional when an update is released which makes throwing them away silly.
  • Is the Moto 360 (15) getting the update I thought they said it was not?
  • I think the 15 is the 2nd generation one? the original Moto 360 isn't getting the update
  • When this would happen??????
  • Or just upgrade for the watches that can upgrade...
  • Asus is usually slow for updates I doubt I will get the update anytime soon I have the ZenWatch 2
  • Google controls the updates for all Android Wear watches, so it should roll out pretty quickly to all eligible watches.
  • Especially if the release is in alphabetical order. :D
  • Hmm...are you going by ASUS or ZenWatch? :-)
  • How do these devices work for people who are lefty (or basically those who put the watch on their right hand). Is it easy to flip the display around for easier access to the buttons?
  • That actually would be a great idea and should be implemented
  • I thought that was an option when I first set up my Huawei, but now that I look back at all the times I've reset it and upgraded to the Dev Preview, I don't think it can be flipped... Did a little Googling before clicking "Comment" and found this: https://www.androidcentral.com/e?link=https2F2F... There's a mirror for installing on Android Wear (if you can't install it through the store): https://docs.google.com/uc?export=download&id=0B7ODz45fOUKVaXJwLU05cHA2eFk Source: http://www.corbin.io/2014/10/hacking-android-wear-part-two.html
  • I'm left handed and I have never had an issue with having it on my right hand. It's just like any other watch and the buttons face away from my wrist instead of towards it like I see in a lot of right hand reviews
  • 2nd that. If there is such a mode, I haven't found it yet. AW2 does not seem to have an left handed mode with the buttons facing towards your fingers. Lefties will have the buttons facing their elbows. The watch display automatically rotates 90 degrees, but will not do 180 deg rotation.
  • When will AW 2.0 be released for the LG Urbane 2nd Edition?
  • I want to know as well. I would like to get this wait over with and see just how badly they messed it up for me.
  • Sony smartwatch 3 should be updated .... Really lame that it won't be
  • I wish some of the newer watches included NFC (Nixon and Casio, for example). They weren't released that long ago so you'd think they would have used a little foresight in their hardware design.
  • But can it play Crysis?
  • Haha I was actually thinking recently, I haven't seen anyone say this in a long time. Used to be said on every product review back in the day as I'm sure you know.
  • I hope I didn't miss this in the review... Where can I get that "portion" watch face?
  • Really wish the Gear S3 had android wear just for the play store. Unfortunately, Samsung pay support trumps android wear in favor of Tizen for me.
  • Can't wait for this on my ZenWatch 2
  • I can't wait either... checking every 8 hrs. or so... for Asus Zen2
  • Same. Been checking on my zen 3 as well.
  • Agreed! :)
  • Looks interesting, but why get Android wear over what Samsung is doing with Tizen and the Gear S2/S3? Maybe I'm just a Samsung fan boy but I see little reason to buy any other watch. I don't know about others on this site, but I'd like to see a good comparison article between the two. I know plenty of reviews are available for each, but I want to see a comparison done by a good author, which is something Android Central could provide.
  • OK - so I have had three Samsung wearables (the Neo, the S2, the S2 Classic - each for several months and now have the LG Urbane 2.0. So here goes - The Neo did not have any LTE support - and it is a couple generations back so I'm not going to mention it, other than to say it was a good entry point into wearables. It did sync with the phone in bluetooth and did the basics... Comparison will be with the S2 Classic and the LG Urbane 2.0 Connectivity
    Both the S2 and S2 Classic were LTE enabled and had their own SIM and phone number so they could work for calling even when the phone was left behind. Great concept right - execution was another thing. In fact both watches suffered greatly and were virtually un-usable as standalone. After a couple of minutes of talking on the Samsung wearables when using their own SIM - they would shutdown with a message they were overheating. Thinking the watch was defective AT&T sent out another. It did the same thing. When then they sent me an S2 - I thought bigger footprint perhaps a bit more heat dissipation. It did the same thing. When paired to the phone they worked find. I believe the issue the CPU they used overheating as the battery drew more current to run the cellular communication for the SIM. Awful, awful, awful. Got AT&T to replace it with the LG - no issues at all. I've held 45 minutes+ calls on it with no problems. Perhaps the issue is fixed with the S3 - maybe a new CPU - but I'd certainly check it out if you plan to use independent of your phone... As for signal strength - I think the LG does a bit better given that its antenna is in the band but none of these pull in signal from a tower like your cell phone. So the winner for LTE - is hands down LG Connectivity via Bluetooth was comparable on all three watches no real noticeable issues I can point to, although I do recall a few instances the Samsung's occasionally dropping connectivity but not to the point of being a big deal. I also the syncing with the phone on the LG is a bit more consistent. Emails / Messages seem to always come in where for some reason they'd frequently not appear on the Samsung. The reason why I will go with Android as a clear winner here is that Google voice command worked SOoooooo much better than S-Voice on the wearable. S-Voice was just not accurate. Maybe it is the mic or the inability to have the processing power to interpret - but it was really unusable in many occasions and totally unusable when I was remote from the phone. Winner again is Android Wear (hard to believe that I was a decade long Samsung guy too so no bias to android in fact after my Note 5 was damaged I went to an LG - and have to tell ---- I really like it (aghhh sorry Samsung) - hopefully I'll never go to an iPhone... Apps
    The Tizen did have a fair number of apps that were available - but certainly not as robust of a library at the time (probably May, 2016) as what is now available on Android Wear. Maybe they have more. Given that I'd favor the LG Android as being a bit better. If you are a Samsung fan then there are nice apps that work well on your Samsung and the Wearable - but beyond that - Android wins. App Performance
    Other than the Samsung Apps and a few of the others like eBay - the third-party Tizen apps didn't seem to be as intuitive / professional as those I find on the Android. Maybe it is the level of coders working with Tizen or limitations of the capabilities of OS - but they just tended to feel like first generation and these were apps that people tended to recommend (Flashlight, remote Camera control, News feeds, etc.). Despite being a decade long Samsung mobile person - once again after using the LG android - I'd have to give it the nod on app choices and look / feel of the programs. I do think the heart monitor worked better on the S2 Classic vs. the LG... General OS navigation
    Both the Tizen and the Android Wear do take some getting used each had nice features. The S2 Classic with the rotating dial was certainly missed and helped navigate a bit better than the LG. Based upon that hardware advantage that the Tizen took advantage of - I'd probably go with the Tizen over the Android Wear on ease of navigation. Appearance
    Since with Tizen you are limited to Samsung's line - I have to also judge on appearance. The Neo and S2 looked very much like wearables and were not really a good looking watch. The S2 Classic was really nice and I had compliments - the LG Urbane 2 is even more like a traditional watch. I'm 5'8" decent build and it fits great on my wrist. Many compliments on it - even from the guys at the AT&T store despite them not really pushing the brand much. Winner for me is the LG although I can't comment on the S3 although I'm told it is really big. Overall Thoughts
    As hard as it is to say since I really wanted to stick with Samsung - for me there really is no choice. Android Wear just seemed to be an overall better OS across the board than Tizen with exception of navigation. I would also say that given Android Wear 2.0's new release and the benefits it purportedly offers (new interface, standalone running of apps, etc.) - which I will post on once it is installed - I just don't see why anyone would prefer a Samsung wearable. Maybe if you really like Samsung S Health or some other Samsung apps like Pay (which I didn't use) I guess. I would suggest keeping your Samsung and maybe doing a 15 day trial with an LG or another Android from your provider once Wear 2.0 is widely available. It is really for them to get your watch back on after a temporary switch since it doesn't have it's own SIM. You don't need to install the full suite of apps on the test watch just the basics. Would be interested in getting your thoughts as a Samsung Fan boy as well to see if you make the leap.
  • I will 2nd your assessment. I was given a free Samsung fit 2 when I got the note 7. I used it for several months. Then I bought a Huawei watch. The hardware of the for 2 is great, but the software is limited to Samsung. For example, you can't keep fitness data anywhere except Samsung. There is no way to export it to anything else. If I ever choose to use another phone, all my data is gone. With the Huawei watch, it syncs with Google for and may other apps. Some of which will export data.
    Now my fit 2 lives on a shelf and my Huawei lives on my wrist.
  • I have the S2 on T-Mobile. Never had it overheat on calls with or without a headset.... I don't have a ton on it though. Also, the S2 doesn't run on LTE, it uses 3G.... Do you even smartwatch?
  • Been playing with last dev preview on my huaweis for a while now and so far I like 2.0 very much. New dark theme, design changes, complications and especially the new play store with "standalone" apps so i can finally look install indepently from my phone. Not too many apps there yet (i like new runtastic, ezride, of course many apps from google...), but hopefully we'll get there soon
  • Can't ever see owning one of these things. I don't know a single person who owns one either.
  • I was going to comment something similar. I don't have any interest in it.
  • Clearly there are those of us who do, and see many people everyday that do. Best to crawl back under your rock and move on from this here post gentleman.
  • So, they finally caught up with Tizen?
  • When do you think Tizen will catch up with Android's developer base?
  • Samsung is so fickle, they cant even go all in on Tizen. Nothing they do OS wise makes any damn sense in the grand scheme of things, then again, ive witnessed this for so many years bqck when i worked in the industry.
  • I'm excited about this. Going to give it a good try on my LG Watch Urbane when it is released, which I hope is very soon.
  • Can't believe all the articles on AW 2.0 the past week, but nothing on when exactly it's coming to existing watches. I guess there really are only a few of us.
  • I thought aw2.0 was being released for all supported watches around the same time. However I see no mention of any old watches getting an update. Only the new lg?