Apple Liquid Glass Design: When Innovation Ignores the User

When Apple unveiled iOS 26 at WWDC 2025, the reaction in the design community landed somewhere between confused and genuinely alarmed. I remember watching the keynote and waiting for the moment where Craig Federighi would wink at the camera and admit the whole thing was a joke. He did not. What followed was a real product decision from one of the most resourced design organizations on the planet — and it promptly broke the internet, not in the good way.

Liquid Glass is Apple’s new visual language for iOS 26. Apple describes it as a translucent material that reflects and refracts its surroundings, dynamically transforming to help bring greater focus to content. That is the marketing copy. In practice, what you get is an interface that shimmers, wiggles, and refuses to stay out of the way of the content it is supposedly serving.

Let’s talk about what went wrong, why it matters, and what it tells us about a company that has spent decades telling us it takes design seriously.

What Is Liquid Glass, Exactly

At the surface level — and the surface is all it really has — Liquid Glass replaces iOS’s traditional opaque interface elements with translucent, animated layers. Tab bars bubble. Buttons pulsate. The status bar floats over your content. Icons shimmer. Navigation elements appear and disappear depending on context. It is, as one widely shared description put it, as though your phone were encased in Jell-O.

Apple’s VP of Human Interface, Alan Dye, framed it as taking advantage of advances in hardware, silicon, and graphics technologies to lay the foundation for the next chapter of software design. That framing is important, because it tells you Apple views Liquid Glass not as an experiment but as a direction. This is where they intend to go.

What makes that framing even richer in retrospect is what happened next: in December 2025, Meta poached Dye away from Apple, hiring him as chief design officer to lead a new creative studio focused on AI-equipped consumer devices. So the architect of Liquid Glass — the person who stood on stage at WWDC and called it the foundation of the next chapter of software design — promptly left for a company not exactly celebrated for its UX elegance. The sentiment within Apple’s own ranks was telling: people described the news as almost too good to be true, having given up hope that Dye would ever be moved out. That is not the portrait of a visionary who pulled off a bold but misunderstood masterstroke. That is the portrait of someone whose departure was quietly celebrated by the team that had to ship his ideas.

And Apple’s response to the Liquid Glass backlash? A masterclass in the “let them eat cake” school of product management. The company has rolled out micro-concessions — a transparency toggle buried in Display settings, a tint option with exactly zero customization, and a Reduce Motion flag that has been in accessibility settings for years and exists precisely because motion-heavy interfaces cause real harm to real users. iOS 26.1 introduced a new Liquid Glass setting under Display and Brightness with two options: Clear or Tinted. For iPad users who struggle with overlapping screen elements, this change makes very little practical difference. A transparency control for the clock. Just the clock. The message is clear: Apple heard you, noted your concerns, and decided you were wrong. Your eyes are just not seeing right. Rather than revisiting the core design decisions that produced the problem, the company offered the equivalent of turning down the volume on a fire alarm. The alarm is still going off. Your eyes still hurt. But now there is a setting for it.

The Research Apple Decided to Skip

The Nielsen Norman Group, the most cited authority in UX research, published a thorough takedown of Liquid Glass in October 2025. The headline: iOS 26’s visual language obscures content instead of letting it take the spotlight, and new design patterns replace established conventions without improving on them.

Let’s go through the specific ways Liquid Glass ignores decades of accumulated evidence:

Transparency and Contrast

One of the oldest findings in usability is that anything placed on top of something else becomes harder to see. Yet Apple is now proudly obscuring text, icons, and controls by making them transparent and placing them on top of busy backgrounds. This is not a new finding. It has been validated repeatedly since the early days of GUI research. Apple’s own Human Interface Guidelines have historically warned against low-contrast interfaces. Liquid Glass contradicts that body of work directly.

Independent beta testing from the design firm Infinum found something even more damning: some screens fall well below WCAG minimum contrast levels — as low as 1.5:1 in places, against a required minimum of 4.5:1. That is not a small miss. That is a failure to meet the foundational accessibility standard that the web has operated under for years.

Motion and Cognitive Load

Animation can be delightful the first time. But delight turns into distraction on the tenth, twentieth, or hundredth time. In iOS 26, controls insist on animating themselves, whether or not the user benefits. Carousel dots morph into search bars. Tabs shimmer when switched. Buttons pulsate when tapped. It is like the interface is shouting “look at me” when it should quietly step aside and let the real star — the content — take the spotlight.

