Casting Google’s Speakers Aside

Posted on

See what I did there?

As mentioned recently, I have switched over to Apple Music from Spotify. Part of the decision was based on personal preferences around the 2 services, but the reason that I was reluctant to drop Spotify in the first place was the lock-in I had with Google’s Chromecast ecosystem. As it turns out, by looking to invest in nicer speakers I ended up switching services and voice assistants along the way. I thought it’d be worth discussion as to why I decided to move to Sonos from the Chromecast setup we had, and some of the pros and cons I’ve noticed in the past few months.

Google stops playing (and sounding) nice

Something funny happened in the past year or so. Google, long known as the ‘open’ ecosystem, became a bit less so. With continued integration between the Nest and Google lines, it’s becoming less open and more of an ecosystem play with Google’s products. That’s fine, but it’s not why I initially bought Chromecasts, Google (now Nest) Hubs, etc. I was hopeful they’d give me the best shot of buying nearly any smart home product and they’d work.

Combine that with an increasing discomfort with Google’s data collection across more and more areas and mediocre sound quality on the Google Homes (and especially the Nest Hub & Home Minis), and I was interested in checking out a different approach to whole-home audio.

A few months ago I had posted an article about Google slowly locking down their smart assistant ecosystem and how I felt like it was time to explore a change. My home setup was a few Google Home & Minis, 2 Chromecast Audios plugged into existing speaker setups on our deck and patio areas, and a Google Nest Hub in our kitchen. We used Spotify for the most part, but I missed the feeling I used to have when using iTunes / Apple Music in years prior. Specifically, I’ve always been more interested in albums and Spotify is very playlist and “mood” centric. I think there’s a time an place for that but in general I was questioning the value of paying for Spotify despite its strengths compared to Apple Music.

Outside of the Google Home stuff, most of our “smart home” stuff is pretty platform agnostic:

  • 2 Nest thermostats
  • A bunch of Wemo and iHome smart plug
  • MyQ garage door
  • A Roomba
  • A HomePod (obviously the biggest outlier)

I’ve mostly relied on using Homebridge via a Raspberry Pi to stitch everything together so that we can use HomeKit scenes to automate most of our scenes (morning, evening, leaving & arriving home). We don’t really automate a ton, but I like being able to make sure the garage is closed if we’re both not home for a certain period of time, the lights are off if we’re away, or they come on if we are home and it’s almost sunset. Overall, pretty basic stuff – I’ve grown kind of sour on most of the stuff “smart” home devices offer these days so we’ve kept things pretty simple at our new house.

If we were going to ditch the Google Homes, we needed something to replace them with something that provided great sound, integrated with whatever music service we wanted, and worked in multiple rooms. Enter Sonos.

Why did I choose Sonos?

I’d been thinking about getting Sonos speakers for years now, as I wanted to get something that was service and platform agnostic. Sonos nails that – they integrate with all of the major streaming services, podcast services, audiobook vendors and even offer multiple options for voice assistants (Google Assistant and Alexa). Throw in Airplay 2 support and it was a no-brainer to upgrade most of our Google Home devices with Sonos Ones. One of my favorite things about the Sonos ecosystem is that you can control the speakers via their app or most services’ default apps (Apple Music is an exception, no huge surprise there).

There was a catch with our house – we have outdoor speakers that wouldn’t be easy to hook up to a Sonos speaker. To get our deck wired up, we replaced the Chromecast Audios we were using with 2 Airport Express units that I bought off of eBay. They’re AirPlay 2 compatible, so I was able to plug them straight into the amps for the 2 outdoor speakers we have and we had an Airplay 2 optimized home. Instead of spending hundreds for a Sonos amp, I was able to get something “good enough” for around $45.

Comparing AirPlay 2 to Casting

Previously, we had an entire setup that was all Google Cast powered, so we could ask any speaker to play music and it’d start playing Spotify wherever we wanted. With Sonos speakers, we introduced some small trade offs for the additional flexibility and sound quality. Some of the key differences between Airplay 2 and Casting:

  • Casting isn’t tied to your device at all. Airplay 2 still relies on a source to stream to each audio source, so that means if you were to stray too far away from your WiFi while controlling music it’d stop playing eventually. That’s not the case with Sonos, only Airplay 2 based streams.
  • Native iOS integration of Airplay 2 means that management of whole-home audio is much easier than it was from Spotify or the Google Home app (from control center or the Apple Watch now playing screen you can control any speaker that’s playing music)
  • Google Cast allows you to create named groups to send music to, while Airplay 2 uses your house layout to dictate grouping. Invoking an entire floor is pretty easy on both platforms but if I want to only call on a subset of speakers I could name that subset with Cast, where on Airplay I’d need to ask for each room when invoking that subset. Hoping I can eventually use HomePod shortcuts integration to fix this.
  • I use apps to invoke music way more than by voice now. This is actually a good thing because previously I’d typically ask for the same few playlists over and over. It’s similar to how I panic and order the same meal every time at a restaurant when pressed. Now, I find myself queueing up different albums and playlists all the time.

Add a dash of HomePod

