One idea I'd just thought of adding might be to use the empty space below the tabs with a top-list of frequently used URLs, excluding those already open. And maybe the most recently closed tabs. Also when mentioning productivity, I immediately thought of putting check boxes or labels on the tabs. Or swipe actions.
Agreed! My work was done on OSX, as a proof of concept. My colleague Hayden is doing some great work to carry it forward, including Windows support (https://github.com/dhdemerson/VerticalTabs)
Thanks for pointing this out, I should have made mention in my post :) I've have seen tree style tabs – which does a great job for more advanced organization of tabs. For my experiments (and Firefox features in general), we try and focus on simplicity and the more general audience.
TST is pretty simple to use and extensible if you want more. What you did was... not really practical. Have you tried using TST for a few days? I promise you won't be able to go back to any other way of browsing.
For developers and other tech guys maybe. But the average, non tech savy users have a very hard time understanding hierarchies and therefore tree controls. It's to such a degree that UX specialists like Alan Cooper strongly suggests never using tree views unless the data is naturally thought of as a hierarchy, such as a family tree etc.
>But the average, non tech savy users have a very hard time understanding hierarchies and therefore tree controls
Oh, that sounds very much like BS. "non tech saavy" users have been using hierarchies in computers since before Windows 95 (considering people that used MS-DOS as 'tech saavy' users). DOS/Windows folders were presented in a structure; File Explorer presented stuff in a structure manner. Hell, the "my documents" folder was structured... and even Gnome (the epithome of doing simple interfaces) presents folders in a structure manner.
Because a UI control exists before Windows 95 doesn't mean it's understood by the majority of users. Also, there is a larger amount of users with minimal software exposure now than ever before, due to tablets and smartphones.
If your computing experience is limited to iOS for example, chances are you'll never even have seen a nested tree view control, much less understand the hierarchy behind it.
At least just read a minimum on usability and UX, before being so rude as to "call bullshit" based on your own personal opinion.
They get lost in it because there are too many things, but they understand how it works. Which is the point here since they would make the tree themselves with something such as TreeStyleTab
No, the cases I speak of get lost in it when they have tree-style menus, when their apps are grouped in different themes (games, tools, office) and want a flat, 3-column single layer.
Right now it works (best) on OSX, I'd love to get some help to make it work better across platforms. My colleague Hayden's work will probably progress faster than mine (this was just a side project for me!) https://github.com/dhdemerson/VerticalTabs
Thanks for the comment, we always try and cater to as many of our users as possible. If you've used our tools, are there particular areas that cause more trouble than others? Do you find the dark or light theme easier to navigate (available in Nightly builds right now)? Would love to hear how our tools can be improved in this regard! Feel free to email me at darrin[at]mozilla.com if you'd rather not post on HN.
You should grab our Nightly build then :) We have parsed responses in the Network tab, I just tried HTML and JSON for you and both show as expected. See http://imgur.com/OHO4lFH and get Nightly at http://nightly.mozilla.org/.
Sorry, that is just a prototype for now! We are in the process of designing and planning the memory (and performance) tools, which should hopefully be available sometime this year.
We (I am the author of that post) definitely care about color blind users and want to make our tools as usable for as many people as possible! Photoshop allows you to simulate varieties of color blindness and we keep that in mind. We are also trying to provide better visual cues, like shapes/textures rather than relying solely on colors. The network panel in nightly for example has shapes to indicate HTTP response codes.
Secondly, once you switch to the light theme (available in the options pane of nightly) it should persist for you, so it will become your "default".