Efficient Browsing: putting it all together

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Hi, I’m *John Mellor*, and I’d like to talk to you about making *tabs* more *efficient*.

    I’ve been writing Firefox extensions for 4 years, all of which focused on improving the tabs experience. I suspect that my latest, Tab Kit, was one of the extensions that helped inspire this contest, and I’d like to share some of the experience I’ve gained from it, along with my thoughts for the future. My focus is on making tabs *scale well*, whether you use 2 or 200 tabs (for power users will use as many tabs as Firefox makes practical).

    Let’s cut to the chase. The tab bar should be *vertical* *by default*, for a number of reasons:-Vertical lists are easier to scan(as the first words are aligned)-Tab Titles stay visible when many tabs are open- Since tabs are wider than they are tall, this lets you seemore tabs at once- And you saveprecious screen height on widescreens. Screen width is less an issue, as websites are usually narrow, but the user can control how much is taken up via a splitter and an auto-collapse option.

    Probably the main benefit of vertical tabs is the ability to use a scrollbar. These are *much* more usable than scroll buttons. Not only are they much better understood by users, but they are more efficient too. The Size of scroll thumb shows users how many tabs are off-screenin each direction; and users can jumpanywhereby dragging the thumb, rather than being limited to a fixed scroll speed.

    So here’s a mockup, to give you an overview of my design. As you can see, tabs have become a vertical sidebar, and I’ll introduce this first. Other than the tabs, the sidebar contains a Search Box at the top and a Tab List Chooser at the bottom, both of which I’ll cover afterwards.

    When there are few tabs open, thumbnails make tabs more user-friendly. But when you have many tabs open, they just get in the way. I propose to start off showing thumbnails, but to gradually shrink them (without scrolling), until they become useless, then seamlessly switch to tabs without thumbnails (and now allow a scrollbar).

    1 Favorite

    Efficient Browsing: putting it all together - Presentation Transcript

    1.  4 years of writing tab extensions and gathering user feedback  Author of Tab Kit (250,000+ downloads), a prototype for the future of tabs  Aim: make tabs scale well for all users
    2.  Easier to scan (first words aligned)  Titles stay visible  See more tabs at once  Particularly good for widescreens  Splitter & auto-collapse to favicons only
    3. Unlike Firefox 2's scroll buttons:  Size of scroll thumb shows users how many tabs off- screen in each direction  Non-fixed scrolling speed – jump anywhere by dragging thumb
    4.  Thumbnails make tabs clearer for beginners, not to mention adding huge Fitts‟s Law targets  Idea: instead of scrolling list of square thumbnails, shrink thumbnails until too small to be useful, then seamlessly switch to tabs without thumbnails (and only then add a scrollbar)
    5.  Currently, tabs scatter in arbitrary order  Must help organise user  Grouping related tabs emphasizes logical connections and minimises mouse travel
    6. Group by domain? Definitely NOT! Consider doing a couple of Google searches on different topics, and opening some results from each search. The unrelated search pages would be grouped together, while their corresponding results would be scattered around and intermixed arbitrarily based on the domains of the results (which the user is very unlikely to remember before they look at the results!)
    7. Instead group tabs semiautomatically:  Automatically by ancestor  Manually by letting user group arbitrary ranges of tabs together
    8.  When users open tabs from links, treat the opened tabs as children of the tab they were opened from, forming a tree (group tabs with common ancestor) 1. Naturally keeps related tabs together 2. Very useful indication of where tabs come from
    9.  Shift+click to Group Tabs From Current To Clicked; Ctrl+click to Add/Remove Clicked Tab From Current Group (chosen by analogy to how selections in lists work; discoverable via context menu)  Drag-select to group would be ideal, but mustn‟t clash with tab dragging. Most user friendly might be a button to activate drag-grouping?
    10.  To incorporate manual groups into tree, surround groups with folders  Also provides central location for group operations  Full, intuitive, drag-drop reorganisation n.b. Coloring groups is still useful – see later
    11.  Groups and subtrees can collapse down to a favicon list:  Can select faviconized tabs, drag-and- drop them, hover to see titles, etc. as usual  Show favicons half size if too many to fit  Auto-collapse inactive groups?
    12.  Clicking close buttons closes descendants too (hovering over highlights them as hint)  Show non-modal “You closed 10 tabs. Undo?” option rather than confirm dialog  Ctrl+W however only closes current tab (de‐indent descendants) as user probably isn‟t thinking about the hierarchy  Context menu offers both
    13.  Groups ↔ Bookmark folders  Move (drag) within or across windows  Detach to new window
    14.  Color tab groups to aid identification  Automatically allocate colors distinct from nearby groups (simple algorithm)
    15.  Scrollbar track background should show group colours in appropriate positions  Helps users keep track of offscreen tab groups, and quickly navigate to them at will. For an evaluation see D. S. McCrickard & R. Catrambone (1999). "Beyond the Scrollbar: An Evolution and Evaluation of Alternative Navigation Techniques". In Proceedings of the IEEE Symposium on Visual Languages (VL'99), pp. 270-277.
    16.  Has main advantage of Fisheye while keeping more efficient and familiar scrollbar.  Could also highlight tabs (both onscreen and on scrollbar) from same site as current, to help user avoid duplicating tabs/groups?
    17.  Highlight unread tabs in bold so user can remember which they‟ve yet to look at  Also highlight tabs whose titles have updated (e.g. Gmail received new mail)  Converse: nice to Updated tab know which tabs are inactive. Perhaps make these darker, as in Unread tab Aging Tabs extension?
    18.  Find-as-you-type filtering to rapidly narrow tabs down  Searches titles and URLs by default Group color  Optional full-text remains visible search
    19.  Multiple independent “tab lists”  Each with its own tree of tabs  Tabs open in current tab list by default  All tab lists (& their tabs) are persistent across sessions and across windows until deleted  Switch via dropdown below tabs (unlike tabs, no point in constantly displaying lists):
    20.  For example, my “Mozilla Design Challenge” tab list contains a group of tabs from the forum, a group with the recommended articles, a group of extensions from AMO, as well as some loose tabs.  Like windows but without the clutter, especially for inactive tab lists (can of course still show multiple tab lists simultaneously in multiple windows)
    21.  Unload inactive tab data from memory; session restore it when next used  This includes tabs in inactive tab lists  Esp. when reloading a session, keep all tabs unloaded to hugely speed startups  Some exceptions (stateful Flash/AJAX)
    22.  Let user „pin‟ tabs that should be always visible at top of tab bar  Tab-list independent  Persistent across sessions  Unaffected by scrollbar, but collapsible, like other groups:
    23.  Vertical tabs needn‟t replace sidebars (e.g. allow tabs on left, sidebar on right)  Show (rotating?) progress pies instead of spinners on loading tabs  Open selected links in tabs
    24.  Tabs as temporary bookmarks  Drag-and-drop to easily bookmark/restore tabs/groups  Makes vertical tab bar more useful with few tabs  Unfortunately, clashes with (shrinking) thumbnails, and tab lists make temporary bookmarks less useful, so not added to mockup
    25.  Could allow user to sort tab bar › By last viewed › By most used › In order of opening › By title › By URL (sort by domain, then subdomain, then query string, hence temporarily „grouping‟ by domain)  Temporarily ignores groups/tree  Sorts can persist (and be updated live), but only intended for temporary specific uses (e.g. “Where‟s that tab I just opened?”)
    26.  Vertical tab bar  Tab grouping, automatically by ancestor with full manual control  Tab tree  Highlight unread and updated tabs  Find-as-you-type filtering of tab bar  Tab lists (Workspaces)
    27.  Tab thumbnails, shrinking to nothing as more tabs are opened  Ctrl/Shift-click and Drag-select to manually group tabs  Scrollbar track showing off-screen tab group colors (and same domain)  Taking old tabs out of memory (& CPU)  Folders mix tree with unstructured grouping  Merge tab bar & bookmarks sidebar?  Mix group color (hue) with age (lightness)
    SlideShare Zeitgeist 2009

    + jomeljomel Nominate

    custom

    1209 views, 1 favs, 0 embeds more stats

    MAKE SURE TO PRESS PLAY TO GET SOUND!
    My vision of more

    More info about this document

    CC Attribution License

    Go to text version

    • Total Views 1209
      • 1209 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 5
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Tags