I really enjoyed Nick Heer’s review of iOS and macOS 26. I wish I wrote something as thoughtful; after my summer spent fighting Safari’s new design, I had a lot to say, but I never wrote it down.

The whole thing is worth reading, but I’ll highlight one section I particularly enjoyed. Nick writes about macOS here, but there are many apps in iOS and iPadOS where this same critique could be levied, including Safari. (The emphasis below is mine.)

The way toolbars and their buttons are displayed on MacOS is, at best, something to get used to, though I have tried and failed. Where there was once a solid area for tools has, in many apps, become a gradient with floating buttons. The gradient is both a fill and a progressive blur, which I think is unattractive.

This area is not very tall, which means a significant amount of the document encroaches into its lower half. In light mode, the background of a toolbar is white. The backgrounds of toolbar buttons are also white. Buttons are differentiated by nothing more than a diffuse shadow… the sum of this design language is the continued reduction of contrast in user interface elements to, I think, its detriment.

Apple justifies these decisions by saying its redesigned interfaces are bringing greater focus to content”. I do not accept that explanation. Instead of placing tools in a distinct and separated area, they bleed into your document, thus gaining a similar level of importance as the document itself. … in my experience, the more the interface blends with what I am looking at, the less capable I am of ignoring it. Clarity and structure are sacrificed for the illusion of simplicity offered by a monochromatic haze of an interface.

Even if I bought that argument, I do not understand why it makes sense to make an application’s tools visually recede. While I am sometimes merely viewing a document, I am very often trying to do something to it. I want the most common actions I can take to be immediately obvious.

The passage I emphasized is the very same problem I have with the design, particularly as a designer. When the tools of the OS bleed into my document, particularly when designing a website, my design has to accommodate Apple’s UI, and that deeply frustrates me. 

But Nick also writes about something else vexing. Tools are now hidden in junk drawers, and often more difficult to find. Apple’s software is great graphic design, but it is becoming frustrating interface design. These are different practices, with different goals. Graphic design is intended to draw attention, often for the sake of branding or advertising. Interface design is not unlike designing a hammer: it is the practice of making a tool useful and usable. For Apple’s software to be a great piece of graphic design, but not a great interface design, is a dramatic failure of purpose.

Nick also asks why Apple feels the need to do this now:

Why is this the first time all of the operating systems are marketed with the same version number? And why did Apple decide this was the right time to make a dedicated operating system” section on its website to show how it delivers a more consistent experience” between devices? I have no evidence Apple would want to unify under some kind of Apple OS” branding, but if Apple did want to make such a change, this feels like a very Apple‑y way to soft-launch it. After all, your devices already run specific versions of Safari and Siri without them needing to be called Mac Safari” and Watch Siri”. Just throwing that thought into the wind.

Stop giving them ideas, Nick.

Apple has worked to unify their designs for years, despite the cries from the design community that this is a fruitless idea. Large, multi-window operating systems like the Mac (and now the iPad) naturally demand different interfaces than a modal OS running in a device you hold in your hand. I don’t know why they did this now. I like Craig Hockenberry’s thoughts on this, where he posits that this all might be in preparation for a foldable phone, but I question anybody who thinks Apple plans that far ahead. I think Apple looks 12 – 24 months out at a time, like most organizations I’ve worked with. 

What I’ve pieced together from years of rumours is that Apple started this redesign process shortly after Ive departed. There was a rumour years ago that Apple was working on a design that embraced neumorphism,” which is a word I never hoped to have to spell. 

What Apple ended up with isn’t exactly — look, don’t ask me to spell it again. But it’s not far off. Listen to the criticism of neumorphism, directly quoted from the Wikipedia page:

Neumorphism has received criticism from UI designers, notably for its lack of accessibility, difficulty in implementation, low contrast, and incompatibility with certain brands.

That sounds about like where we’re at to me. From Wikipedia’s Liquid Glass entry:

However, other users noted that certain elements were too transparent, making text difficult to read in low-contrast environments, such as direct sunlight. Designers interviewed by Wired felt that the visual effects distracted from app content. One designer said developers with smaller teams might struggle to meet the high visual standards set by the new interface.

Neumorphism and Liquid Glass are by no means identical, but one could argue they share the same etymology. Based on when neumorphism was trending (2022 and 2023), I’d wager they’ve been working on Liquid Glass for two years. I’d also wager they might have waited another year to ship this redesign, if it weren’t for the disaster that Apple Intelligence was for the company last year. They needed a win.

If Apple was working on this for at least two years, and it involved redesigning everything (including macOS), I’m not convinced it was for a foldable phone. I’m also unconvinced their plan is to make one unified operating system. If I worked at Apple, the major selling point of a cohesive design is a manageable component library. Every large platform I’ve worked on is obsessed with minimizing components across all their apps. Apple makes a lot of operating systems and need to avoid both design and engineering complexity. It is easiest to share parts where they can. 

I don’t think they have a plan. While a unified design library makes sense to me as a design practitioner, I am not certain it works in practice (particularly on macOS). As far as asthetics, I think Apple thinks design is partially fashion, and that they need to be a forward-thinking fashion house. They are not wrong. But is OS 26 forward-thinking or merely a façade? I suspect the latter, but only time will tell.