I’m a longtime, diehard Tweetbot user and it’s been one of my favorite apps on the platform since it’s debut nearly seven years ago. But Nick Heer recently pointed out a nifty feature that’s exclusive to Twitterrific — “Delete and Edit Tweet”. Many Twitter users have been clamoring for the ability to edit tweets and the folks at Iconfactory have developed a clever workaround.

When you choose the option, through the ellipses menu on one of your tweets, Twitterrific will delete the selected message and open a compose view with the contents of that tweet filled in. This gives you the ability to quickly fix typos or grammatical errors without having to go through multiple steps to accomplish it.

This feature alone piqued my interest in the app. I haven’t revisited Twitterrific since the last major release and thought this was a great opportunity to give it another try. I’ve spent the past week with Twitterrific as my primary Twitter client and the following is an unordered list of thoughts and observations regarding the app:

I wish that I could hide display names in the timeline. I tend to prefer minimal user interfaces and would rather my Twitter app only show usernames within the timeline. If I want to see a user’s display name, I’m more than willing to tap their avatar to see it in their profile view. Display names aren’t used within tweets for mentions or replies, so why should they be emphasized in the timeline?

I find myself searching Twitter several times each day and wish I could set the search view as a tab, but there’s no option to do so. The only way to access it is through the sidebar, which adds another interaction to the process — tap or swipe to open the sidebar and then tap again to open the search view.

I’m not happy with the font options in the app. I’ve used Avenir in Tweetbot for a couple of years and it looks like trash in Twitterrific. The weight is too heavy for my taste and it looks sort-of blurry — it’s not crisp and clean like it is in Tweetbot. I’ve settled on using Helvetica Neue with a slightly increased line height. I’m not in love with it, but it’s better than all of the other options.

I don’t like how replies are displayed. I wish usernames were included within the tweet rather than being displayed on their own line above the tweet’s content.

The unified timeline is Twitterrific’s best feature. Displaying all of your mentions and replies within your primary timeline, whether you follow the person or not, is absolutely brilliant. If Tweetbot was to steal one feature from Twitterrific, I hope it would be the unified timeline.

The Project Phoenix icon is gorgeous — one of the best app icons on my device.

In Tweetbot, when you setup a mute filter, you can choose an expiration date. This is perfect for hiding tweets about a specific event during its duration to prevent spoilers and keeps your mute filters tidy by automatically removing them after their specified timeframe. Twitterrific doesn’t have that ability. Muffles, as they call them, are either on or off — there’s no way to set an expiration date and that’s pretty lame.

I keep my iPad in landscape mode the vast majority of the time, but Twitterrific gives you no way to hide the tab bar in this view, even if you have the sidebar displayed. And the sidebar is necessary to keep line length reasonable. You’re forced to choose between good line length and redundant user interface elements or terrible line length. Both of those options lead to a bad user experience.

I understand what they’re trying to do, but I don’t like the use of emoji in notifications. It doesn’t do enough to help me distinguish between mentions, likes, and so on. It only feels like it’s adding to the noise.

I’m not fond of how tweets are dated. I don’t need relative and absolute dates on each tweet. And displaying this information below the contents of the tweet — instead of right-aligned next to the username as Tweetbot does — adds unnecessary height to each tweet giving you less content on the screen at once.

I enjoy the use of color within the timeline to differentiate between your own tweets, mentions, and everything else. It’s a nice touch.

Twitterrific is a well-made application with some bright spots, but after spending a week with it as my primary Twitter client, I’m going back to Tweetbot. I’ll miss the Project Phoenix icon in my dock and the utility of the unified timeline, but those two features aren’t enough for me to make the switch. Tweetbot features beautiful type, a perfectly minimal user interface, and it makes better use of screen real estate on the iPad with the multicolumn view. Overall, Tweetbot is still the best Twitter client on the platform.

An incredible update to my favorite podcast app. It features Smart Resume, the option to delete episodes 24 hours after completion, and support for some password-protected feeds. If you already use Overcast, get the update now. And if you don’t, this is a great time to consider switching.

I was really excited about support for password-protected feeds. I subscribe to the Wrestling Observer and listen to many of their shows, but the only way to get those episodes into Overcast has been to utilize the premium-only uploads feature. I built a workflow to help with the process, but it’s still tedious. My hopes were high, but upon testing it with the Wrestling Observer’s feeds, it looks like Overcast’s system doesn’t work for the shows I listen to. They must be using some alternative authentication method that Overcast doesn’t support. Maybe that will change in a future update, but until then, I’m stuck using my old process.

