Basil and Morgamic have already blogged about it, and what's new, but I wanted to pipe up and add my congratulations to the AMO/webdev team, AMO editors, and localizers for the really tremendous effort that's gone into overhauling the site.
This release is particularly exciting for me, partly because the wireframes and interaction-model for the site were the first things I worked on when I arrived at Mozilla. Also, though, because alongside the re-skinning and reorganization of the site, I think we've managed to improve the user-experience of finding and installing add-ons in a number of interesting ways:
We've built some logic for this into the new "Add to Firefox" buttons — we detect what you've come to AMO with, and present you with more human-friendly options:
There's more that's new, of course, and Basil's post does a great job of itemizing them.
Between the new AMO, the recent additions to the Add-ons Manager, and cleaning up the install process (a clearer install confirmation dialog and doing away with the install whitelist), I think that it will never have been easier to customize Firefox with add-ons.
My last two posts about the Firefox 3 Add-ons Manager have been mostly about the new Get Add-ons tab, and the ability it provides to our users to get recommendations and search the add-ons catalog without leaving the Manager. No surprise there, really — those features are the new exciting additions.
Alongside that work, though, has been quite an effort to iron out some of the usability wrinkles in the process of installing add-ons. Some of these fixes have been in Firefox since beta 3:
But one of the worst ones on my list has remained as yet unironed: that Firefox abandons users after the restart required by add-ons installation. In the Firefox 2 task flow, a user interacts with the browser in a reasonable back-and-forth until he or she is required to restart the browser. After that point, the user is left hanging — the browser comes back up, but it doesn't offer any visual indication of whether the user has actually accomplished anything. In some cases, the newly installed add-on itself offers up a preferences window or steers the browser to a welcome webpage, but this is by no means universal. Regardless, it's the responsibility of the browser to complete this transaction with the user and to ease him or her back into the restart-interrupted train of thought.
As of today's nightly build, thanks to Dave Townsend and a merry band of reviewers working through Bug 408115, the Add-ons Manager will present itself, post-restart, to confirm that installations have taken place and will, helpfully, point out what's new:
Users can launch into setting preferences, start working with their new add-ons, or just get on with browsing, but, in all cases, they won't be left hunting in the interface for some sign of what just happened.
As usual, I humbly request your feedback — please tell me what's what here in comments or over in the discussion.