By John Gruber
Build web apps, iOS apps, and workflows with Retool.
Our long national iOS 15 Safari nightmare ended last month, praise be, but the lesser of the two bad Safari designs unveiled at WWDC persists and actually shipped: the new tabs in Safari 15 for Mac. Safari 15 on iPad suffers similarly, but it’s the Mac version I’ll concentrate on here.
The most controversial Mac Safari changes shown at WWDC — compressing tabs and the URL location field into a single row at the top of each window, and coloring the entire window with the accent color of the currently frontmost web page — are settings that (thankfully) can be turned off in Safari’s Preferences window (under “Tabs”, natch). The “Compact” layout that puts tabs and the location field in the same row — by using the tabs themselves as the text editing fields for URLs — is, thankfully, off by default. But the “Show color in tab bar” option is on by default:
Here’s what it looks like as you switch back and forth between tabs with this option on. (Note that I’ve done nothing, explicitly, to support this feature on Daring Fireball.)
Apple, in the “What’s New in Safari” alert that’s shown upon first run after upgrading to Safari 15, describes the new tabs thus:
Tabs have a rounder and more defined appearance and adjust to match the colors of each site, extending your web page to the edge of the window.
This is nonsense. The color matching does not extend web pages at all. It just looks like it does. Who, for example, owns this button?
Is that Defector’s button? Or is it Safari’s? It sure as shit looks like it’s Defector’s — but it’s Safari’s. Click that thinking it’s a menu for Defector and you’ll be surprised to be dumped to your Safari Start Page.
I despise the new tabs even when the “Show color in tab bar” and “Compact” layout settings are turned off. They don’t look like tabs. They look like buttons. Here are four full-window screenshots, in order from worst to best to my liking:
The “Separate” layout, with “Show color in tab bar” off, is the closest you can get to Safari’s previous tab design. These new “tabs” waste space because, like buttons, they’re spaced apart. Tabs that look like real-world tabs aren’t just a decorative style. They’re a visual metaphor. My brain likes visual metaphors. It craves them. And my brain is very much comfortable with the particular visual metaphor of tabs in a web browser window. Buttons do not work as a metaphor for multiple documents within a single window. Thus, trying to use the new Safari 15 on Mac (and iPadOS 15, alas), I feel somewhat disoriented working within Safari. I have to think, continuously, about something I have never had to think about since tabbed browsing became a thing almost 20 years ago.1 The design is counterintuitive: What sense does it make that no matter your settings, the active tab is rendered with less contrast between the tab title and the background than background tabs? The active tab should be the one that pops.
Safari actually debuted as a public beta in January 2003 without any support for tabbed browsing (which, humorously, I was OK with — the tab habit hadn’t gotten its grips on me yet), but within a few weeks it had tabs. Apart from that brief weeks-long stint when it debuted as a public beta in 2003, Safari for Mac has always had tabs. And those tabs have always looked like tabs, because why would anyone want to make them look like anything other than tabs? There are certainly a lot of ways to style tabs in a UI. Try different browsers, try different windowing OSes, and you’ll see many different takes on tabs. Even the Safari team at Apple has experimented with various different tab styles — most famously, in 2009, when they put the tabs at the top of the window for Safari 4’s public beta. It was an experiment Apple wound up abandoning, but they didn’t need to — it could have worked well with some tweaking, as I explored in a copiously illustrated post at the time.
Google Chrome — and Chrome-derivatives like Brave and Microsoft Edge — now use tabs-on-top layouts very much like what the Safari team experimented with in 2009. It’s a fine design that confuses no one. They work because they both look like tabs and embrace the tab metaphor.
Not so with Safari 15. Consider a window with two tabs, perhaps both from the same website. A very common scenario, I think it’s fair to say. With Safari 15, it’s almost a guessing game, a coin flip, when you want to determine which tab is active:
It’s even more ambiguous in dark mode:
In Safari 14 — as well as Safari versions 1–13, and every other browser I’m aware of — there’s never any ambiguity about which tab is active, in either light mode or dark mode:
There’s no ambiguity because the tabs are visually connected to the rest of the browser chrome, and the browser chrome is rendered in a way to make it visually distinct from the web page content. There’s no ambiguity because the first job of any tab design ought to be to make clear which tab is active. I can’t believe I had to type that sentence. But here we are.
Yes, it gets easier to discern the active tab with more than two tabs in a window, because any confusion as to whether darker or lighter indicates “active” is alleviated by having only one tab shaded differently than the others. But the utter failure of the new Safari tab design with exactly two tabs should have been reason enough to scrap this idea while it was experimental. Replacing an interface that doesn’t require you to think at all with an interface that requires you to think — even a little — is a design sin of the first order. Designs should evolve over time in the other direction.
Does the Safari 15 tab design look cooler, particularly with the default coloring? I say no. I think it’s novel, obviously, but suspect it’s going to get old quickly. But even if you think it looks cool as fuck, that’s not what user interface design is about. A good user interface needs to work first, then worry about looking cool.
The Safari 15 tab design is a blatant violation of Steve Jobs’s oft-cited “Design is how it works” axiom:
Most people make the mistake of thinking design is what it looks like. People think it’s this veneer — that the designers are handed this box and told, “Make it look good!” That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.
If I were preparing a lecture for design students about what Jobs meant, I’d use Safari 14 and 15’s tab designs as examples. If anything, Safari 15 feels like a ginned-up example — too obviously focused solely on how it looks, too obviously callous about how it works. If it hadn’t actually shipped to tens of millions of Mac users as a software update, you’d think it was a straw man example of misguided design.
Functionality? Here’s functionality. In Safari 14, the close tab button is just to the left of each tab’s favicon. In Safari 15, bizarrely, the favicon turns into a close button on hover. First, hiding functionality behind unguessable hover states is a bad idea, but a hallmark of Apple’s current HI team’s fetish for visual minimalism. But turning an icon into a close button? Good god. Guy English, back on June 18:
Safari beta on macOS 12 tabs have a real anti-pattern: the favicon in the tab turns out to be the close tab button on hover. So if you aim at the favicon you’ll close the tab. The only place in the entire OS where clicking an icon will delete the object you were interested in.
It’s hard to express in words how perverse this is. The icon that represents the web page is a destructive button for that web page. Imagine clicking a document icon in the Finder to trash it.
Speaking of close buttons, if you open a dozen or so tabs in a window in Safari 15, the “tabs” shrink to just show the favicons. When this happens, close boxes stop appearing on non-frontmost tabs, even on hover. So how can you close these tabs without first activating them? To close them while they’re not frontmost, you need to hold down the Command key while you move the mouse over them. Guess how many people are going to figure that out? (Not many.) Safari 14 does this too, but because its actual tab tabs are more space efficient, you have to open way more tabs in a window to get to the point where close boxes only appear for non-frontmost tabs while holding down the Command key.
From a usability perspective, every single thing about Safari 15’s tabs is a regression. Everything. It’s a tab design that can only please users who do not use tabs heavily; whereas the old tab design scaled gracefully from “I only open a few tabs at a time” all the way to “I have hundreds of tabs open across multiple windows”. That’s a disgrace. The Safari team literally invented the standard for how tabs work on MacOS. The tabs that are now available in the Finder, Terminal, and optionally in all document-based Mac apps are derived from the design and implementation of Safari’s tabs. Now, Apple has thrown away Safari’s tab design — a tab design that was not just best-of-platform, but arguably best-in-the-whole-damn-world — and replaced it with a design that is both inferior in the abstract, and utterly inconsistent with the standard tabs across the rest of MacOS.
The skin-deep “looks cool, ship it” nature of Safari 15’s tab design is like a fictional UI from a movie or TV show, like Westworld’s foldable tablets or Tony Stark’s systems from Iron Man, where looking cool is the entirety of the design spec. Something designed not by UI designers but by graphic designers, with no thought whatsoever to the affordances, consistencies, and visual hierarchies essential to actual usability. Just what looks cool. This new tab design shows a complete disregard for the familiarity users have with Safari’s existing tab design. Apple never has been and should not be a company that avoids change at all cost. But proper change — change that breaks users’ habits and expectations — is only justifiable when it’s an improvement. Change for change’s sake alone is masturbatory. That with Safari 15 it actually makes usability worse, solely for flamboyant cosmetic reasons, is downright perverse.
Safari debuted in 2003 as the only major browser on Mac OS X with a first-class Mac interface.2 It remains the only major browser with a truly native Mac interface 18 years later. Safari hasn’t just been a Mac-assed Mac app, it’s been one of the best Mac apps, period — the sort of app UI designers turn to when they need to study how a proper Mac app implements something in its interface.
As someone who depends upon my web browser and relishes Mac apps that do things the Macintosh way, I’m angry. But I can only imagine how furious the WebKit team at Apple is. Safari is the app and WebKit is the rendering engine, but from a practical perspective they’re one and the same, because — again — Safari is the only major WebKit browser for the Mac. Not because there couldn’t be other great Mac WebKit browsers, but because Safari has been so good as a Mac app for so long, it left no room for a third-party Mac WebKit browser to gain traction.
The team that came up with these Safari redesigns shown at WWDC almost destroyed iOS Safari. Apple changed course over the summer and avoided that disaster. But though good design sense prevailed and iOS Safari was spared, the same design team has been allowed to disfigure Mac (and iPad) Safari. It’s one thing when a bad UI design ships in a new or obscure Mac app from Apple; it’s another thing altogether for what’s almost certainly, by any measure, the single most-used app on the platform.
Web developers argue endlessly about the underlying differences in capabilities of rendering engines. Users don’t think like that, though. They just want to use a browser that works, and that feels familiar and gets out of their way. Safari 15 for Mac is the opposite — it is unfamiliar and in your face.
Safari 15 for Mac is a tragic own goal — a de facto gift to Chrome and its growing browser hegemony. The option to turn off “Show color in tab bar” is an admittedly appreciated glass of ice water in hell. But true relief from the boiling hot sun of these craptacular “tabs” is just a download away. Google could and should run ads targeting Safari users, with a simple welcoming message: Switch to Chrome, the Mac browser where tabs look like tabs.
I decided to check on this, and I’m glad I did. Tabbed browsing didn’t go mainstream until after the year 2000, but there were tabbed browsers as early as 1994, in a Windows web browser named NetCaptor written by Adam Stiles. Look closely for the tabs in those screenshots — they’re at the bottom of the windows. ↩︎
The team behind Camino, an open source Mac browser based on Mozilla’s Gecko rendering engine that debuted under the name Chimera all the way back in 2002, did yeoman’s work to make Camino as Mac-like as it was. They could not out-Mac Safari though. ↩︎︎
|Previous:||Why Does the iPhone Still Use Lightning?|
|Next:||Apple Watch Series 7|