2008-08-24

Content Preferences, Now With Toolbar Widgets

Last weekend I updated my Content Preferences extension to work with Firefox 3.

Along the way, I finished up an additional feature for it: pref widgets you can add to your browser toolbars. The widgets let you set page zoom, page style, and character encoding directly from visible browser chrome, and you use them by customizing your toolbars to include them via the View > Toolbars > Customize command.

Here's the page style widget in the menubar on Linux:




Here are all three widgets on their own toolbar on Mac:




As with page zoom in Firefox 3, these widgets are site-specific and persist across browsing sessions. And as with earlier versions of the extension, they're also available in a sidebar that follows you as you browse around the web and also lets you set global defaults:




UI like this has three possible futures:

  1. If it's useful to a broad range of users a significant percentage of the time, it belongs in the default chrome.

    The page zoom widget is a candidate for this placement. Among other indications, a number of popular sites, like CBS News, provide a version of it to their users within the default "chrome" of their content pages:





  2. Otherwise, if it's useful enough to enough users (a fuzzy definition, to be sure), it belongs in optional chrome, either via an extension or in well-concealed parts of the core product (hidden preferences, the browser toolbar palette, etc.).

    The character encoding widget perhaps satisfies these conditions, as it might be very useful in certain parts of the world where automatic charset specification and detection is not yet up to snuff.

  3. Otherwise, it doesn't belong in the chrome at all.

    I wonder if that's the case for the page style widget, since browser UI for website skinning has never caught on.

    But there's a chicken and egg problem here, since sites don't have impetus to provide multiple skins without useful browser UI for applying them, while browsers don't feel pressure to implement good UI when so few sites take advantage of it. Maybe a persistent site-specific page style widget is just the ticket to change that.


I'm not happy with the widgets, though. The page style and charset widgets simply mirror the functional but archaic menu-based UI in the View menu, and while the page zoom widget tries something new, and it's easy enough to understand, it's difficult and frustrating to use, since it requires precise manual dexterity to set a specific zoom level.

It could be improved in a variety of ways--indicators of which direction does what, markers and snap anchors at specific zoom levels, etc. But maybe there's something even better. Two big buttons for zooming in and out?




A set of sticky buttons that each represent a zoom level?




As for page style, perhaps it could display a set of screenshots showing the appearance of the page with each alternative style applied. And the charset widget could show you what the text would look like if you applied each encoding.

Thoughts?

2008-08-13

Snowl Feedback and Futures

Last month I blogged about Snowl, an experiment with messaging in the browser.  Two weeks ago I presented it at the Firefox+ Summit.  And last Wednesday I released an initial prototype.

I've been getting tons of feedback since then from a variety of sources, including discussion at the summit, comments on the announcement, AMO reviews, discussion in the forum, news and commentary (TechCrunch, ReadWriteWeb, ZDNet, Computerworld, Ars Technica, Slashdot, Digg, etc.), blog posts, and bug reports.

Some opinions I've seen expressed more than once:
  • the river view feels like it fits into Firefox
  • the list view doesn't mix well with general web browsing
  • "I'd rather use a standalone application."
  • "I'd like even more integration with Firefox."
  • many of the prototype's features should be part of Thunderbird
  • it lacks a number of useful features (f.e. sharing)
  • it contains a number of bugs
  • it has lots of potential
Overall, there's a lot of interest in Snowl, in browser/messaging integration, and in messaging innovation generally.  There's plenty more to explore here, and I'd like to see Snowl experiment with the following features in particular:
  • simple web search engine-like attribute-based search
  • a message view optimized for short, simple messages (Twitter, IM, SMS)
  • an experimental message view that uses color, size, graphics, word clouds, animation, or other techniques to help users make sense of their flood of messages
  • support for sending messages, including responding to tweets and posting comments to blogs
  • easy access to feeds from frecent (frequent+recent) sites, sites you are currently browsing, live bookmarks, and feed items you've commented on
  • conversations (i.e. threads) as first-class objects
  • better support for people as first-class objects
  • email, IM, and other message sources
  • user-initiated and automated message grouping (Home/Work, Important/Unimportant, Today/Yesterday/Last Week, etc.)
Of those, I'll be focusing on a short message view, message sending, and conversations as first-class objects for the next iteration.

If you have a burning desire to see something else on this list (or something else entirely) happen sooner than later, your contributions are welcome!  Discuss ideas and post mockups to the discussion forum, pick up the source code from the code repository, and submit patches in bug reports.