Wear OS Is Upsetting, and I’m Gonna Rant About It

I’ve personally been maintaining a policy that generally dumber tech is better. I don’t own any smart speakers, I don’t own any smart lightbulbs because I’m terrified of the prospect of having a web server in a light-socket, and I definitely don’t own any smart cameras or the such for similar reasons. I’m not opposed to such things existing, I just think they’ve got a long way to go before I’d trust them.

I did however somewhat break this trend with an impulsive purchase of the Huawei Watch 2, which at the time was one of the best (technically speaking) Wear OS smartwatches on the market. I thought “Hey, it’s a Google product, how bad can it be?!”. As I’d learn over the course of owning the damn thing, quite bad.

The first thing I noticed about the watch was just how poor the performance was. Considering the fact that the processor inside of it is roughly equivalent to a Nexus 4, the performance was appalling. Even just swiping through the various menus caused frame drops and stuttering. Still, I powered through, and attempted using the watch for what I thought it would be useful for; music.

One install of Google Play Music later, and I begin to wonder why I’d bothered. The app takes around 20-30 seconds to launch fully (I swear I’m not making this up!) and you’re booted into a very spartan interface that can charitably be described as functional. Then, once I hit play on a particular song, another 10-15 second pause, and…what’s this?! The music is coming out of my watch! I’ve got a set of headphones connected to my phone, yet the watch decides the best thing to do is blast said music out of its own speaker! What use case does this serve? I’ve never seen a single person listening to music literally through their watch, so why is this the default?!

I later learned the intention is to pair your Bluetooth headset up to the watch, so that it can play independent of the phone. My question is why would I want to do that? I’ve got 3000+ MAh in whatever smartphone I’m carrying, why not use some of that battery power instead?!

I later learned that in order to control the music on your phone, you first have to take the phone out, start playing music, and then you’re presented with some incredibly basic back/forward/play/pause type controls in a notification on the watch. None of the nice navigation through playlists or stations. Wonderful.

Even more hilariously broken is the Google Assistant. One day, I was working out in a gym and I decided that the music coming out of my headphones could do with being a little louder. I hold the Google Assistant button on the watch, and around 5 seconds later it chugs into life. I ask it to turn the volume up. What does it do? Google “turn the volume up”. Another time, I’m going to bed and I want to be woken up in the morning, so I hold the Assistant button, wait the customary 5 seconds for it to finish mining Bitcoin or whatever the watch is doing other than responding to my request for Assistance(tm). After the Assistant finally wakes up, I ask it to set an alarm for whatever-O’clock I wanted it set for. Wonderful, it set an alarm! I felt assisted. I then take the watch off, stick it on its charger and go to sleep (a necessary process, seeing as it lasts roughly a day, maybe 2). Unsurprisingly, the assistant played a trick on me again, I slept through the alarm, which was coming through the watch, which was away on its charger, rather than the phone, which I kept beside my bed, fully expecting the alarm to come from there.

Another fun aspect of Wear OS is the app development ecosystem. It’s Android! This sounds great if you’ve ever messed about with Android development in the past, and in some ways this is nice, but frankly it feels incredibly bloated and wasteful considering the majority of the apps on the watch are garbage anyway.

The common theme with all of these problems is this insistence on the watch being independent from the phone, and I just don’t understand it. Surely, it would be better to treat the watch as an alternative method of interacting with the phone, where it makes sense for this to be the case? Why, when I ask the Google Assistant a question, does it deal with the query itself? Why not forward it to the Google Assistant that is running on the phone itself? There’s only so many times you can ask the assistant how tall the Eiffel Tower is. Why, when I have headphones plugged into my phone, does the watch assume the best audio output available for music is the watches speaker?

It’s not all terrible though. The Citymapper app for Wear OS was a glimmer of hope. In the morning, my phone pops up telling me that it’s calculated my route to work for that day. I tap the notification, and immediately my watch vibrates and starts displaying the route information. It sounds ridiculous, but that kind of interaction is extremely rare.

Comparing and contrasting the Citymapper app to the Google Maps app, it’s almost comical. Remember that these devices have screens that aren’t much larger than a two pence piece. Opening the Citymapper app (which launches pretty much immediately) on the Android Wear device offers you two options, “Get me to work” and “Get me home”. Anything more than that, you’re going to need to pull your phone out. Open Google Maps however and you’ll be waiting approximately 7-8 seconds for it to literally load a street level map onto your wrist. Dragging the map around stutters and skips frames. Can you get directions to your home or work through this App? Of course you can’t! You can, however, search for places nearby, and get navigation directions to those places, if they’re in the list of Google approved(tm) places. Why, in Gods name, would anyone want to look at a two pence piece sized version of the world? If I wanted to see a map, I’d have looked at my phone!

I think that Wear OS would be so much better off if instead of working to put a phone on your wrist, it was instead designed to be auxiliary to the ridiculously powerful slab of glass you already almost certainly have in your pocket. While I don’t regret the purchase, and to Googles credit things do seem to be very slowly improving, I certainly won’t be buying another Wear OS device. Companies like Xiaomi are releasing devices like the Amazfit, which while nowhere near as versatile as Wear OS, give me the main things I care about: Seeing and responding to notifications, tracking fitness/sleep, controlling music, and telling the damn time. It also has a month of battery life, and isn’t trying to do literally everything the phone in my pocket does better than it.

Update: I eventually sold the damn thing and have been much happier since.

Let me know what you thought! Hit me up on Mastodon at @kn100@fosstodon.org.