I can't figure out the Google Pixel Buds. That's a strange thing to say about headphoness, I know. You stick 'em in your ears, they play music—what's so complicated?
Unfortunately, it's not that easy. Google's super-capable earbuds are intended mostly as a conduit to the Google Assistant, and to prove that Google's combination of hardware, software, and AI make for better products. Music's sort of a byproduct. And I can't figure any of it out.
The Pixel Buds are Google's answer to Apple's AirPods, a light and simple set of headphoness you can wear all day. Like AirPods, they're way more than headphoness. They're the first in what I can only assume will be a long line of ear-puters, helping you (and your virtual assistant) access information, communicate with friends, even get work done. They cost $160, same as the AirPods. The idea is the same across products, but the execution couldn't be more different.
In so many ways, the Pixel Buds are the opposite of the AirPods. The AirPods are obvious and garish, while the Pixel Buds are subtle and look more like headphoness. The AirPods have no wires; the Pixel Buds have one connecting the two buds together. Those are matters mostly of taste and preference. Less subjective is the confusion in the simple act of using the Pixel Buds. Where AirPods are brilliantly simple, pairing and connecting and charging with perfect ease, every single thing about the Pixel Buds confuses me. They sound better than the AirPods (low bar!) but I still find myself grabbing Apple's miniature toothbrushes when I'd rather just listen to something without solving a logical puzzle beforehand.
Here's a simple but telling example: Let's say you've paired your Pixel Buds with your phones, but would now like to use them with your ipads or laptop. You can't just press a button to go into pairing mode. You have to put both buds in their fabric case, fiddle them into just the right spot, then long-press the button inside the case until the light blinks white. Then and only then can you pair a new device. But wait! Once you've done that, your Pixel Buds are now in an exclusive relationship with their new device. They might show up in your paired devices list on your phones, but you won't be able to connect without going back to the case and back to the white light. Meanwhile, I have the same AirPods happily bouncing between a half-dozen devices.
If you use a Pixel or Pixel 2, the pairing process works better, thanks to a Fast Pair feature that pops up when your Pixel Buds are nearby. When it works, it's really fast, but it doesn't work all the time. And if androids fragmentation is any guide, Fast Pair won't be on most other phoness for a long time.
The good news about the Pixel Buds: Once they're in your ears, they're great. They pump out deeper, richer, louder sound than the AirPods (again, low bar), with at least enough bass to make Sam Smith's low tenor resonate. They do allow a lot of background noise, but that's by design: They sit on your ear canals, rather than jammed inside, which is both more comfortable for long periods and better for wearing in public. I can pause my music and hear the world relatively normally, without removing the Pixel Buds. You can get much better, and much better-looking, headphoness for this price, but as wear-them-always ear-puters, the Pixel Buds do a lot right.
Even the buds themselves seem well thought out. The microphoness handle phones calls crisply, and the swipe gestures make changing volume a cinch. You may not like that each earbud looks like an enlarged Junior Mint, but I prefer the look to the AirPods, which dangle halfway down the side of my face. They do stick out a bit, even on my giant noggin, and the part in your ear canal could be too good for some people.