Labs/Test Pilot/WeeklyMeetings/2009-10-01

From MozillaWiki
Jump to: navigation, search

TP Basic Panel study

aka: A Week in the Life of a Browser

Goal:

To collect basic user/usage data that may help inspire decision-making, recheck feature assumptions, or monitor product performance for your project.


Duration:

5 days (?) per 30-day period (cover both weekdays and weekends. Could also be randomly picked 5 days? or after a big release?)

(Duration will be defined when we finalize what data need to be collected.) (To reduce the server pressure, we need to unbind the submission date. )


Potential metrics:

Browser configuration (one-time metadata which can go along with any other data upload):

  1. OS version
  2. Firefox version
  3. Firefox language/local (e.g. Firefox en-US)
  4. Amount of Add-ons
  5. What add-ons (with their respective version number) are active (could be used to correlate memory data to find add-ons using much memory?)
  6. Number of tool and status bar items (min/max/avg)
  7. Search bar (enabled/disabled/which search engine)
  8. Other tool bars installed

Product performance (collected as a series of values over time):

  1. time taken to launch browser
  2. time taken to open new tab
  3. average time to draw a page
  4. amount of memory available (incl. OS)
  5. amount of memory used (average and max should be stored)


Browsing behaviors (interacts with product performance metrics):

  1. how long FF is running
  2. how often FF gets restarted (user forced? add-on update?)
  3. number of open tabs/windows
  4. count how many pages have been visited/ how many are opened during a session
  5. preferred Tab-Add-ons (i.e. tab view on top or on which side (Tab-Kit))
  6. Search methods: search box, quick search? - <Aza>
  7. Frequency and "average time open" of various non-browser windows: JS Error Console, Preferences, Library, Add-ons manager, etc.


Browser UI (some subset of these could be piggybacked on other tests):

Examples:

  1. Width of the address bar (in relation to the toolbar and its space when shared with other items.)
  2. Tool bar icon sizes (small or large)
  3. Common button order (default navigation buttons)
  4. Whether status bar / bookmark bar / etc are shown or hidden

(To ensure the successful submission to our server, we need to estimate the approximate overall data volume for submission.)