In trying to redesign the Firefox 3 Add-Ons Manager UI (AMUI), the team has found that it would be useful to document the various user interaction paths. It should help simplify testing and uncover wacky edge cases.

• To Do: document for each of these flows
  • What is the UI screen flow
  • Decide where user notification is needed (and where in the UI it is provided)
  • Include the full cycle (including the UI post restart)
  • Consider if Firefox behaves differently if the addon were a Themes or Plugin

PATH-1: install an add-on

1a: Install from the web

(from AMO)

1. Click on "Add to Firefox" button
2. Add-ons Manager comes up on the "Installation" tab

process is as it is currently

1b: Install from within the Add-ons Manager

-> from PATH 11, PATH 12

> > >

1. Click on "Add to Firefox" button for the desired add-on
2. Wait while add-on downloads (progress indicated inline)
3. Wait while add-on installs (progress indicated inline)
4. Notice prompt to restart firefox - restart or find another add-on

PATH-2: install a theme

PATH-3: install multiple addons

PATH-4: install and then backout/cancel

PATH-5: uninstall

PATH-6: uninstall and then backout/cancel

PATH-7: addon update (in browser)

PATH-8: addon update (at browser start)

PATH-9: Firefox minor update/add-on compatibility check

PATH-10: Firefox major update/add-on compatibility check

(is it any different than PATH-10?)

PATH-11: Review recommended list (in AMUI)

1. Open Add-ons Manager
2. Switch to "Get Add-ons" tab (already there the first time)

next step -> PATH 1b: Installing an Add-on From within the Add-ons Manager

PATH-12: Search for addons (from AMUI)

1. Open Add-ons Manager
2. Switch to "Get Add-ons" tab (already there the first time)
3. Enter search terms in search field, hit enter / click magnifying glass
4. Review resulting set
5. Options:
   1. Click on one of the results to expand
   2. Refine search
   3. Clear search

next step -> PATH 1b: Installing an Add-on From within the Add-ons Manager