Tap Targets and Touch Ergonomics

The long-standing guideline of at least 0.4cm between targets and 1cm x 1cm tap areas seems to have been tossed out the window. In iOS 26, tab bars feel cramped, squeezed to accommodate a persistent search button in the bottom-right corner of nearly every page.

Predictability and Learned Behavior

This is where Liquid Glass does its most significant damage. Back in the day, Microsoft Office experimented with adaptive menus that reordered themselves based on recency. People hated them because nothing stayed where you left it. Apple seems to have learned nothing from that lesson. In iOS 26, controls appear, vanish, collapse, and expand depending on context. Users had developed reliable habits. Liquid Glass dismantled them.

Good UX Should Not Be Controversial

There is a useful litmus test for any design decision: does it need to be explained? Good UX is self-evident. A well-placed button, a clear hierarchy, an obvious action — none of these require a press release or a developer keynote to justify.

Liquid Glass required both, and still generated 29 pages of complaints in a single Apple Community thread.

The user backlash centers on a fundamental tension: what looks impressive in marketing materials often becomes exhausting in daily use. That tension is not a bug in user perception. It is the definition of form over function. When a design system impresses on a stage and frustrates in a pocket, the design has failed its primary obligation.

Early adoption data told what looked like a damning story — until the numbers clarified under further research. Initial reports citing StatCounter and MacRumors visitor stats claimed only around 15-25% of iPhones were running iOS 26 months after launch, versus 89% on iOS 18 at the same point the prior year. Those numbers spread fast across the tech press. MacRumors later issued a correction, acknowledging the conclusions were incorrect due to Apple’s change in how Safari reports itself in iOS 26. Starting with Safari 26, Apple changed its user agent string so it no longer lists the current version of the operating system — meaning analytics services were counting iOS 26 devices as still running iOS 18. StatCounter’s CEO confirmed the miscounting publicly.

The real picture, once corrected sources were consulted, points to a roughly 20-point drop in adoption compared to prior years — significant, but nowhere near the collapse originally reported. That still matters. Users are holding off on upgrading at a measurably higher rate than in previous iOS cycles, and the reason consistently cited across analysis is Liquid Glass. You do not have to fabricate a disaster to make the case that something went wrong. The real numbers are sufficient.

The Accessibility Failure

The accessibility implications of Liquid Glass are not a side issue. They are a core indictment of the design process that produced it.

AppleVis, an advocacy organization for blind, DeafBlind, and low vision users of Apple products, released its 2025 Apple Vision Accessibility Report Card. Apple’s cumulative rating dropped 0.2 points to 3.7, with the organization noting that Liquid Glass had a significant negative impact on the user experience for many low vision users.

One contributor who works for a charity supporting blind people described Liquid Glass as a serious accessibility issue, not just an aesthetic one — and characterized it as a significant failure against Apple’s usual standard of excellence in this area.

The workaround? Bury yourself in Settings > Accessibility and toggle Reduce Transparency, Increase Contrast, and Reduce Motion — all of which should be unnecessary for a flagship OS update from a company with a dedicated accessibility team.

Beyond readability, Liquid Glass introduces performance degradation and battery drain, particularly on older devices. iPhone 13 Mini users reported batteries dying before the end of the workday, and Apple Watch Series 10 users noted significant frame rate drops with every Liquid Glass animation. Accessibility via hardware attrition is not a strategy.

It Gets Worse on a Mac

If Liquid Glass on iPhone is a frustration, on macOS Tahoe 26 it is something closer to an abomination. The design language Apple debuted on iOS did not stay on iOS — it rolled across the entire platform ecosystem, landing on the Mac with noticeably less grace. The Six Colors annual report card, a respected industry survey of Apple writers, editors, and developers, noted that while iOS was generally considered the place where Liquid Glass caused the least damage, the macOS Tahoe implementation was judged the harshest of any platform. That is not a compliment to iOS. It is an indictment of what Liquid Glass does when it lands on a productivity-focused desktop OS that professionals depend on daily.