Smart Resume, on the other hand, is exactly the type of feature that has kept me using Overcast. Adjusting the seek point to add context and minimize resumes in the middle of words is such a great little detail that subtly improves my listening experience.

Unfortunately, the world wide landscape today desperately calls for us to encrypt what we can. We, as creators on the web, are obliged to help protect the privacy and security of our readers. Enabling HTTPS on a domain doesn’t hurt existing content, but it does provide your visitors with a little more protection, and — critically — it doesn’t require a change in their behavior. They get to keep just using the web.

There’s no easy solution to this. Encrypting the web is almost certainly better than not, but it does introduce an additional barrier to entry for new creators. And, as I said when I linked to Dave Winer’s piece last week, it would be a very bad idea to dismiss unencrypted webpages as a byproduct of encouraging developers to move to HTTPS. To put it another way, it’s okay to move forward, but that doesn’t mean we should destroy everything behind us in our quest for progress.

I also agree with Winer on another key point: enforcing a pseudo-mandatory policy on HTTPS makes it that much harder for someone new to this stuff to even begin to understand it. As Frank Chimero recently wrote, building stuff for the web has become vastly more complicated since even five years ago. I’m happy to keep learning new skills and growing my understanding of what the web can do, but I don’t know where to begin on this modern web. I don’t intend to hold myself up as a barometer of the complexities of modern web programming or anything — I just don’t know what’s going on any more. I’ve been doing this stuff for nearly twenty years. I don’t know how someone who is eight years old could start digging into React, or Node.js, or any of the other modern JavaScript-based ways of writing <h1>hello world</h1>.

I’m sure the kids will figure it out — they always do. However, I worry that introducing more requirements, even something as simple as HTTPS, can be discouraging. That’s the last thing HTTP/HTML web should be: discouraging. It is one of the greatest enablers of communication in human history. Let’s not allow its future to be dictated by browser vendors.

Craig Hockenberry, regarding the ten year anniversary of the original iPhone SDK:

After recovering from all the great news, developers everywhere started thinking about shipping. We didn’t know exactly how long we would have, but we knew we had to hustle.

In the end, we had about four months to get our apps ready. Thanks to what The Iconfactory learned during the Jailbreak era, we had a head start understanding design and development issues. But we still worked our butts off to build the first iPhone’s Twitter app.

What an exciting time that was. I just wish I would have had the foresight to spend some time learning about app development instead of simply writing about the platform.

A lot of the web consists of archives. Files put in places that no one maintains. They just work. There’s no one there to do the work that Google wants all sites to do. And some people have large numbers of domains and sub-domains hosted on all kinds of software Google never thought about. Places where the work required to convert wouldn’t be justified by the possible benefit. The reason there’s so much diversity is that the web is an open thing, it was never owned.

I think the move to HTTPS is good for most websites, but it’s unfair for browser makers to punish owners of simple webpages that haven’t switched to the encrypted protocol. Maybe we just need a longer transitionary period. Or perhaps browsers should only warn users if the webpage they’re viewing includes text fields and forms that request user data. That’s far from a perfect solution, but dismissing large portions of the web because they aren’t HTTPS seems like a bad idea too.

Workflow is an essential app for iOS that lets users build script-like systems with a simple drag and drop interface. It’s powerful enough for experts, giving them the flexibility to combine numerous applications and web services into a single workflow. But its still able to maintain an approachability that allows novice users to find utility in it too.

The Toolkit is a collection of workflows for publishing on the web that I’ve developed throughout the two years that I’ve been using the app. As I add to the kit and refine each of the workflows’ functionality, I will be updating The Toolkit’s webpage with these new additions. I simply hope that you’ll find them useful, even if only to build off of or learn from.

A few days ago, I got into a Twitter discussion about things Apple changed and were mocked for changing, yet those changes were copied and, eventually became the new normal. The original discussion was prompted by a wave of phones embracing the notch.

Matt Birchler with a neat feature request for voice assistants — the ability to request an action to be triggered at a future time. This would be useful for my wife when a snow day causes an unexpected day off. We have HomeKit triggers setup to change our ecobee’s temperature when we are expected to be at work. But when she gets the call that school is going to be cancelled, she could override the automatic temperature adjustments by telling our HomePod “hey Siri, set the ecobee to 71° tomorrow morning at 8am.

I’ve had my eye on the smart speaker market for a handful of years now. Not just because I’m a gadget nerd, although that doesn’t hurt, but because I’m obsessed with podcasts and could see the utility in a computing device that was almost entirely interacted with through voice.