Airplay 2 stuff won’t work with the Sonos system so I have to control them with my phone or iPad if I want to play music everywhere, but this really isn’t a big deal. If we ever want to go 100% into the Sonos world, we can always get something like the Sonos Amp, but I can’t really imagine that happening, to be honest. The only time we really need whole-home audio are if we’re having some sort of group gathering and want to play music everywhere. For now, if I want to play anything on our Sonos setup, outdoor speakers and my office don’t fit into the picture. But as previously mentioned, Sonos speakers are all Airplay 2 compatible, so if I want to play a song everywhere I just have to invoke the music from my phone, iPad or Mac.

Or a HomePod.

Another purchase I made about a year ago was a HomePod. They were on sale at Best Buy, so I picked on up, figuring I’d either return it or sell it eventually. The sound is fantastic, filling my office with very rich sound and serving as a HomeKit hub. Obviously, there are limitations to using a HomePod as well – currently it’s very ecosystem-limited. You can Airplay nearly anything to it but as far as native integration goes, it’s Apple Music or the highway. But it’s by far the best sounding speaker I own. It has smarts to auto tune itself for the room that it’s in, and it shows.

For a while, I just used it when I was working from home but once we made the Sonos switch, I started thinking more about moving to Apple Music. Originally, moving to Sonos wasn’t really about moving away from Spotify. That happened after messing around with the possibilities of an AirPlay 2 based whole-home audio setup. With HomePod + AirPlay 2 you can use your phone to control the HomePod and make that the primary audio source, sending music to the other speakers throughout the house. That way, you don’t run into most of the limitations that AirPlay 2 has compared to Chromecast. Since the HomePod is streaming music to all of the other speakers in our house instead of my phone, it’s really the best of both worlds. If Apple ends up allowing Spotify as a native HomePod integration later this year, it’ll be an even more elegant solution.

Google Assistant to Alexa

My original goals were to replace the Google Homes with better sounding speakers but leave nearly everything else in tact. However, one that original choice was set into motion I found myself making other tweaks as I went – integration with the HomePod, focusing more on Airplay 2, and then switching the default assistant on the Sonos speakers to use Alexa.

The reason is simply the cascading effects of moving to Apple Music. Alexa works with Apple, while Google does not. It’s still too early to have a ton of observations about Alexa vs Google Assistant but I will say that the UX of the Alexa app is light years better than the nested options hellscape Google has put out.

Conclusion

I’ve definitely added a little bit of short term complexity to how we were playing music in our house by making this switch. I know my wife has had a few instances where she throws her hands up with my constant experimentation with this sort of stuff. However, the trade offs have been worth it so far for me:

Pros

  • Way better sounding speakers overall.
  • More choices & service integration.
  • I’ve been really happy with Apple Music as a Spotify convert.
  • More music variety as a result of me invoking music via apps instead of voice.
  • Moving to Alexa puts my tech eggs in more baskets, and reduces my dependence on Google.

Cons

  • The previous setup was more streamlined compared to what we have right now. We could invoke music to any speaker via voice and it just worked.

I’ll be interested to see what Apple has in store for the HomePod as opening it up will further improve the flexibility of what we can play across the entire home. If Apple ends up releasing a mini version or one with a screen (my dream product), then we’d really be cooking.

Dang, The iPad Pro Magic Keyboard Looks Cool in X-Rays

Posted on

From iFixit:

New trackpad designs, double-loaded hinges, quirky wiring and magnet arrangements—an X-ray peek inside the Smart Keyboard is a trip into some serious engineering.

Looks like a full-fledged laptop X-ray. The $300 (or $350!) price tag is definitely steep for the Magic Keyboard but it does appear to be an engineering marvel. What’s interesting to me is the lack of innovation by 3rd parties when it comes to the smart connectors. Wonder if Brydge or others can give consumers more choice at different price points.

Rebuilding our tech stack for the new Facebook.com

Posted on

From Facebook Engineering Blog:

When we thought about how we would build a new web app — one designed for today’s browsers, with the features people expect from Facebook — we realized that our existing tech stack wasn’t able to support the app-like feel and performance we needed. A complete rewrite is extremely rare, but in this case, since so much has changed on the web over the course of the past decade, we knew it was the only way we’d be able to achieve our goals for performance and sustainable future growth. Today, we’re sharing the lessons we’ve learned while rearchitecting Facebook.com, using React (a declarative JavaScript library for building user interfaces) and Relay (a GraphQL client for React).

Tons of great nuggets in here, and a lot that I can relate to in what’s we’ve been up to at my job.

Facebook reduced their CSS by 80%, added code splitting and added code budgets to help deliver what’s needed only when it’s needed. They also moved to GraphQL to modernize their data fetching.

It’s a shame Facebook makes products that are so terrible for society, because they really do build world-class software.

The Senate just voted to let the government keep surveilling your online life without a warrant

Posted on

From Recode:

the Senate voted on Wednesday not to protect Americans’ internet browsing and search history data from secret and warrantless surveillance by law enforcement. The measure needed 60 votes to pass. It got 59.

I barely recognize this country anymore.

