The introduction of browser tabs is arguably one of the greatest advances in user interface design since the birth of the web browser. Think about all of the people you know (yourself included, perhaps) who exist in a perpetual state of crowded tabs, to the point that the tabs’ names themselves aren’t readable in the browser interface. They have, in a very real way, become today’s bookmarks.
No one doesn’t want tabs, but effective means of dealing with them in your browser at the least conjures feelings of dissatisfaction in users, and the brightest lights look for solutions. Consider recent attempts to rethink tabs and bookmarks: Microsoft Edge’s vertical tabs, for example, and Arc’s unique implementation.
I don’t think visual exposure is the solution… at least for me. In the same way that organizing files in your system is only useful to a point, the obvious answer is search. On the Mac, I rarely look for a specific file, outside of something I’m working on multiple times a day or throughout a week. I’m more likely to search: Search in Finder, search in Notes, search in an app.
You can, of course, search your open tabs in each of the major browsers. Keyboard jockeys surely know that to see your tabs, you’d type:
- Safari: Shift-command-backslash
- Chrome: Shift-command-a
What you see, however, in the browser’s UI is markedly different from browser to browser. Here’s Chrome:
And here’s Safari:
I actually like Chrome’s behavior and interface better than Safari’s, in this case. First, it visually makes a more meaningful distinction between bookmarks and tabs. In my mind at least, bookmarks are either links you’re going to click on every day, or reference links you want to have handy. They’re of arguable importance anymore, I suppose. Secondly, the menu in Chrome immediately suggests that the user’s next interaction should be search. You don’t have to search, but it’s suggested/revealed in the UI. Safari fits this second bill, but the large preview tiles, while informative, take up a lot of screen real estate.
In the best kind of diversion, I cobbled a quick Keyboard Maestro macro together to at least make the key command the same for showing tabs in between both browsers, as the Chrome one for some reason developed muscle memory for me, whereas the Safari keystroke hasn’t been sticky.
It has make me realize, to some degree, that for as much as I have historically used Safari, I never made the strides to understand it and get the most out of it as I had other applications, and notably Edge. The reason for Edge, of course, is that so many of Windows’ solutions happen in the browsers. That’s an OK version of computing for plenty of people, including students using Chromebooks. It’s just not for me.
So! Back to tabs.
I wrote about Tabby way back in 2003, which I liked because it was a small utility that would show all of your open browser tabs, searchable, across Safari and Chromium-based browsers. I did check out Tab Switcher at the same time, but didn’t ultimately adopt it because it was specific to Safari, and I used it and Chrome (or Edge) simultaneously. I did not, however, prefer Tabby’s interface, which anchored your search to the left side of the screen, resulting in some visual interface weirdness, and it was also hard to see in that corner of my larger home display (this wasn’t an issue on a laptop screen or even the 27” I had at the office).
Happily, it looks like Tabs now supports Chrome as well. I don’t use it as much as I used to, though, so I was gonna switch to Tabs Switcher for a bit anyway.