These products were never practical for me, though. Up until this past fall, my wife and I lived in a small apartment with a nearly-closet-sized kitchen, which always seemed like the most suitable location for a smart speaker. But power outlets and counter space were at a premium. I had dabbled with connecting a set of speakers to an old AirPort Express, but they were quickly ousted when we needed the counter space for food preparation and storage.

One of the reasons we purchased the house we’re in now is the size of the kitchen. My wife and I love cooking at home and the new place has two or three times as much counter space as our apartment did. This, of course, means that we finally had space for a smart speaker in our lives.

In my younger years, I probably would have ordered an Amazon Echo in the car ride home from our closing, but I have a bit more patience these days. Apple had already announced the HomePod when we signed the paperwork and the last time I purchased a piece of Amazon hardware it ended up in my desk drawer a few months later. The second-generation Kindle was no match for the original iPad.

I didn’t want to go through that experience again. So I waited for Apple to release their entrant into the smart speaker market. It was delayed a bit, which was lame, but I remained patient. And when I woke up the morning of pre-orders, I purchased one in space gray.

Design

From the moment I slid the top off of the box, I knew the HomePod was a premium product. It features a sleek glass touch panel up top, a futuristic spongy material over the speaker and microphone arrays, and a rubbery base that will keep the unit from shifting during playback.

The HomePod is deceptively heavy. You notice its weight while carrying the shipping container, but it isn’t until it’s unboxed before you realize that the packing material isn’t adding much to the heft. But it’s the good kind of heavy. The kind of heavy that reassures you that the $349 you spent on a speaker wasn’t just for the logo — it’s made out of high-end materials and built like a tank.

You may have heard about the HomePod’s power cable — either on Twitter or in one of the myriad product reviews — and I can say without hesitation, the hype is real. Now I’m not one to complain about Apple’s cables, I haven’t experienced the rapid fraying and splitting that others have, but the HomePod’s power cable is almost certainly the nicest I’ve ever seen. It’s wrapped in a durable, braided material and feels like it’s built to last.

The size of the HomePod was a bit surprising to me. I was aware that it was larger than the Google Home and Amazon Echo, but I don’t have much experience with those products. The HomePod was just a bit bigger than I expected. Not to say the HomePod is too large, by any means. The device fit on my kitchen counter just fine without dominating the space, but it’s not exactly something you could hide in a corner and forget about.

Overall, the hardware design of the HomePod is top-notch. It’s comparable to the AirPods or iPhone X in regards to their superb materials and near-flawless build quality. There’s no gaps where two materials meet or any noticeable inconsistencies to speak of. It’s just a well-manufactured product that was designed by a team with an incredible attention to detail.

The HomePod does have one major design flaw, though, that will certainly be difficult for some buyers to get past. The unit’s base can cause white rings to appear on some wooden surfaces. I haven’t experienced the issue myself, but Jon Chase addressed the problem in his review for Wirecutter:

An unhappy discovery after we placed a HomePod on an oiled butcher-block countertop and later on a wooden side table was that it left a defined white ring in the surface. Other reviewers and owners (such as Pocket-lint, and folks on Twitter) have reported the same issue. Apple attributes the problem to the oils diffused between the speaker’s vibration-dampening silicone base and the wood, and suggests wiping the marks off with a damp or dry soft cloth, or else moving the HomePod to a different surface. An Apple representative added over email that “the marks can improve over several days after the speaker is removed from the wood surface,” and that if they don’t fade on their own, you can “try cleaning the surface with the manufacturer’s suggested oiling method”—in other words, go refinish your furniture. This really undermines the design aspect of the HomePod—especially if you were thinking of displaying it on some prized piece of furniture—and it will surely be a sore point for many potential buyers. In other testing, we have seen no visible damage when using it on glass, granite countertop, nice MDF, polyurethane-sealed wood, and cheap IKEA bookcases.

I suspect that most HomePod owners will never come across this flaw, but for those who do, it will be infuriating. The least Apple could have done was communicate with customers about the problem beforehand. But ideally, they would have designed their speaker without the flaw at all.

I don’t think this should deter the majority of customers from purchasing a HomePod, though. In most circumstances, you can place it on another surface or put something underneath it to prevent the white rings from forming. It’s a bit lame, I know, but it’s not much of a hassle to deal with as long as you’re aware of it. And it’s worth noting, HomePod isn’t the only smart speaker that has this issue.