It’s also worth noting, this is yet another reason to use DuckDuckGo as your search engine (they don’t save your searches or track you), and reconsider using browser history sync. A VPN will also help if you’re worried about your ISP selling or otherwise turning your data over.

‘Vintage’ Apple Products

Posted on

From Apple:

Vintage products are those that have not been sold for more than 5 and less than 7 years ago. Mac, iPhone, iPad, iPod, and Apple TV vintage products continue to receive hardware service from Apple service providers, including Apple Retail Stores, subject to availability of inventory, or as required by law.

Crazy to think that a laptop I bought in late 2015 is going to be considered vintage soon.

How the Novel Coronavirus is Speeding the Scooter Apocalypse

Posted on

From The Verge:

There are some early signs that shared mobility could survive the crisis, even come out looking better than before; one of those “it’s always darkest before dawn” kind of things. But before that happens, the scooter industry as a whole will need to shrink, as it already was doing before COVID-19. And a lot of people will probably lose their jobs.

In what seems like a lifetime ago, I would walk past a local MARTA train station after work every day and it looked like the rapture happened without me. Scooters were flung about in every which way, and it made walking down the sidewalk a real pain. Every time I needed to use a scooter, it seemed like I never had the correct app and couldn’t find a scooter for the one that I already had credit with. First world problem to be sure, but it rarely left me feeling positively about the experience.

You never like to cheer for the downfall of any company, but I’m not all that upset to see this industry shrinking. Ideally there’s only one or two of these companies that work with local public transportation to fill the gaps in their service, rather than the streets being a wasteland littered with a dozen different scooter brands at any given time. Consolidation could be a good thing, with more predictable service and fewer apps to navigate.

Alphabet’s Sidewalk Labs scraps its ambitious Toronto project

Posted on

From Ars Technica:

But Sidewalk Labs’ vision was in trouble long before the pandemic. Since its inception, the project had been criticized by progressive activists concerned about how the Alphabet company would collect and protect data, and who would own that data. Conservative Ontario premier Doug Ford, meanwhile, wondered whether taxpayers would get enough bang from the project’s bucks. New York-based Sidewalk Labs wrestled with its local partner, the waterfront redevelopment agency, over ownership of the project’s intellectual property and, most critically, its financing. At times, its operators seemed confounded by the vagaries of Toronto politics. The project had missed deadline after deadline.

I’m always torn when I see these sorts of smart city initiatives pop up. In reality, it’s about how I feel about smart home stuff in general. On one hand, I’m excited about the promise of an efficient and “always learning” city that can help planners optimize. In a world that will be increasingly affected by climate change, finding ways to squeeze every bit of efficiency out of the existing infrastructure is obviously a win.

However, rarely do these things come without hidden complexity or tradeoffs. In this case it’s cost overruns, privacy implications and half-baked solutions.

Direct Support & Subscription Fatigue

Posted on

As I mentioned recently, I’ve been listening to even more podcasts than ever that I’m mostly tooling around the house and doing yard work with all of this spare time. As a result, seeing some of the shows and sites I love start to feel the pinch of reduced ad spending have sparked me to start directly supporting them via membership or donation. Recently, I’ve started to support the sites and podcasts that give me the most joy in these fairly monotonous times: Pewter Report, Relay.fm, Macstories, The Athletic, Stratechery and a few others. All told, it’s about $25/month but I feel like I’m doing my part to keep these folks going.

I’m no behavioral economist but I’ve always wondered what the average difference between the increased brand affinity a subscriber/member feels and the subscription fatigue associated with yet another monthly fee is. I feel like the $5 or so a month I pay to these services, podcasts or sites that give me a ton of joy has an outsized amount of real estate in my head. I love knowing that I’m helping directly support podcasts, apps, websites but I also find myself sweating the relatively small amount that I’m giving them. I know they’re in a bind too – going subscription-only reduces their addressable advertisement market and overall reach, while relying only on “donations” makes that support super elastic.

I’ll be curious to see how much the pandemic-induced ad spending changes the podcasting revenue game. The most positive effect could be additional creativity around revenue generation, ad reads and membership programs, with the least being consolidation, paywalls and more invasive tracking. Let’s hope there’s more innovation in the “positive” areas.

11-inch iPad Pro Experiment

Posted on

From Ryan Christoffel at MacStories:

This is probably too general of advice, but I’d recommend that if you expect to regularly use your iPad Pro as a tablet, the 11-inch will likely be your best option. If, however, you expect to use it almost entirely with a Magic Keyboard attached, the 12.9-inch is a good bet. Both devices can work in both modes, but the 11-inch is a better tablet, and the 12.9-inch is a better laptop.

I really enjoyed this article, as it captures a lot of my feelings regarding using the iPad as your primary computer. As my personal laptop begins to age, I find myself using my work issued MacBook Pro for most of my “computer” tasks, and an iPad for nearly everything else. The iPad Pro + Magic Keyboard combo is a very versatile (albeit expensive) solution for almost anyone now. If you’re going to go that route, the biggest decision is how much you want to use it as a traditional tablet.