iOS 27 Is Here — and Liquid Glass Is No Longer Optional for Your App

Apple released iOS 27 on 14 September, following its 9 September event, with the update supporting every iPhone back to the iPhone 11 (MacRumors). Most of the launch coverage focuses on the new Siri and Apple Intelligence features. But if you own or manage an iPhone app, the most consequential change isn't a feature at all — it's the quiet end of a grace period.

Liquid Glass, the translucent design language Apple introduced with iOS 26, has moved from "strongly encouraged" to unavoidable. Here's what that means in practice, what tends to break, and how to plan a migration that improves your product instead of just patching it.

A quick recap: what Liquid Glass is

Apple introduced Liquid Glass at WWDC 2025 as its biggest visual overhaul in over a decade — a system-wide material that behaves like layered, light-refracting glass across buttons, tab bars, navigation and widgets (Apple Newsroom). The first year was bumpy: developers and users complained about legibility, and Apple iterated repeatedly on transparency levels. iOS 27 continues that refinement with more uniform refraction, improved contrast and a user-facing adjustment slider — a sign Apple is settling the material into its long-term form rather than backing away from it.

The opt-out is gone

When Liquid Glass shipped, Apple gave developers an escape hatch: a build setting called UIDesignRequiresCompatibility that let apps compiled with the new tools keep their pre-Liquid Glass appearance. That hatch is now closed, and Apple's own documentation is unambiguous about it — the key, it says, is ignored when you build for iOS 27 or later (Apple Developer Documentation).

"We'll deal with it later" now has a deadline attached, and the deadline is whenever you next compile.

What actually breaks (and what just looks bad)

Custom navigation and tab bars. Apps that pixel-perfected their own bars over the years are hit hardest. System components adopt the new material automatically; custom ones sit next to them looking like screenshots from a different decade.

Contrast and legibility. Translucency means your content shows through interface layers. Text that sat comfortably on an opaque bar can become hard to read over a busy scrolling background — a real accessibility issue, not just an aesthetic one. Test with Reduce Transparency and Increase Contrast switched on; a meaningful slice of your users runs them.

Brand colour systems. Liquid Glass tints and refracts. A brand palette specified as flat hex values needs rethinking as a set of tints, materials and elevations. This is design-system work, not a find-and-replace.

App icons. Layered icon appearance modes — light, dark, tinted, clear — mean a single static PNG now renders in contexts it wasn't drawn for. If your icon hasn't been rebuilt as a layered asset, it's quietly degrading on users' home screens.

Dark mode edge cases. Every translucency decision doubles in dark mode. Screens that were "fine" in a quick check often fail in dark mode over dynamic content.

Rising expectations are the real deadline

Apple says iOS 27 makes app launches up to 30% faster and newly taken photos appear up to 70% faster. Each OS release resets what "normal" feels like. When the system and the big apps feel faster and visually coherent, a dated app doesn't just look old — it feels slow and untrustworthy by comparison, and that shows up in retention and reviews.

This isn't an Apple-only dynamic either. Android's design language has been moving in a more expressive, motion-rich direction over the same period. Cross-platform products need a design system that expresses one brand through two native dialects — not one compromise UI exported twice.

A pragmatic migration plan

You don't need a ground-up redesign. You need a sequenced one.

• Audit first. Build your current app against the new SDK in a staging environment and catalogue what breaks, what degrades and what merely looks off. An afternoon of honest screenshots beats weeks of speculation.
• Triage by traffic. Fix the screens where users actually live — onboarding, home, checkout — before the settings page anyone visits twice a year.
• Rebuild the design tokens, not just the screens. Translate your brand palette into materials, tints and elevation rules once, centrally, so every future screen inherits the answer. This is the same groundwork that makes a design system machine-legible for everything else coming down the line.
• Test accessibility settings as first-class citizens. Reduce Transparency, Increase Contrast, Dynamic Type at large sizes.
• Ship deliberately, before you're forced to. A planned Liquid Glass release is a marketing moment. An accidental one, via a rebuilt bug-fix release, is a support-ticket generator.

The takeaway

When a platform design language shifts, every app on it either moves with it or visibly falls behind — and with iOS 27, Apple has stopped holding the door open. Teams that treat this as a chance to clean up their design system will come out with a better product. Teams that ignore it will make the decision anyway, just unintentionally, on whatever day they next compile.