Configure

Setting up the HomePod was just as easy as you’d expect. Plug in the power cord, hold your iOS device close by, and follow the on-screen instructions. You tell the software what room the HomePod will be in, it asks if you’d like to enable personal requests, and than it prompts you to transfer your Apple accounts and Wi-Fi settings. And that’s it. The HomePod’s ready to go.

I have kept the personal requests feature disabled on my HomePod. I’m not exactly worried that some prankster in my circle of friends is going to respond to my messages or add items to my to do lists. But the HomePod is only tied to a single user’s iCloud account. I didn’t want to start using features on the device that my wife couldn’t. I want the HomePod to be our smart speaker, not just mine.

It matters to me that she’s able to get just as much out of the HomePod as I do. If I started creating notes or adding items to Reminders from the device, she would inevitably ask if she could do so too. And when I broke the news about the HomePod being tied to my account, it might steer her away from using it at all. I would prefer to avoid that if possible — $349 is a lot to spend on a speaker that only one person in the house uses.

Hopefully, Apple will add support for multiple iCloud accounts in the future with the ability to recognize each users’ voice. I’d be more than willing to enable personal requests, at that point. But until then, I’ll keep the feature disabled.

Interact

The HomePod has three input mechanisms — the touch panel, Now Playing in iOS Control Center, and Siri. This feels like a great assortment of options, all of which can be quickly accessed based on your current context. In my two weeks with the device, I actually found the touch panel to be surprisingly useful. It features plus and minus buttons for adjusting volume and you can tap just about anywhere else on the glass to perform a handful of functions — tap for play/pause, double tap for next track, triple tap for previous track, as well as tap and hold to activate Siri.

If I‘m right near the HomePod and my hands aren’t covered in food, I typically just use the touch panel to control playback. Apple was very generous with the tap targets — you can basically just slap anywhere on the glass and the HomePod will do what you wanted it to. Even the volume buttons allow for a fairly large margin of error, which you wouldn’t expect given their visual representation on the device. There’s no need to be precise with your taps and, more importantly, there’s no delay between your input and HomePod preforming the action.

With iOS 11.2.5, Apple added new functionality to Control Center’s Now Playing platter. If you have Apple TVs or HomePods on the same Wi-Fi network as your iPhone or iPad, it will display playback controls for each of those devices. This is especially convenient if you’re listening to audio from a distance, where Siri wouldn’t be able to hear your commands. I haven’t used this feature more than a handful of times, but it works well. There’s almost no delay between tapping a control on my iPhone and the HomePod responding to the input. And it’s the only way to see what the device is playing without using your voice.

One thing of note about the Control Center playback controls for HomePod, is that it helped me uncover an annoying bug that cropped up three or four times during my two weeks with the device. Occasionally I would ask Siri to playback songs from an artist or album, she would respond as if the request was understood, and then nothing would play. In Control Center on my iPhone, I could see the HomePod rapidly rotating through each of the songs before finding one that it could actually play.

My suspicion is that this is tied to my use of iTunes Match instead of Apple Music. But I wasn’t able to determine if HomePod was only skipping tracks that I had uploaded from my iTunes Library or if it was skipping any track that wasn’t already cached on the device. Or it could just be some weird Wi-Fi connectivity issue. Luckily unplugging the HomePod and rebooting always fixed the problem, but I’d like to see Apple address this in a software update soon.

The real star of the show for interacting with HomePod is Siri. Simply start a phrase with the wake words — “Hey Siri” — and ask the device to play some music, tell you the weather, read the latest news, and so on. What Siri is capable of on HomePod is severely limited compared to other smart speakers from Amazon or Google, but I think Apple made the right compromises with their first-generation offering.

I fully expect Apple to continuing adding to Siri’s capabilities, but out of the gate, I think Apple was smart to focus on a small number of areas. I would rather Siri have a handful of features that are executed well, with more coming in the future, than to ship with dozens of half-baked abilities that I wouldn’t be able to rely on.

In my time with the HomePod, it has only failed to respond with a sufficient answer in one instance. I was cooking pork tenderloin and, on a lark, asked Siri what temperature it should be cooked to. She responded by saying “I can’t get the answer to that on HomePod.” Now, that was disappointing for sure, especially since I believe HomePod is at it’s best in the kitchen and I expect this might be a common query. But I would rather it fail than give me an unusual or incorrect response — I wouldn’t want to get sick because my HomePod told me to cook our pork to the wrong temperature.

