334
edits
Spectator: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
Although, we can obtain this data through detailed user studies. A more scalable solution is to technically instrument the browser to collect anonymous usability information and submit to a central site. A web application would aggregate this information into actionable summaries. | Although, we can obtain this data through detailed user studies. A more scalable solution is to technically instrument the browser to collect anonymous usability information and submit to a central site. A web application would aggregate this information into actionable summaries. | ||
= Subject Areas = | |||
There are numerous metrics that could be collected. For the initial build of this system, we will focus on feature use. In particular, the following questions: | There are numerous metrics that could be collected. For the initial build of this system, we will focus on feature use. In particular, the following questions: | ||
== Feature Use == | |||
* How many times is the search box used? | * How many times is the search box used? | ||
* Which search is being used? | * Which search is being used? | ||
| Line 19: | Line 18: | ||
* How many tabs are used? | * How many tabs are used? | ||
= Technical Implementation = | |||
The current proposal is to implement instrumentation as an extension. The advantages to this approach include the ability to update the extension independently and greater flexibility to promote/market the extension. | The current proposal is to implement instrumentation as an extension. The advantages to this approach include the ability to update the extension independently and greater flexibility to promote/market the extension. | ||