Xcode 27 removes the Liquid Glass opt-out. Audit before you recompile.
The ability to opt out of Liquid Glass is going away: recompile with Xcode 27 and your app adopts the new design whether it suits it or not. That turns a routine toolchain bump into a design review.
Among the Xcode 27 changes announced at the 2026 Platforms State of the Union is one that deserved more attention: support for opting out of the Liquid Glass design language is being removed, and apps recompiled with Xcode 27 adopt it automatically.
Read that as a scheduling problem rather than a design one. The next time you rebuild - for a bug fix, a dependency bump, a required SDK version - your app's appearance changes.
Why this differs from a normal refresh
Platform redesigns usually arrive with an opt-in period. You adopt when ready, and the flag buys a release cycle or two to do it deliberately.
Removing the opt-out collapses that. The change is no longer coupled to a design decision; it is coupled to a compile. And the reason you recompile is often unrelated and urgent - a crash affecting users, a security patch, a store requirement with a deadline. Nobody wants to discover a design regression while shipping a hotfix.
Where custom interfaces break
- Hard-coded background colours behind system chrome, which stop lining up once the chrome is translucent.
- Custom navigation and tab bars built to match the old appearance, which now match nothing.
- Contrast that was borderline against a solid background and fails against a translucent one.
- Screenshots and marketing assets showing an interface the app no longer has.
- Snapshot tests, all of which fail at once - a real cost if your suite treats them as blocking.
Contrast is the one that matters
The rest of that list is cosmetic. Contrast is not. Translucency composites your foreground colour over content you do not control. Text that passed a contrast check against a fixed background can fail against a scrolling photograph, and it will fail intermittently - which is worse, because it passes every time you happen to test it.
A contrast ratio measured against a solid colour describes one moment, not a design.
Where text sits over translucent material it needs a scrim, a vibrancy treatment, or a guaranteed-opaque backing. Not a slightly darker text colour and optimism.
A day of work, done early
- Build against Xcode 27 on a branch. Do not ship it - just look at it.
- Walk the five screens users actually spend time on, not the settings screen nobody opens.
- Check every place text sits over an image or a blur, at both type sizes and in both appearances.
- Re-record snapshot baselines in one deliberate commit rather than letting them fail piecemeal.
- Book the marketing screenshot refresh now, because it will be forgotten otherwise.
Do it while nothing is on fire. The alternative is doing it during a hotfix, which is how a cosmetic change becomes a bad week.
The broader point
Apple has been narrowing the gap between platform convention and platform requirement for years. It is a reasonable trade, but it changes what a design system has to buy you. The apps that absorb this cheaply are the ones whose visual decisions live in a token layer rather than scattered through view code.
Sources
Reporting and images linked above belong to their respective publishers and are shown from their own servers. The analysis here is our own.
