I liked the angry website Bugs Apple Loves because it’s hitting on something that got me worried in recent months: Apple has been bad at bugs for a while now, but we might be overfocusing on giving them crap solely for some of the most visible – even visual – Tahoe stuff.

This is a condensed list at the time of writing, as the site itself doesn’t make it easy to see it:

• Mail search doesn’t work
• Autocorrect won’t take no for an answer
• Apple Pay: card icon changes address
• Google Contacts sync is a black hole
• AirDrop: Looking for devices...
• iCloud Photos: ‘Uploading X Items’
• Spotlight: ‘Indexing...’
• Personal hotspot won’t auto-connect
• Apple Watch widgets won’t let go
• iOS text selection is pure chaos
• AirDrop shuffles targets mid-tap
• macOS 26 window resizing doesn’t work

There are themes here: “the interface doesn’t remember my preference,” and “things move around as I interact with them,” and “some process gets clogged up,” and “a thing gets stuck and doesn’t respond to interface actions.”

What I appreciate about this is that none of this is very “visible” stuff, but the insidious things that add up and bother on the daily basis, chipping away at your flow first and sanity second – which the site tries to quantify via a formula:

I think this is really interesting, even as a satire.

I found it’s really hard, if not impossible, to justify design or experience bugs using the same frameworks as other engineering bugs. As Mike Swanson wrote: “You cannot easily measure the resentment. Or the rage clicks when they smash a button to dismiss another […] pop-up.”

A lot of it is utterly subjective. Various small frustrations add up in non-linear ways. A lot of it doesn’t subscribe to binary “data loss or not” or “does it function or not” classifications. A lot of it feels heavy to fix in terms of context switching, so it’s timeboxed and then discarded when the time box overflows.

I have seen engineers say “Oh, it’s a long-standing bug, it’s been like this for 3 months” as a justification to deprioritize something, while to me it feels like that should be an accelerant. The users have already been suffering for 3 months!

So maybe metrics like these could actually help? Quantifying at least the blast radius (affected users + usage per day) seems valuable, not to mention the embarrassment of seeing something like “9.1 years unfixed by Apple.” (And yes, internal embarrassment and shame should also be a metric.)

This would be harder to do for creators of the site, but easier inside Apple: I would also try to quantify vocal user frustration. One of my tricks when thinking about bugs has been “Notice when your users are really angry about invisible stuff.”

…for example someone going on and on about Finder.