Of course, it’s certainly possible that I haven’t run into too many Siri failures on HomePod because I have been subconsciously avoiding certain questions because I’m aware of what Siri is capable of. But my wife, who isn’t obsessed with this stuff like I am and has used the HomePod more in these two weeks than I have, has only had Siri fail on her once or twice. That’s a successful rate in my book.

In our daily lives, Siri has been more than capable of handling the vast majority of what we’ve thrown at her. Activating HomeKit devices, controlling audio playback, and asking about the weather have been our most common queries. And that fulfills nearly all of our needs in a smart speaker. That might change in the future as our expectations grow, but for now, it’s quite good.

Listen

The HomePod is an incredible speaker. I can’t compare it to the Amazon Echo or Google Home because I have next to no experience with those devices, but the HomePod sounds better than any other speaker I’ve owned. To be fair, I’m not exactly an audiophile. But the bass was strong without overpowering the rest of the music and there was enough clarity in the vocals and instrumentals to feel like I could focus on each aspect of the music without any of it sounding muddy.

I spent most of my time listening to, what most would classify as, pop-punk music. You might remember this as a popular genre in the mid-2000s. Here’s a small sample of the albums I’ve been listening to lately:

What’s most interesting about my experience listening to music on the HomePod compared to most others is that I’m not an Apple Music subscriber. I’ve kept my music library in Plex for a little over a year and use Plex’s iOS and Apple TV app for playback. Since Apple hasn’t added support for third-party audio apps in SiriKit, this left me with three options — subscribe to Apple Music, subscribe to iTunes Match, or utilize AirPlay for all of my music playback.

The last option, while technically possible, wasn’t even considered. AirPlay is a fantastic feature and I make use of it regularly, but it’s too much of a barrier to entry for everyday use. The extra step of initiating AirPlay to the speaker means that we might simply play audio through our iPhone’s speakers to save ourselves the trouble. I didn’t want that. If we were going to spend $349 on a smart speaker, we need to be able to initiating music playback with our voice. We already have a decent collection of music purchased through iTunes, which the HomePod can play with or without an iTunes Match or Apple Music subscription, but we still listen to albums that we ripped from CDs more than a decade ago.

This left us with either iTunes Match or Apple Music. There’s pros and cons to both, but we ended up choosing iTunes Match because it’s far less expensive than Apple Music. My wife and I don’t discover and listen to new music often enough to justify the cost of a subscription service. It still makes more sense for us to purchase a handful of albums each year than pay $10-15 a month for Apple Music.

iTunes Match doesn’t offer all of the “Musicologist” features that Apple Music does, with automatically generated playlists and whatnot, but it works just fine for our needs. It does mean I’ll have to maintain my library in two locations — Plex and iTunes. But I was already adding music to Plex by hand anyway and, as I mentioned above, we don’t acquire new music frequently.

One major gripe I have with all smart speaker interfaces — which manifests itself in just about everything that you do with it, but is simply an inevitability of a screen-less device — is the lack of serendipity. It’s mitigated in some ways with Apple’s personalized playlists on Apple Music and the ability to shuffle all of your music with iTunes Match. But without a list of albums to scroll through, there’s no way to browse your collection and happen upon a forgotten album.

I don’t know about everyone else, but I can’t keep more than a handful of albums or artists in my head at any given time. On the HomePod, I found myself requesting the same few albums and artists every time I entered my kitchen. I suppose this isn’t too much of a problem. You can always relegate music discovery and serendipity to your iPhone or iPad and stick with your recent favorites on HomePod. But this realization puts a damper on how impressive it is to instantly playback nearly any song you could ever think of — if you’re only playing the same handful of albums, what’s the point of all this extra technology?

Of course, this doesn’t just pertain to the HomePod and isn’t something that’s worth going in too deep about within the context of this review. But it is worth considering if you’ve been thinking about purchasing such a device. I still believe I get enough value from the HomePod, but for others, it might not be worth $349 for a speaker that you never play more than a handful of albums on at any given time.

But of course, the HomePod isn’t just a music speaker, it can control HomeKit devices, receive audio over AirPlay and playback podcasts. My wife and I have five HomeKit devices at the moment — three indoor iDevice Switches, an outdoor iDevice Switch, and an Ecobee 3 lite. They add an astounding amount of convenience to our lives and the HomePod is able to control them with ease. Walking in from our garage with both arms full of groceries and being able to just tell Siri to turn on the lights is simply delightful.

