Your App Looks Fine Today. iOS 27 Takes That Choice Away.

If you own an app, there's a change worth understanding before it lands on your desk as an emergency. Apple's new look, called Liquid Glass, has been optional for the past year. With iOS 27, it stops being optional. The next time your app gets rebuilt, it will wear the new design whether you planned for it or not. This lab note explains what it means for your business, when it happens, and what to do about it.

What iOS 27 actually is

iOS 27 is the next version of the software that runs iPhones. Apple announced it at its Worldwide Developers Conference (WWDC) on June 8th, 2026, and will release it to the public around September 2026. Most people will get it as a free automatic update, including owners of older iPhones. In practice that means a large share of your customers will be on iOS 27 within weeks of launch.

The feature everyone will notice isn't just a new app or a smarter Siri, it's the way everything looks. And because the update spreads so quickly, the change to how apps appear will be visible to millions of people almost at once. For any business whose app is part of how customers experience the brand, that makes this a design moment worth getting ahead of.

What "Liquid Glass" means

Liquid Glass is Apple's redesign of how apps look. Menus, buttons, and the bars at the top and bottom of the screen become translucent, like frosted glass, so your content shows through them and they subtly react to what's behind them. Apple's goal is to give more of the screen to your content and less to solid, boxy controls.

It first appeared in iOS 26 a year ago and has been refined with iOS 27. Overall, I like it. What changes now is that it becomes the only option.

This isn't a passing trend, either. Apple has written Liquid Glass into its Human Interface Guidelines, the official rulebook it publishes for how apps on its devices should look and behave. When something lands in those guidelines, it's the standard Apple expects apps to meet, and the standard its App Store reviewers increasingly hold apps to.

Why this affects apps that already exist

Here's the part that catches business owners off guard. When Apple introduced this design last year, they gave developers a temporary switch to keep the old look. Lots of teams flipped that switch to buy time. It was always meant to be short-term.

With iOS 27, Apple removes the switch entirely. Any app rebuilt using Apple's latest tools will show the new design, with no way to opt out. Your app doesn't change on its own overnight, but the next time it's updated and resubmitted, the old look is gone.

This matters because most apps get updated fairly often: a bug fix here, a small feature there. Each of those routine updates eventually has to be built with Apple's current tools. So the change isn't triggered by some big decision you'll make deliberately; it's triggered by the ordinary maintenance your app already goes through. That's exactly why it tends to surprise people. The team ships what looks like a minor update, and the app comes back looking noticeably different.

The timeline that matters

There are three dates to keep in mind:

• April 2026: New apps and updates submitted to the App Store must use Apple's recent toolset. This has already passed.
• September 2026: iOS 27 launches. The opt-out switch stops working for any app built with the new tools.
• April 2027: Apple requires all App Store submissions to use the iOS 27 toolset. After this, there is no way to avoid the new design. If you update your app, it adopts Liquid Glass.

The practical takeaway: you have until roughly April 2027 before this is forced, but it arrives the moment you ship your next meaningful update after that point, possibly sooner if you update regularly.

What will actually change on screen

For most standard apps, a lot of this happens smoothly. Apple's building blocks adapt to the new look automatically, so navigation bars and buttons will simply take on the glass appearance and generally work fine.

The trouble shows up where an app has been visually customised. Because bars are now see-through instead of solid, anything that assumed a solid background can look wrong: text becomes hard to read over busy content, elements sit in unexpected places, or brand colours clash with the translucency. The more distinctive and custom your app's design, the more attention it needs.

What this means if your app has a custom look

This is the real risk area. A heavily branded app, with custom buttons, a bespoke menu bar, or a distinctive layout, will not translate automatically. Those pieces need to be reviewed and reworked so they look right and stay readable against the new transparent style. It's not usually a rebuild from scratch, but it is deliberate design and testing work, not a box to tick.

The good news is your team can decide how the glass effect is applied and keep your brand intact, but only if the work is planned rather than discovered after an update ships looking broken.

It's worth being clear about the cost of ignoring it, too. The risk isn't that your app stops working; it will keep running. The risk is quieter and more damaging: an app that suddenly looks unpolished, with hard-to-read text or misplaced buttons, on the phones of the exact customers you want to impress. People rarely file a complaint about that. They just trust the app a little less, or use it a little less. For a business that has invested in a professional-feeling product, shipping a version that looks half-finished is a step backwards that's easy to avoid with a bit of foresight.

What to do now

You don't need to panic, but you do need a plan. Three sensible steps:

First, work with who built and maintains your app and ask them one direct question: has our app been tested against the new Liquid Glass design, and where does it break? A good answer will list specific screens.

Second, treat any update you're planning between now and April 2027 as the trigger. If you're shipping a new feature, fold the design review into that same release rather than doing it twice.

Third, budget for it. For a standard app this may be minor. For a heavily branded one, set aside real design and testing time so your app looks intentional on day one of iOS 27, not patched together after customers complain.

The apps that come out of this looking best won't be the ones that did the most work. They'll be the ones that saw it coming.

Not sure where your app stands? We're happy to run a quick review and tell you honestly whether this is a five-minute job or something to schedule properly.

References

• Liquid Glass — Apple Developer Documentation
• Stop holding out hope, Liquid Glass will be mandatory in iOS 27 — AppleInsider
• iOS 27 Makes Liquid Glass Mandatory: Act Before April 2027 — byteiota