CHI-WEB Archives

ACM SIGCHI WWW Human Factors (Open Discussion)


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Justizin <[log in to unmask]>
Reply To:
Mon, 21 May 2007 08:39:27 -0700
text/plain (47 lines)
On 5/21/07, Nikki Roberg <[log in to unmask]> wrote:
> Hello,
> I am currently working on a project in which a part of the interface will
> display search results. This part of the interface will take up about 1/4+
> of the screen (if that even matters).
> During a group walkthrough with potential users 50% wanted to be able to
> scroll through a long list of results and 50% wanted to have the results
> paginated with links to the next set of results.
> I'm wondering if anyone knows of any research (aside from Piolat, A.
> Roussey, J-Y., and Thunin, Olivier (1997)) that discusses this issue and/or
> shows that one presentation may be better than another? I would also be
> interested in other ways of implementing the design.

IMO no research can supercede user preference.  If you have a clear 50
/ 50 split you should consider:

  (a) developing a new meme which satisfies the root desire of each set of users
        ( ajax load-on-demand ? )

  (b) sending a paginated set at first, and allowing to select a full
scrollable set

  (c) sending the full set, but hiding most of it unless a user
selects to have it fully scrollable.  That is to say, you can paginate

In a web application, (b) will generally be faster and/or allowed to
run more times per second than simply giving a full data set, and it's
the first avenue I would investigate.

Justin Alan Ryan, Director, VonGogo Foundation
Independent Interactivity Architect, ACM SIGGRAPH

           Tip of the Day: Postings must be in plain text
     CHI-WEB: POSTINGS: mailto:[log in to unmask]
              MODERATORS: mailto:[log in to unmask]