We were already on board with HomeKit, but owning a HomePod has accelerated our interest in the ecosystem. We plan on purchasing one of those light bulb adapters for our kitchen soon — most likely the iDevices unit — and maybe a few more switches to outfit the rest of our house. It’s an excellent protocol with a bright future and I expect HomePod will play a pivotal role going forward.

And then there were podcasts. I spend the vast majority of my listening time with spoken audio in my ears — shows like Cortex, Accidental Tech Podcast, and the recently revitalized The Menu Bar, to name a few. But I haven’t spent a ton of time listening to podcasts on the HomePod. I use Overcast as my podcast client of choice and, as I mentioned before, you can’t use Siri to playback audio from third-party applications.

You can tell Siri to play the latest episode of a specified podcast, but unless you use Apple’s podcast app, you’re playback position won’t sync with your primary player. I have used this feature for a few shorter podcast episodes and then deleted the episode in Overcast once it was completed, but there’s no way I’m going to do this with any regularity. It’s just too fiddly.

Ideally, Apple will add audio app support to SiriKit at WWDC. Or at least, that’s when I hope the feature will be added. In the meantime, if you want to use a third-party audio service with your HomePod, you’ll have to do so over AirPlay. It’s not as pleasant to use as Apple’s first-party services, but at least we have the option. There’s a small delay on the audio, which is mildly annoying, but you can still use many of the same voice commands to control playback — play, pause, and skip forward or backward thirty seconds.

We don’t just use AirPlay for Overcast, though. When my wife and I have friends or family at the house, we like to play a different mix of music from what we normally listen to. We have historically paired a Bluetooth speaker to our iPhone and played music from Pandora, but now we’ll be able to AirPlay music from Pandora’s Apple TV app to the HomePod. This gives us a large interface for choosing music, that everyone in the room can offer suggestions on, and a speaker closer to the areas of the house where we tend to congregate — the kitchen and dining room.

This setup has worked well and has been a hit with the guests we’ve had over recently. Especially with how easy Apple has made it to send audio from an Apple TV to an AirPlay speaker. For applications that use the standard system playback interface, simply swipe down on the Siri Remote’s trackpad while the media is playing, swipe over to the Audio tab, and choose you’re desired destination. And for applications that don’t use the standard interface, jump to the Home Screen, hold down the play/pause button, and choose which AirPlay device you’d like to send your audio to.

Overall

The HomePod is a tremendous product that has quickly integrated itself into my daily life. I use it in the morning for weather forecasts, we listen to music on it while my wife and I cook dinner, and I use it for podcast playback while I’m doing dishes. It has its faults, but I think purchasing one was a wise decision.

It might not be best for everyone, though. It’s a bit more expensive than competing products and has a limited set of features at the moment. Whether the HomePod is right for you depends a bit on what’s most important to you in a product like this. If you want a superb sounding speaker that works well with your existing devices, looks great on a kitchen counter, and can tap into Apple Music, the HomePod is right for you. But if you want something that’s cheap, works with Spotify, and integrates with hundreds of third-party hardware and services, it might not be.

The best advice I can give is to wait and see how HomePod grows with future software updates. Apple has already announced AirPlay 2, and the ability to pair two HomePod’s into a stereo set, both of which should be coming later this year. AirPlay 2 will let you control multiple speakers throughout your home — playing different audio on each or the same audio on all of them in unison. And this is how Apple describes the stereo speaker pairing feature on HomePod’s product page:

Put another HomePod in the same room and they automatically detect and balance each other. With advanced beam forming capabilities, a HomePod pair is able to create a wider, more immersive soundstage than a traditional stereo pair.

I believe Apple has even more features in store for the future of HomePod. I think we will eventually see support for third-party audio apps in SiriKit. Which, assuming developers add support for it, could let you initiate playback of audio from Spotify, Pandora, Overcast, and more using only your voice.

There’s also the potential for Apple to add support for multiple iCloud accounts or the ability to connect to HomePod over Bluetooth with non-Apple devices. All of these additions could change the value proposition of a $349 smart speaker. But I wouldn’t suggest that you purchase a HomePod with the expectation that these will be coming in the future.

If you’re on the fence at all, just wait. In the meantime, maybe pick up an Echo Dot or a Google Home Mini to see if a smart speaker is even something you’d enjoy having. You might find that it doesn’t fit well into your life. And you can always revisit the idea in a year or two after Apple has added a number of new features to the software or expanded the lineup with an inexpensive HomePod Mini.

But if the HomePod sounds like something that does enough for you today, even with the relatively expensive purchase price, then get one. You’ll be very happy with it.