Apple Confirms Liquid Glass Is Here to Stay — And That's a Design Crime Against 2 Billion Users

Let me paint you a picture. It's March 2026. You're squinting at your iPhone in the sun, trying to read a notification through layers of translucent, shimmering, blob-shaped UI elements that Apple insists look gorgeous. You can't quite make out whether that message is from your boss or your dentist, because the text is fighting for contrast against a background that looks like someone smeared Vaseline on a glass table.

Welcome to the Liquid Glass experience. And according to Bloomberg's Mark Gurman, it's not going anywhere.

In his Power On newsletter published yesterday, Gurman dropped what should be a bombshell for anyone who cares about usable software: the internal builds of iOS 27 and macOS 27 "don't reflect major design changes." Liquid Glass, the controversial UI overhaul that Apple introduced with iOS 26 at WWDC 2025, is getting tweaked at the margins but fundamentally staying put. The company's plan? "Years of gradual improvements."

Years. Plural.

That's not a design roadmap. That's a hostage situation.

How We Got Here

To understand why this matters, you need to rewind to June 2025. Apple unveiled Liquid Glass as a system-wide design language inspired by visionOS — the operating system built for a $3,500 headset that most people have never used. The idea was to unify the visual language across iPhone, iPad, Mac, Apple Watch, and Vision Pro with translucent, depth-aware surfaces that shift and morph as you interact with them.

On stage, it looked stunning. In the real world, it was a disaster.

Within weeks of the iOS 26 beta landing on devices, the complaints started rolling in. Readability was tanked. Navigation bars blurred into backgrounds. App icons became harder to distinguish. Accessibility advocates raised alarms about contrast ratios that failed WCAG guidelines. Power users found themselves lost in interfaces they'd navigated for a decade.

Apple's response was telling: rather than reconsider the direction, they started bolting on escape hatches. iOS 26.1 brought a "Tinted" mode to reduce transparency. iOS 26.4 added a toggle to disable Liquid Glass highlights entirely. Each update was essentially Apple saying, "Fine, here's a way to turn off the thing we told you was the future."

And now, with iOS 27 on the horizon, the best we might get is a systemwide slider to control how much glass effect you see. Gurman says Apple had been working on this during iOS 26 development but "ran into engineering challenges" extending it beyond the lock screen clock.

Let that sink in. Apple — a company worth north of $3 trillion, with the largest software engineering workforce in consumer tech — couldn't figure out how to make a transparency slider work across their own operating system. In a year. That's either an engineering problem of staggering complexity or a company that didn't prioritize fixing what users actually hate.

I'll let you guess which one.

The Alan Dye Factor

Here's where the story gets interesting. Alan Dye, the design VP who was largely responsible for Liquid Glass's direction, left Apple in late 2025. He didn't just leave — he went to Meta, which is about as loud a statement as you can make in Silicon Valley. His replacement, Steve Lemay, now inherits a design language that's already baked into every Apple platform.

Many observers hoped that new design leadership would signal a course correction. Gurman's report dashes that hope entirely. And honestly, it makes sense — not because Liquid Glass is good, but because of how Apple works.

Apple doesn't reverse course. Not quickly, not publicly, not without years of internal deliberation. The butterfly keyboard lasted four generations of MacBook Pro before Apple admitted it was a problem. The Touch Bar hung around for five years. The trash can Mac Pro was Apple's "professional" offering for six years before they acknowledged it was a dead end.

Liquid Glass is on the same trajectory. Apple invested years developing it — first for visionOS, then adapting it system-wide. The sunk cost isn't just financial; it's ideological. To reverse course now would be to admit that the most visible design change since iOS 7's flat design revolution was a mistake. Apple's institutional ego won't allow that, at least not on any timeline that helps current users.

The Usability Tax

Let's talk about what Liquid Glass actually costs users, because this isn't just an aesthetic debate.

Readability. The fundamental purpose of a user interface is to communicate information. Liquid Glass actively undermines this by placing translucent, light-refracting surfaces behind text and interactive elements. In well-lit environments — say, outdoors on a sunny day — the contrast reduction is measurable and meaningful. This isn't subjective. This is cognitive load imposed by a design choice that prioritizes visual novelty over information clarity.

Navigation. Liquid Glass elements morph and shift based on context, scroll position, and background content. This means the visual affordances that help you understand where you are in an app are constantly changing. For experienced users, this creates friction. For elderly users, users with cognitive disabilities, or anyone who doesn't use their phone with the intensity of a tech reviewer, it creates genuine confusion.

