Citation Timeline (2010):
Mohan Raj Rajamanickam, Russell MacKenzie, Billy Lam, and Tao Su. 2010. A task-focused approach to support sharing and interruption recovery in web browsers. In Proceedings of the 28th of the international conference extended abstracts on Human factors in computing systems(CHI EA '10). ACM, New York, NY, USA, 4345-4350.
In this paper, authors developed a task-oriented mobile web browser on an iphone. They relay on a previous study which state that most web users leave the browser without finishing their task. Thus, they argue that when a user return back to browser the current techniques such as: history and bookmarks, do not provide good information about what was the task and what was done.
First, they conducted semi-structured interviews with 9 students (aged between 18-29), with different browsing skill sets. They discussed that most of the participants do not use browser's history and bookmarks, but they havely use the autocomplete features, and multiple tabs. Participants often use some sort of annotation or text files to save their task state before leaving computer. They use these techniques to help them when they return back to their tasks.
As a reslt of their semi-structured interviews, authors have concluded their prospect browser design to contain the following features: (a) group multi webpages under one task, (b) enable easy way to stop any task, and to come back and continue it, (c) include some artifacts about each task such as: task history and task bookmarks, (d) users can annotate webpage while performing their tasks, (e) tasks can be shared with other users. With that in mind, they developed a prototype of a browser called: TabFour. Due to their short implementation time, they did not include all of their design requirements in this prototype. To validate their requirements and design, they conducted a study on 8 subjects to check if their designed prototype is suitable. In their short conclusion, they indicated that experiment users reported that this type of browsers indicated that this browser was useful to them.
In relation to [ref], this paper indicated the [ref] as a previous study which comes handy in studying web users, however for this study they elicit design requirements for an existing problem from browser users, then they used these requirements to built a prototype which lead to an experiment similar to the one at [ref] in order to validate their work.
Mohan Raj Rajamanickam, Russell MacKenzie, Billy Lam, and Tao Su. 2010. A task-focused approach to support sharing and interruption recovery in web browsers. In Proceedings of the 28th of the international conference extended abstracts on Human factors in computing systems(CHI EA '10). ACM, New York, NY, USA, 4345-4350.
In this paper, authors developed a task-oriented mobile web browser on an iphone. They relay on a previous study which state that most web users leave the browser without finishing their task. Thus, they argue that when a user return back to browser the current techniques such as: history and bookmarks, do not provide good information about what was the task and what was done.
First, they conducted semi-structured interviews with 9 students (aged between 18-29), with different browsing skill sets. They discussed that most of the participants do not use browser's history and bookmarks, but they havely use the autocomplete features, and multiple tabs. Participants often use some sort of annotation or text files to save their task state before leaving computer. They use these techniques to help them when they return back to their tasks.
As a reslt of their semi-structured interviews, authors have concluded their prospect browser design to contain the following features: (a) group multi webpages under one task, (b) enable easy way to stop any task, and to come back and continue it, (c) include some artifacts about each task such as: task history and task bookmarks, (d) users can annotate webpage while performing their tasks, (e) tasks can be shared with other users. With that in mind, they developed a prototype of a browser called: TabFour. Due to their short implementation time, they did not include all of their design requirements in this prototype. To validate their requirements and design, they conducted a study on 8 subjects to check if their designed prototype is suitable. In their short conclusion, they indicated that experiment users reported that this type of browsers indicated that this browser was useful to them.
In relation to [ref], this paper indicated the [ref] as a previous study which comes handy in studying web users, however for this study they elicit design requirements for an existing problem from browser users, then they used these requirements to built a prototype which lead to an experiment similar to the one at [ref] in order to validate their work.
No comments:
Post a Comment