The problems are structural. On a phone, you are mostly consuming content and tapping through flows. On a Mac, you are working. You are scanning sidebars, toggling settings, reading dense text in apps, and moving through complex workflows at speed. Liquid Glass actively interferes with all of that. Scroll through the System Settings sidebar and watch as sidebar items bleed directly over the search box, rendering text in both elements unreadable at the same time. Enable a settings toggle and it literally jumps off the screen — an animated leap that pulls your eye away from whatever you were trying to do next. It is indulgent overengineering where measured restraint was the only appropriate choice.

And then there are the corners. MacOS Tahoe introduced window corners so aggressively rounded they would look more at home on a Fisher-Price toy than a professional workstation — a visual choice that manages to feel both childish and condescending at the same time.

Users who have relied on macOS for serious work found themselves dealing with something that, in the words of one longtime Mac writer, increasingly felt like a half-baked product held together with a shaky combination of duct tape and wishful thinking. Another common thread in feedback: window backgrounds in Light Mode are now pushed to 100% white, stripping out the tonal variation that made content easy to parse. Entire menus and window titles render completely illegible in everyday, non-contrived situations. Not edge cases. Normal use.

And the bugs arrived with the design. Users reported that the Reduce Transparency accessibility setting — the same workaround Apple pointed to on iOS — lost its effectiveness in macOS 26.1 and was not meaningfully addressed in 26.2. The fix broke the fix. One developer put it plainly: “I can’t even tell what’s a UI bug and what’s working as intended, because all of it just looks wrong.” When your users cannot distinguish intentional design choices from software defects, something has gone badly off the rails.

John Gruber, one of the most prominent voices in the Apple commentary community, declined to install macOS Tahoe at all, writing that it was so much worse than macOS Sequoia that it crossed a line he was not willing to cross. That is a significant statement from someone who has covered Apple through every major transition of the past two decades. It is not a reaction to change — it is a reaction to the specific quality of this change.

This Is a Pattern, Not an Accident

What makes Liquid Glass most frustrating is that we have been here before. A similar situation unfolded when Apple introduced its last major UI overhaul with iOS 7, which launched with terribly thin typefaces. iOS 8 and 9 dialed back the thinness to help with accessibility. Users expected Apple to have learned that lesson.

They did not.

Apple’s response to the Liquid Glass backlash followed a familiar script: push forward, offer buried workarounds, wait for users to adapt. Apple positions Liquid Glass as its “next decade” interface direction, treating current complaints as growing pains rather than design failures. That posture is worth examining, because it reveals something about how Apple weighs user feedback against internal conviction.

This is a company with extraordinary design resources, proprietary research capabilities, and a direct relationship with hundreds of millions of users. The fact that basic contrast failures, tap target violations, and motion-triggered discomfort made it to a public release is not the result of oversight. It is the result of a culture that, at times, values the vision of its design leadership more than it values the people using its products.

That is a form of arrogance that no amount of hardware achievement should excuse.

A Call to Apple Support, and a Telling Admission

I called Apple support recently — a completely unrelated issue — and at the end of the call, almost as an afterthought, I asked the rep when a Liquid Glass kill switch was coming. I was not serious, obviously. Apple has too much institutional pride to ever frame a retreat as a retreat. But his response stuck with me. Without missing a beat, he said he didn’t like it either.

Not a hedge. Not corporate-speak. Just a guy who works at Apple, on Apple support, using Apple products every day, telling a customer he agreed with them.

That is the part Apple’s leadership should sit with. It is one thing when the design community piles on. It is another when your own people — the ones answering the phones, representing the brand, selling the experience — quietly nod along when someone asks if the new interface is any good.

So, Alan Dye: I genuinely hope you bring the same design instincts to Meta that you brought to Apple. They deserve each other. And in the meantime — long live Sequoia.

The Bottom Line

Liquid Glass is not just a design misstep. It is a case study in what happens when aesthetic ambition is decoupled from data supported user-centered design. The research exists. The guidelines exist. Apple wrote many of them.

Good UX does not announce itself. It gets out of the way. It makes the next action obvious, the content readable, and the experience predictable. It does not wiggle when you tap it. It does not camouflage your friend’s message against a photo of their dog. And it does not require users to dig into accessibility settings just to use their phone without eye strain.

Apple is capable of better. The fact that they shipped this anyway is the part worth talking about.

---