Closed Bug 615381 Opened 14 years ago Closed 1 month ago

New Study: Awesomebar

Categories

(Mozilla Labs Graveyard :: Test Pilot Data Requests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jono, Assigned: jono)

Details

(Whiteboard: new data collection)

To answer the following questions (Requested by Dietrich):


> * responsiveness of switching tabs over time
> * % users that restore session by default
>
> some awesomebar questions:
>
> * how often do users actually use the awesomebar vs other methods of loading urls
> * how do users navigate the awesomebar - arrows, tabbing, mouse?
> * how often is the first result in the awesomebar the one selected?
> * how often is the awesome bar selected and then unselected (ie: user interacted with it, but didn't find what they wanted)
>
> awesomebar + switch-to-tab:
>
> * how often is switch-to-tab in the results?
> * how often selected, when there?
> * how often is an item below switch-to-tab item selected?
Whiteboard: new data collection
Dietrich: are you still interested in this data?

Blake/Hamilton:  Which of these questions can be answered through current data, and which ones need to be implemented as a new study?
I am interested, but am not working on anything at the moment that would utilize it immediately.

However, I'm cc'ing UX and Labs people that are working in this area. They may have additional questions and maybe be able to make more immediate use of it.
I posted some numbers from some initial data in bug 658120:
- average of 3.22 letters typed for users that did press ~1.23 downs
- 11.73 letters typed before hitting return (including 4 for .com)

I also tracked tab presses and switch to tab actions in the awesomebar hd study.
Some data from the 2 day study..
43875 "keys urlbar" events that look like "# down+ return"

9332 :: 3 down return
8220 :: 2 down return
7913 :: 1 down return
6201 :: 4 down return
2553 :: 5 down return
1714 :: 6 down return
1364 :: 7 down return
776 :: 1 down down return
718 :: 8 down return
675 :: 3 down down return
593 :: 2 down down return
482 :: 4 down down return
376 :: 9 down return
255 :: 5 down down return
211 :: 10 down return
205 :: 3 down down down return
201 :: 1 down down down return
164 :: 6 down down return
150 :: 11 down return
And the initial 2hour study seems pretty consistent with the 2day study:

43875 events "# down+ return"
3.247202279202279 letters typed before down
1.182928774928775 downs before return

163 events "# tab+ return"
3.6503067484662575 letters before tab
1.1840490797546013 tabs before return
161731 total keys urlbar events that end with return
61576 events that don't end with return (user clicked)

This *does not* have information about whether users just clicked the dropdown arrow and selected a result.

About 1/3 of the users who type then click type just 1 letter! (Though the data doesn't show what entry was selected.)

20447 :: 1
12219 :: 2
8337 :: 3
5097 :: 4
1848 :: 5
1197 :: 6
1005 :: 7
719 :: back_space 1
501 :: 8
414 :: 1 back_space 1
404 :: back_space 2
395 :: back_space 3
285 :: 9
246 :: back_space
189 :: 10
182 :: back_space 4
180 :: 1 back_space 2
157 :: 2 back_space
143 :: 11
116 :: 1 back_space 3
102 :: 3 back_space
101 :: 2 back_space 1
93 :: space
89 :: back_space 5
89 :: 12
87 :: 13
82 :: 2 back_space back_space 2
78 :: back_space 7
73 :: back_space 6
72 :: 4 back_space
72 :: 2 back_space back_space 1
69 :: down
62 :: 1 back_space back_space 1
62 :: delete
60 :: 2 back_space back_space 3
59 :: 2 back_space 2
58 :: back_space 8
57 :: 14
53 :: 1 back_space 4
Product: Mozilla Labs → Mozilla Labs Graveyard
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.