Liquid Glass: One Year In. What It Actually Means for Your SaaS UI
Apple's Liquid Glass shipped across 6 platforms in June 2025. One year on: what actually changed, what filtered to the web, and what your SaaS team should do about it.
On 9 June 2025, Apple walked onto the stage at WWDC and unveiled Liquid Glass — a new material system rolling out across iOS 26, iPadOS 26, macOS Tahoe, tvOS 26, visionOS 26, and watchOS 26 simultaneously. By Apple's own description, it was the most extensive software design update the company had ever shipped. The design community's reaction was immediate, vocal, and divided.
A year later, the noise has settled into something more useful: a clear picture of what actually happened, what filtered through to the web and SaaS world, and what your team should actually do about it. That is what this piece covers.
What Liquid Glass actually is, and what makes it different
The name is precise in a way that matters. Liquid Glass is not an aesthetic trend. It is a material — a real-time rendering system that produces translucent, refractive surfaces which dynamically respond to the content behind them, the ambient light conditions, and the movement of the device. Controls float as a distinct functional layer above apps, collapsing and expanding as the interface demands. Specular highlights react to scroll. The whole system is hardware-backed by Apple Silicon.
Liquid Glass vs Glassmorphism
Glassmorphism, named by designer Michal Malewicz and popularised on Figma and Behance from 2020 to 2021, was a visual treatment: blur the background, apply a frosted transparent layer, suggest depth. Liquid Glass is a reactive material system: surfaces refract and reflect their surroundings in real time, responding to context and movement. You can apply glassmorphism with a CSS filter. Liquid Glass is Apple's rendering engine, not a style sheet.
The scope was also unprecedented. Every Apple platform received the same material system simultaneously — the result of a decade of progressively converging OS experiences that made a unified design language possible for the first time.
The historical playbook: what happens when Apple changes design language
Every major Apple design overhaul follows the same arc. Understanding it is more useful than reacting to the announcement.
iOS 7 in 2013 replaced skeuomorphic design with flat, minimal UI. Leather textures, felt backgrounds, and wooden shelves disappeared overnight. The design community initially recoiled, then adopted, then overcorrected into a decade of grey minimalism that drained personality from most of the web. Flat design did not fully settle into sensible defaults until around 2022.
macOS Big Sur in 2020 brought translucency back. Designers on Dribbble and Figma immediately ran with glassmorphism — every UI concept on the internet had a frosted glass panel for the next 18 months. Then the predictable backlash: accessibility failures, readability problems, the same effect applied to every surface regardless of whether it helped. By 2023, glassmorphism had matured from trend to tool. Something to use deliberately, not habitually.
Liquid Glass is following the same arc, faster. The design community has been here before. It shows in how quickly the discipline emerged this time.
The pattern is always the same: Apple announces, designers overreact, the web cargo-cults the aesthetic, backlash arrives, and sensible selective adoption follows. Liquid Glass is in the middle of that arc — and knowing where you are in it changes how you should respond.
The year-one reality check
The backlash to Liquid Glass was significant and specific. Users reported shifting colours and floating icons making interfaces difficult to read. Dark mode became particularly problematic — glass tints and moving reflections caused eye strain and, for some, dizziness. Animations ran sluggishly on devices without Apple Silicon. Some routine flows required more taps than before. The critique that landed hardest was blunt: Apple had prioritised visual expression over usability discipline.
The accessibility discourse was faster and louder than it had been for glassmorphism, which is exactly as it should be. The community had already learned that semi-transparent layers over complex imagery fail contrast requirements, that blur motion triggers vestibular issues, and that hiding remediation in accessibility settings is not an adequate solution.
Apple's response was characteristic: no backtrack. Liquid Glass will become mandatory for all App Store apps. Refinements will arrive through point releases. The direction is fixed; the execution is improving.
In SaaS and on the web, the influence has been real but restrained. Designers are borrowing the vocabulary — depth, layering, adaptive surfaces, floating elements — without copying the material system wholesale. Modals, navigation headers, and contextual overlays are the primary adoption sites. Full-page glass backgrounds have not followed. That discipline is correct.
Note: AppleInsider, reviewing iOS 26 one year on, framed it well: the Liquid Glass complaints hide the real problem. The debate is not really about transparency — it is about whether Apple is prioritising visual expression over the usability discipline that made its design language worth following in the first place. That tension has not been resolved.
What Liquid Glass actually changes for your SaaS
There are three distinct areas where Liquid Glass creates decisions for SaaS teams. They require different answers — and conflating them is where most teams go wrong.
1. User expectations are shifting
Over two billion Apple device users are now spending their days in an interface built on depth, adaptive surfaces, and floating controls. Their baseline for what a modern interface looks and feels like is moving. This does not mean your SaaS product needs to look like iOS 26. It means you need to understand where the reference point is going so you can make deliberate choices about where your product sits relative to it.
The products that age fastest are not the ones that failed to adopt the latest trend. They are the ones that stopped investing in visual language entirely, still shipping the same flat grey UI from 2019 as if expectations stood still.
A short conversation with TheBullseye can tell you whether your brand is keeping pace with what users now expect.
2. Your native iOS or iPadOS app
If your product includes a native iOS or iPadOS app, Liquid Glass compliance is not optional. Apple is making it mandatory for App Store distribution. The visual update needs to happen — and it needs to happen with the discipline that Liquid Glass demands: selective application, accessibility checks at every component state, and contrast verification against the darkest and most complex content the glass will sit above.
The teams that treat this as a design refresh opportunity rather than a compliance checkbox will come out ahead. Depth, layering, and floating controls applied thoughtfully produce interfaces that feel genuinely more alive. That is worth building toward, not just toward meeting the minimum bar.
3. Your brand's visual language
This is the area most SaaS teams conflate with the product question, and it is a separate decision. Whether your marketing — your explainer video, your website hero, your brand assets — reflects the visual sophistication that users now encounter daily in their OS is a different question from whether your product UI uses glass surfaces.
Product and brand are different problems. The brand question is worth asking independently of the product roadmap, and often it is more urgent.
What does not translate from iOS 26 to web SaaS
Liquid Glass is a native system feature, hardware-accelerated by Apple Silicon, embedded in Apple's rendering pipeline. The web is a different environment — and the constraints matter.
The nearest CSS equivalent, backdrop-filter: blur(), is GPU-intensive, browser-inconsistent, and performs poorly on mid-range hardware. Chromium has improved; Safari handles it best of all browsers. But 'better than it was' is not the same as 'Liquid Glass quality at acceptable performance cost.' On real-world hardware — not the M-series MacBook you are designing on — the experience degrades.
WCAG contrast requirements add a harder constraint still. Text over a blurred, content-sampled background regularly fails the 4.5:1 ratio required for WCAG AA compliance. The fix — dark pill backgrounds behind text, contained glass regions over controlled backgrounds — is achievable but requires discipline at every component state. Designers who copy the aesthetic without checking contrast at every state are building accessibility debt into every release.
Glass as a tool, not a treatment. Use it for high-value surfaces where it signals hierarchy and depth. Reserve it. Verify contrast. Test on mid-range hardware. This is the same lesson glassmorphism taught — it applies directly to Liquid Glass-inspired web design.
SaaS teams that get this right start with a clear brief: what the visual language needs to communicate and where the functional constraints sit. TheBullseye can help you frame that before a pixel is moved.
TheBullseye perspective
The question we hear most often from SaaS founders is: 'Do we need to redesign our UI to look like Liquid Glass?' That is almost always the wrong starting point.
The right question is: what does our brand need to communicate to the people we are trying to reach — and is our current visual language, across product and marketing, capable of communicating it?
Liquid Glass is Apple's answer to a specific Apple problem: how do you make system UI feel expressive and alive without distracting from the content it frames? Your SaaS product has a different problem. The answer is shaped by your audience, your positioning, and your stage — not by what Apple shipped last June.
The more interesting opportunity for most SaaS brands is not the product UI. It is the marketing layer — the explainer video, the hero section, the brand assets that users encounter before they ever log in. That is where the vocabulary of depth, motion, layering, and glass surfaces can be applied expressively without the functional constraints of production UI. And that is where the gap between where your brand is and where user expectations have moved tends to be widest.
Strategy before aesthetics. That is the line we build on.
FAQs
Liquid Glass is Apple's new material-based design language, announced at WWDC on 9 June 2025 and introduced across iOS 26, iPadOS 26, macOS Tahoe, tvOS 26, visionOS 26, and watchOS 26. It is a real-time rendering system that produces translucent, refractive surfaces which dynamically respond to the content behind them, light conditions, and user movement. Controls float as a distinct layer above app content, morphing and collapsing as the interface demands. Apple describes it as the most extensive software design update it has ever shipped.
Glassmorphism, named by designer Michal Malewicz and popularised in 2020 and 2021, was a static visual treatment: blur the background, apply a frosted transparent layer, imply depth. Liquid Glass is a reactive material system: surfaces refract their surroundings in real time, specular highlights respond to scroll and device movement, and the rendering is hardware-accelerated by Apple Silicon. You can approximate glassmorphism with a CSS filter on any device. Liquid Glass requires Apple's rendering pipeline to function as designed — it is a system, not a style sheet.
Not directly, and there is no compliance requirement for web products. The influence is real but indirect: as over two billion Apple device users habituate to depth, adaptive surfaces, and floating controls in their daily OS, their sense of what a modern interface looks and feels like will gradually shift. Web SaaS products that last invested in visual language several years ago risk feeling dated — not because they lack glass surfaces, but because they stopped moving while user expectations did not.
Not directly, and there is no compliance requirement for web products. The influence is real but indirect: as over two billion Apple device users habituate to depth, adaptive surfaces, and floating controls in their daily OS, their sense of what a modern interface looks and feels like will gradually shift. Web SaaS products that last invested in visual language several years ago risk feeling dated — not because they lack glass surfaces, but because they stopped moving while user expectations did not.
Semi-transparent surfaces over complex imagery regularly fail the 4.5:1 contrast ratio required for WCAG AA compliance, making text hard to read for users with reduced visual acuity. The motion of glass tints and specular highlights has triggered eye strain and vestibular discomfort for some users. On devices without Apple Silicon, animation performance can degrade enough to affect usability. Apple has included accessibility settings, but design experts have consistently noted that burying remediation in settings does not constitute shipping an accessible default.
Yes, with significant constraints. The nearest web equivalent is the CSS backdrop-filter: blur() property, which is GPU-intensive, inconsistent across browsers, and performs poorly on mid-range hardware. WCAG contrast requirements are stricter in web contexts than on iOS. Glass effects work on the web when used selectively — modals, navigation bars, contextual overlays over controlled backgrounds — and poorly when applied wholesale. The glassmorphism era established this discipline, and it applies directly to Liquid Glass-inspired web design.
Yes. Apple is making Liquid Glass compliance mandatory for App Store distribution, with timelines rolling out through point releases. If your product includes a native iOS or iPadOS app, the update needs to be planned now rather than treated as optional. The teams that approach this as a design refresh opportunity — rather than a compliance checkbox — will produce interfaces that feel genuinely more alive.
Liquid Glass drew criticism for prioritising visual expression over usability discipline. Specific complaints included dark mode glass tints causing eye strain, shifting colours making interfaces hard to read, sluggish animations on older devices, and some common flows requiring more taps than before. AppleInsider, reviewing iOS 26 one year on, noted that the Liquid Glass complaints hide the real problem: whether Apple, in its ambition to make iOS feel expressive and alive, moved too fast on aesthetics at the cost of functional clarity. Apple is refining via point releases rather than backtracking.
The vocabulary of Liquid Glass — depth, motion, layering, adaptive colour, glass surfaces — can be highly effective in brand and marketing contexts because it does not carry the functional constraints that make it difficult in product UI. A brand video or explainer using these visual qualities communicates modernity and confidence without needing to pass WCAG checks or perform on older hardware. The question is whether the aesthetic serves your brand's positioning — not whether it maps to Apple's design system.