Battery. Rendering translucent, depth-aware surfaces in real time is computationally expensive. Apple's newer chips handle it fine, but on older supported devices — which Apple deliberately keeps on the compatibility list to tout their longevity — Liquid Glass is a battery tax. The GPU cycles spent making your Settings app look like a jellyfish could be spent on, you know, keeping your phone alive until dinner.

Consistency. Third-party developers have been scrambling to adapt to Liquid Glass since iOS 26 landed, and the results range from "acceptable" to "what happened here." Apple's own apps look cohesive because they had years of advance notice. Everyone else is still catching up, and many smaller developers have simply given up trying to match Apple's visual language, resulting in apps that look jarring and out of place.

The Slider Isn't Enough

Gurman's report hints that Apple might finally ship a systemwide transparency slider in iOS 27. Let's be generous and assume they pull it off. Is that good enough?

No. And here's why.

A slider is Apple admitting the design has a problem while refusing to solve it. It's a punt to the user. Instead of making design decisions — which is literally what a design team exists to do — Apple is saying, "Here, you figure out how translucent you want your phone to be."

This is the same company that Steve Jobs famously said should make decisions for users because users don't know what they want. Now they're shipping a slider because they can't decide how much glass is too much glass.

More importantly, a slider doesn't fix the fundamental architectural problem with Liquid Glass. The design language assumes that translucency and depth are inherently desirable across every context: messaging, email, settings, photo editing, health data, banking. That assumption is wrong. Some interfaces need to be crystal clear and information-dense. Others can afford to be playful and expressive. A single systemwide slider treats all contexts the same way, which is exactly the kind of one-size-fits-all thinking that created the problem.

What Apple should be doing is what they actually did well with the original iOS 7 transition: commit to a clear design philosophy, execute it with rigor, and iterate ruthlessly based on real-world feedback. Instead, they've committed to Liquid Glass aesthetically while retreating from it functionally through toggles and sliders. That's not design. That's indecision with a nice gradient.

The Competition Isn't Standing Still

While Apple fiddles with transparency sliders, the rest of the industry is moving in a completely different direction. Google's Material You has matured into a design system that's genuinely adaptive — it responds to user preferences, content context, and accessibility needs without requiring manual tweaking. Samsung's One UI 8 doubled down on readability and information density, acknowledging that most people use their phones to do things, not to admire their phones.

Even Microsoft, not exactly known for design leadership, has been iterating on Windows 11's Fluent Design with practical improvements to contrast, typography, and layout density. The irony is rich: Microsoft is shipping more readable transparent effects than Apple.

Android's design trajectory feels focused on making interfaces work better. Apple's feels focused on making interfaces look different. There's a chasm between those two goals, and Liquid Glass sits squarely in it.

What Should Apple Actually Do?

Here's what I'd love to see, knowing full well it won't happen:

1. Make Liquid Glass contextual. Let it shine on the home screen, lock screen, and entertainment apps where visual flair adds to the experience. Strip it back to clean, high-contrast surfaces in productivity apps, communication interfaces, and accessibility-critical contexts.

2. Set real accessibility targets. Commit publicly to WCAG AA contrast ratios across all default UI states, not just when users enable accessibility modes. The default experience should be accessible. Full stop.

3. Give developers real guidance. Apple's Human Interface Guidelines for Liquid Glass are vague to the point of uselessness. Third-party developers need concrete specifications, not mood boards.

4. Accept the L on the timeline. If it takes "years of gradual improvements" to make Liquid Glass work properly, then Liquid Glass wasn't ready to ship. Saying the quiet part out loud would earn Apple more goodwill than any number of Settings toggles.

The Bigger Picture

Liquid Glass isn't just a design problem. It's a symptom of Apple's current creative crisis.

For decades, Apple's design decisions were driven by a clear vision that prioritized usability alongside beauty. The original iPhone interface wasn't just attractive — it was intuitive in a way that made people gasp. The flat design of iOS 7 was polarizing, but it was also functional: it made interfaces faster to parse and easier to navigate. Even the notch, which everyone mocked, was an honest engineering trade-off that Apple didn't try to hide.

Liquid Glass breaks that tradition. It's a design language that came from a product most people don't own (Vision Pro), imposed on products everyone uses (iPhone, iPad, Mac), without adequate consideration for whether it actually makes those products better. It's design leadership by aspiration rather than observation — Apple designed for the reality they wanted (spatial computing everywhere) rather than the reality they have (2 billion people using flat screens in varied lighting conditions).

The confirmation that iOS 27 won't meaningfully change direction is disappointing but unsurprising. Apple has chosen its path. The rest of us — all two billion of us — will squint through the glass until they decide, years from now, that maybe readability matters after all.

In the meantime, I'll be in Settings, looking for that slider.