Safari 15's debut at WWDC drew genuine enthusiasm in web-focused circles: the tinted browser controls were a fun experiment, and iCloud Private Relay earned broad praise as a security advance. The interface changes, however, landed very differently once the discussion moved beyond front-end developers.
The case against the new chrome
Michael Tsai's roundup of reactions collects a long list of serious complaints, including Steven Shen's demonstration of how awkward the tabs are to operate on iPadOS and Saagar Jha's observation that private and regular browsing are nearly indistinguishable. Most of the criticism, though, targets the browser controls rather than the color effects.
Nick Herr's verdict was blunt: "Chickenshit Minimalism." His objections are structural. Folding the address bar into each tab means the entire control surface shifts as tabs scroll horizontally and resize when tabs are opened or closed. Tabs are also small, so controls like reload and share are hidden by default inside a "⋯" overflow menu—and for people who share links often, there is no way to restore that button to the toolbar permanently. Federico Viticci made a related point about iOS Safari: hiding buttons from popular built-in apps is a bad idea.
John Gruber framed the design as a noble experiment with intriguing ideas that, in practice, amounts to a usability regression, and said he would like Apple to return to the previous Safari interface for tabs and browser chrome. Even the Share button, he noted, now costs an extra click or tap. He went further, predicting that shipping this design on the Mac would push many current Safari users toward Chrome or other Chromium-based browsers.
Defenders: effort, not error
Others see merit in the attempt. Jason Snell called the redesign a self-inflicted wound while arguing that Apple deserves credit for the effort: designers examined every element—tabs, URL bar, toolbar items—to see what could be hidden, removed or minimized to give the page more room. He tied that to the fact that most Apple customers use screens measuring at most 13 inches diagonally, and argued that no app category, from browsers to email clients to text editors, is a solved problem.
Jeff Kirvin reads the release as misunderstood—the first step toward a new iOS design language built around adaptive, contextual interfaces. Since the shift to the all-screen iPhone X design, he argues, content has been king on iOS and Apple has steadily removed user chrome; Safari 15 continues that trajectory.
The disagreement, then, is less about whether the interface changed than about whether that direction is progress. Whether dissatisfaction alone would drive users to switch browsers is an open question; the more likely split is between people who use Safari because it ships on their Mac and people who choose it deliberately for its Apple-ness.
Practical notes for web designers
- Niels Boey's "What does the Safari 15 update mean for my designs?" is among the most thorough surveys of the visual changes available.
- Luke Channings investigated whether Safari 15 fixes the viewport height problem. The answer is mostly yes: subtracting
env(safe-area-inset-bottom)from100vhgives the intended result.




