I use iZotope’s RX audio utilities constantly. They clean up background noise, remove buzzing and humming, and even remove the reverberations from echoey rooms. There was even that one time when someone played three hours of D&D with a sump pump beeping in the background every 30 seconds, and I used iZotope’s tools to isolate that frequency and eliminate the beeping entirely. It’s pretty great stuff.
What’s not so great has been the company’s slowness to embrace Apple silicon. While Rosetta has made the iZotope RX Audio Editor app usable on my M1 MacBook Air, it’s hard to use CPU-intensive audio utilities without feeling frustrated that they’re not living up to their potential because they’re being translated from Intel code.
iZotope finally released its Apple silicon upgrade—it’s RX 9 9.3.0, so if you’re using a previous version of iZotope RX you’ll be forced to buy an upgrade—and yes, of course, everything is faster. A lot faster:
In my brief tests, the native version of the Spectral Denoise tool I use to remove background noises took 60 percent of the time it did in Rosetta mode. The extremely processor-intensive Dialogue Dereverb tool, which uses fancy math to subtract room echo, executed in 75 percent of the time it took in Rosetta.
This has, of course, also made it more painful to compare my $999 M1 MacBook Air to my beloved $5000 (in 2017 dollars) iMac Pro. Yes, it’s four years old, but it’s quite a thing to watch as Apple’s bargain laptop absolutely crushes my iMac Pro at removing reverb and almost matches it at removing noise.
This means that, for my purposes, my MacBook Air is officially a more powerful tool than my iMac Pro. The next-generation big iMac can not come soon enough.
Ooooh, Apple, you’ve done it this time. You’ve gone and gotten a European country mad—and not just any European country, but the Netherlands, a country which in the context of an epic fantasy novel would surely be a shadowy realm inhabited by demons who enjoy inflicting eternal torment, feasting upon your soul, biking, and growing tulips, but in this world they’re just into three out of the four.
The point of contention is the insistence by Dutch regulators that Apple must allow dating apps in the country the ability to use alternative payment systems, rather than being forced to use only the App Store. And because the regulators don’t consider Apple’s current “solution”—an onerous process that involves jumping through a bevy of hoops, including submitting a separate binary only for the Netherlands—to be sufficient, the country’s government is now fining Cupertino the baronly sum of €5 million per week, to a maximum of €50 million.
Which in turn has led the European Union’s head of digital policy, Executive Vice President Margrethe Vestager, to comment, “As we understand it, Apple essentially prefers paying periodic fines, rather than comply with a decision of the Dutch Competition Authority.”
And, simply put, yes. Yes it does.
To put it in perspective, that €5 million per week is about $5.6 million. Do I want to pay $5.6 million a week for 10 weeks? No, I do not. But that is because I make only a mere $5.7 million per week as a freelance journalist and podcaster, and really, what am I going to live on then?
But Apple? Yes, Apple, in the words of a succinct headline from 9to5Mac, “doesn’t care.” Because $5.6 million per week is not even pocket change for Apple; it’s not even money found in its couch cushions; it’s not even money that it accidentally leaves in its jeans when it puts them in the dryer, causing them to clink and rattle like the bones of the dead. It’s money that, I have it on good authority, Eddy Cue once ran through a shredder just to see if he could.
If that’s not enough for you, I present a non-comprehensive list of the things that Apple has spent $56 million on without even really thinking about it:
$56 million covers replacement earbuds for crackling AirPods Pro.
$56 million is what Apple spends to polish every single iPhone, iPad, MacBook, and Apple Watch in every single Apple Store in the world. (Not the Apple TVs, though, those things are dusty as hell.)
$56 million is Craig Federighi’s salon bill.
$56 million is what Apple pays Jon Hamm to not be in any of its Apple TV+ shows.
$56 million is what it cost to set all those AirPower charging units on fire. All of them. Not just the ones that were catching fire on their own.
$56 million is the cost of stocking Apple Park’s cafeteria with gourmet meals provided three times a day to employees, only there are just seven people working there right now, and let me tell you, they are eating like royalty.
$56 million is what Apple pays for tires on its self-driving car that will never come to market.
Apple once mislaid $56 million. It later turned out it had forgotten to cancel its gym membership for John Sculley. In 1993.
Look, Apple’s net income—its profit, not its total sales—just in its most recent quarter was $34.6 billion. If the Dutch government continued to charge $5.6 million per week until that was depleted, it would take until July 26. Five months!
Oh wait, in the year 2140.
Ho ho, won’t Apple look silly then?
[Dan Moren is the East Coast Bureau Chief of Six Colors, as well as an author, podcaster, and two-time Jeopardy! champion. You can find him on Mastodon at @dmoren@zeppelin.flights or reach him by email at dan@sixcolors.com. His next novel, the sci-fi adventure Eternity's Tomb, will be released in November 2026.]
I've spent a lot of time with different pieces of smart home tech over the last several years, but having finally made the jump from an apartment to a house that I actually own has opened up possibilities that weren't available to me before.
Thus: a foray into smart locks.
I've always been a little bit skittish at the idea of smart locks. The idea of being able to gain access to my home via a security vulnerability or hack seemed like a worrying prospect. But the more I thought about it, the more I realized those fears are largely unfounded. It's not as if picking a lock or smashing a window is particularly difficult. Nor does it seem likely that your average thief is going to spend time reading up on security exploits for your particular brand of smart lock.1
Moreover, I wasn't sure about the styling of some of the smart locks on the market, many of which stand out like a sore thumb thanks to complex keypads or glowing lights. Personally, I was interested in something a little more understated.
The Bolt keeps its battery inside the bolt itself, and it's easily replaceable.
The Bolt is unlike most other smart locks in that it doesn't replace your existing deadbolt. Instead, it fits inside your door, basically sandwiched in between the exterior keyway and the interior thumb turn. Inside sits a small motor with a Bluetooth chip, which can turn to shoot the bolt itself.
The engineering and design of this device is extremely clever. From the outside, the Bolt is completely invisible. The only place you can even see the device is the bolt itself, where Level's logo is embossed on the end. (In another particularly ingenious piece of engineering, the bolt also contains a replaceable CR2 battery that powers the whole assembly. Swapping it out just requires unscrewing the end cap.) Another plus: the existing key and thumb turn for the deadbolt work exactly as before, and don't interfere with the smart lock, or vice versa.
In addition to its invisibility, the other feature that drew me to the Level Bolt was its compatibility with HomeKit—not a given in the smart lock market right now.
For all of that, the Bolt isn't cheap: it ordinarily retails for $199, though I managed to snag it while on sale from Amazon for around $150.
If you're being specifically targeted by, say, the government or other state actor, that's a different story. But you also probably have better security arrangements. ↩
ViacomCBS changes its name, Peacock weathers the Super Bowl storm, the Disney brand continues to evolve, the culture of binge-dropping begins to fade away, Netflix is Doing Just Fine, and your letters!
Oh, tax season. Admittedly, the annual ritual has gotten a lot easier for me since getting a) an accountant and b) getting most forms delivered electronically as PDFs.
But I ended up with a wrinkle this year when I was processing a few of the tax forms provided by my clients. Several of them used a handy service that emails tax forms, which also thoughtfully encrypts and password protects those files. However, when uploading these for my accountant, I find it convenient to strip out the protection, so that I don’t have to provide a bunch of passwords as well.
In the past, I’ve simply used the loophole of opening a PDF in Preview, entering the password, and then using the File > Export as PDF… command or the old trick of printing to a PDF. That generates a version of the file without the password protection.
However, in macOS Monterey I was surprised to discover that these loopholes have been plugged. Exporting as a PDF simply maintained the password protection, and trying to save as as PDF from the Print menu wasn’t even an option: the system now grays it out.
In theory, this is a good security practice to avoid having password protected files easily stripped of those protections.1 But when it comes to my personal usage, it’s decidedly inconvenient.
But it turns out, whoops, Apple didn’t implement these security features across the board. Making an end-run around these restrictions is as easy as firing up your web browser. I used Chrome for my first foray, but I then tested the same process in Safari, and it works just as well.
Just open the password-protected PDF in your browser of choice, enter the password, and then print to PDF just as you would have in Preview (or even just open an unencrypted copy right in Preview). I was then able to save a password-free version.
All of this is a bit silly: there’s really no point in locking down Preview if all you need to do is use another app. Then again maybe this loophole will itself get plugged in another five years or so.
Of course, you still need the password, so just how much this is actually a security loophole is questionable. ↩
[Dan Moren is the East Coast Bureau Chief of Six Colors, as well as an author, podcaster, and two-time Jeopardy! champion. You can find him on Mastodon at @dmoren@zeppelin.flights or reach him by email at dan@sixcolors.com. His next novel, the sci-fi adventure Eternity's Tomb, will be released in November 2026.]
Upon arriving at our tropical resort for a week on vacation, my wife and daughter sat out on the deck doing crossword puzzles and I broke out my iPad with Magic Keyboard and tried to solve a puzzle of my own—namely, debugging a Python script. (This is how this family rolls.)
Literally minutes after leaving our house to go to the airport, I got an alert indicating that our home network might be down. Perfect timing, as always. Just before I left I had noticed a notification on my phone that our eero base station had restarted overnight. Given a five-hour flight to Hawaii to stew on that one, and a frantic text message from our housesitter who couldn’t watch anything on our TV, I took a shot in the dark and tried to remotely restart the eero.
The good news is, that totally worked. Within a minute, the network came back and our housesitter was happily binging the HBO Max shows she only gets to see at our house. I checked the weather page on my home server to verify that everything was up and running—and discovered that all of my precious charts and graphs were seriously messed up.
Jason imagines a future iOS App Store improved by sideloading, Myke gets back into reading digital comics, and both of them have a very strongly worded wish list involving the rumored big new iMac.
My thanks to Clay for sponsoring Six Colors this week.
Being more generous, more responsive, and more conscientious with people can take effort. And yet they’re core to our personal and professional success. That’s why the people behind Clay have created an intuitive and private home for your relationships—built automatically from your email, calendar, LinkedIn, Twitter, and iMessage.
Clay helps you show up informed and at the right time by creating and automatically updating beautiful, contextual cards for each of your contacts. You can use powerful features such as natural-language search, dictation and note taking, reminders, birthday notifications, news articles about people you know, and more to deepen your relationships over time.
Clay was thoughtfully designed specifically for macOS and iOS, using Apple’s latest tech, including a whole lot of SwiftUI. They’ve sweated the small deetails, including animation timings, shadows on cards, and haptic feedback on taps. There are iOS widgets, iMessage and iCloud calendar integrations, plus Spotlight search, Zapier integration, light and dark themes, and no advertising.
If you’re looking for a tool to be more thoughtful with the people in your personal and professional life that seamlessly integrates with Apple devices, give Clay a try for 60 days for free!
Electric Cars and Sleeping Macs
The long, slow transition to electric cars. And is Jason’s iMac shut-down procedure Lawful Good or Neutral Evil?
We’ve been in the Apple silicon era for 15 months now, and I’m tired of waiting.
My last two primary Macs have been 27-inch iMacs. First the original 5K model, then the iMac Pro. As much as I have loved using this iMac Pro for the past four years, I’m over it now. I’m ready to enter the Apple silicon era. And Apple has, thus far, failed to oblige.
Will Apple announce a new, large iMac at an event next month? “Reply hazy, ask again later,” said Bloomberg’s Mark Gurman. (Or at least that was my interpretation of his reporting.)
What I’m saying is, if the next new Mac to be announced is a faster Mac mini or an upgraded 13-inch MacBook Pro, I’m going to treat them fairly and evaluate them properly… and the entire time, I am going to be grumbling. Because what I want is a new big iMac.
So to pass the time while I’m waiting, I’m going to do what they taught me to do as a kid and enter the land of the imagination. Here’s what I want to see in a new, big Apple silicon-bearing iMac.
Don’t make it too big. As much as I have loved the screen on my 27-inch iMacs, I’m not sure more is better. Occasionally I find myself dragging windows in from the far-off corners of my display because it’s uncomfortable to focus on them unless they’re a little more central. Then again, there are times when I have to switch to “more space” mode to fit more on the screen. I contain multitudes.
However, the 24-inch iMac expanded the screen of the smaller iMac without making it feel huge. Apple has done some similar expansions with the MacBook Pro recently. So if Apple could take a 27-inch iMac and transform it into a 30-inch model without making it seem ridiculous, I’d go for that. But that’s all.
More ports than other Apple Silicon Macs. The 24-inch iMac comes with two or four ports, some of them Thunderbolt and some USB. That won’t cut it on the larger iMac, which needs to offer Thunderbolt ports, at least a couple of USB-A ports (you heard me!), and an SD card slot. (Just for perspective: my current iMac Pro has four USB-A and four Thunderbolt ports on the back, as well as an SD card slot! And I use them, frequently! This sort of Mac should not be limited by its ports.)
A better webcam. I will continue to hold out hope for Face ID on the Mac because it makes a lot of sense—but it hasn’t happened yet, so it’s a bit of a stretch. Still, at the very least, the new iMac should offer a webcam more in line with what’s available on the iPad line. That means a 12-megapixel camera with support for Center Stage, a feature that feels like it was built specifically for the iMac. I’m tired of Apple releasing Macs with 1080p webcams and declaring them the best Mac webcams ever. Compared to the iPad and iPhone’s front-facing cameras, they’re a joke. It’s time to change things, and this is the right place to start.
Better ergonomics. If I’m being honest, the 24-inch iMac’s stand seems a little short. And since it’s not adjustable, if you need to get it to the proper height, you’ll need to put that cute little iMac on a riser or dictionary or leftover cardboard box. That’s not great, and I hope Apple puts a bit more effort into the ergonomics of the larger and more expensive iMac model. I don’t think we need a $1000 stand in the vein of the Pro Display XDR, but users should be able to make their iMac taller or shorter as needed.
Everything the M1 Pro and M1 Max deliver. I’m expecting Apple to offer the new iMac in both M1 Pro and M1 Max chip configurations, as they have with the MacBook Pro. (If, as rumored, Apple is working on a dual-Max configuration, I’ll have that as well!) This means that, as on the MacBook Pro, the M1 Pro models will be configurable up to 32GB of RAM, and the M1 Max models will reach up to 64GB. Yes, please.
A better power brick. I assume the new iMac will have the same power brick as the 24-inch model does, complete with an Ethernet jack. That’s a great feature, but speaking as someone who has a USB hub velcroed to the bottom of his desk, I’d love it if Apple also offered a brick with additional USB ports. I doubt that it will, but what’s the harm in asking?
A better display. I don’t know if Apple is ready to ship a 27- or 30-inch micro-LED display, but I’d love one. The display on the new MacBook Pro models is something to behold. I’d love that same high-dynamic-range display in a big iMac. (And while we’re at it, Apple, don’t forget to keep the glare-resistant nanotexture coating option that you currently offer on the high-end Intel iMacs.)
Nice colors. I don’t expect that Apple will release larger iMacs in the same bright colors as the 24-inch models. These are likely to be expensive iMacs—probably with “Pro” in the name—and if the iPhone has taught us anything, it’s that professional products don’t come in bright, bold colors. I’ll take a dark blue or dark green iMac, though, if that’s all the choice that’s open to me. I’d just rather not be stuck with Space Gray again if I could help it.
Announced March 8, orders March 11, shipping March 18. This is my list, and like I said, I’m tired of waiting. Let’s make it happen, Apple.
Each year when Apple’s WWDC wraps up, I find myself doing what a lot of app developers do: planning my response to the upcoming version of iOS. But my summers aren’t consumed by Xcode or SwiftUI. My annual contribution to the Apple economy is a book called iOS Access for All: Your Comprehensive Guide to Accessibility for iPad, iPhone and iPod Touch. You think that title’s long? The iOS 15 edition weighs in at 215,000 words, 11 chapters, and four appendices—all written, assembled and sold by me.
Realizing I’d just published the book’s ninth edition got me thinking about how this all happened, and the extent to which I’ve managed to streamline many parts of the publishing process, while hopefully living up to the expectations of a group of readers who don’t get much attention from other iOS books and overviews.
Beginnings
Before I focused on iOS or accessibility, I wrote books about the Mac, web development, and wireless networking. I worked with book publishers whose end products were heavy, paper volumes you could find on a bookstore shelf. Even in 2012, when I first had an idea for a book about accessibility on Apple platforms, I knew the publishing model I had worked under for 10 years or so had changed dramatically. Who needs Mac Answers when you have Google?
I learned soon after iOS became accessible in 2009 that good search craft can’t find what isn’t online. Lots of knowledge about how to use Apple’s accessibility tools was ephemeral. And what was available quickly went out of date with no one having the incentives or a mandate to fix it.
I decided there should be a book about iOS accessibility, written by an experienced tech author. So, as you do, I pitched some publishers. But despite my track record and an opportunity to own a corner of the market, the answer was no. These publishers didn’t think they could sell enough copies of a book focused solely on accessibility.
It’s possible they were entirely right. But as I started embedding myself into the accessibility community, I became aware that publishers really didn’t know who might want the book I planned to write, or how to sell it to them. At least I had the advantage of being a daily user of some of what I planned to write about. I learned a lot by listening – over coffee and on Twitter – to people who make and use accessible tech every day. They reinforced in me the need to make the book, even if I couldn’t yet prove a market existed.
Self-publishing
The other thing you need to know about my plan to publish a book on my own is that I was on a budget. I would need to spend as little money as possible while still doing a professional job. I was a freelancer planning to devote months of full-time work to this endeavor. And I knew I would need to pay for things like a cover design and a copy editor. I also gave myself a travel budget, but not one for software.
At the last couple of Macworld Expos, I sat in on ebook publishing sessions, where I learned the gospel of ePub as a flexible online format that Apple was already using in what was then the iBooks Store. And from accessibility experts, I learned that it was an important part of special-purpose devices that turn text into audio for blind users.
Coming into the 2013 iOS release cycle, I had a topic, a format and publishing strategy, and a foothold in a community I would need to sell the book.
Maximum Accessibility
A major advantage of ebooks over paper ones is that they’re accessible on devices, where screen readers and text visibility options break down the barriers between readers and content. And you’ll find free ePub readers on all platforms.
As a book builder, ePub turned out to be a great choice, There are lots ways you can build a good-looking ePub. Structurally, an ePub is just a bunch of XHTML files, images, CSS, and a manifest, all zipped together.
A brief flirtation with Pages taught me that using an app that was easy to write in would not yield the book I wanted. (Pages support for ePub improved considerably once Apple discontinued iBooks Author, but it’s still not beefy enough for my needs.) Nor did I choose the popular Scrivener, or the expensive inDesign, both of which will export fine ePubs, and in which many of my writer friends have boundless faith. Ditto Calibre and Sigil, which at least appealed to my desire to think of the book as a giant ball of text.
BBEdit in action, displaying the book’s source code in a project window.
The way I published the iOS 7 version of the book and the way I do it today are remarkably similar. I work in BBEdit on the Mac, and Textastic on the iPad, then I run ancient AppleScripts that verify the book against the ePub specification, and finally put the files together as a book. Building my book this way is a little like compiling a program. A big part of the editing process is debugging it.
Learning to Ask for the Sale
To promote the book, I became a regular at accessibility tech conferences, bought party sponsorships and tables on trade show floors (these were less costly than they might sound). I even had gimmicks, like business cards with QR code stickers on the back that were easy to scan, even if you couldn’t see them.
I used Twitter extensively, and embarked on a podcast book tour – going on any show that would have me to hawk the book. And you know what? People did have me on their shows – there seemed to be real enthusiasm for what I had made.
Acquired Wisdom
Every couple of years I re-examine my publishing process. I’ve made refinements, like adding shortcuts that help me frame and size screenshots. And because there’s demand for a PDF version, I now build an accessible one based on a Microsoft Word template.
At this point, iOS and the book itself are mature propositions. Like the rest of the software, the accessibility tools in iOS have gained incremental updates each year, but the fundamentals remain, meaning not everyone needs either a new phone or a new book each year.
But people do keep buying it and telling me how valuable it has been to them. So chances are pretty good there will be a tenth edition sometime late this fall.
If we know anything about iOS as a platform, it’s that if you want to run apps on it, you need to download them from the App Store. (If you missed it, it turns out that this decision continues to be controversial!) The iPhone and iPad have never been platforms defined by a combination of Apple-approved apps and third-party apps from random sources.
But what if that’s what iOS was to become? Certainly, as legislators and regulators circle around Apple and its practices, it’s possible that someone will force Apple to allow apps onto the platform without them going through the App Store.
It’s almost unimaginable. And yet… what if that calamity ended up being the best thing for the App Store, and improved it–and the base iOS experience–for most users?
Everyone has a thing in their life long overdue for a change. It might be a piece of clothing that you’re convinced still looks good on you or that pickup line that’s more sleaze than smooth. For macOS, it needs to admit that settings… I mean… System Preferences is long (LONG!) overdue for an overhaul. Like insisting, against all evidence, that your favourite pair of jeans still fit, it’s time to face the fact that you’ve outgrown what you’ve got and move on.
This is one of the oldest-feeling corners of macOS. It is long past time for a complete rethink. And I like the look of this proposal.
Last in, first out? John Gruber, who was the final person to enter the Six Colors Report Card (to be fair, there were four stragglers who popped in at the very last moment), has published his full responses:
I appreciate everyone who submits to the survey, but especially appreciate those who take their comments and turn them into posts on their own sites later!
I subscribe to a lot of streaming video services, and that means I use a lot of streaming video apps. Most of them fall short of my expectations. Here, then, is a simple specification for a streaming video app. Follow it, and your app will be well on its way to not sucking.
This spec includes only the basics. It leaves plenty of room for apps to differentiate themselves by surprising and delighting their users with clever features not listed here. But to all the streaming app developers out there, please consider covering these fundamentals before working on your Unique Selling Proposition.
John’s list is really solid. I quibble about a couple of the things he’s looking for, but can’t argue with most of them: there’s nothing more frustrating than an app that gets in your way, especially when you’re trying to do something as simple as watch an episode of TV.
My personal addition to this list is better recognition of when you’ve finished an episode (I’m sorry, I’m not always going to watch all five minutes of credits—you should be able to figure that out).
Apple’s newer video player UI, rolled out in tvOS 15, has become adopted by more and more apps, and it’s really pretty good. Frankly, I wish all players used this framework because then I wouldn’t have to figure out where the features are in every different player.1 This would be like if every television channel had its own slightly different interface.
There are a lot of bad UI experiences in video streaming apps, but Peacock might be the worst on the Apple TV. Getting to the controls is a pain and I’ve never figured out how to make the “jump back 10 seconds” command work correctly. ↩
