Pay EXTRA close attention to what you are paginating. Sometimes a
big-ol-list of items page after page is the wrong fit. In the app I
am working on, for example, there is a big old list of all the
articles released in the last forever. The obvious thing to do was to
paginate them into 10 or 20
Also keep in mind your sort options. If a very large result set is
returned and users are unable to adequately refine or sort, I've
often seem them jump to a middle page to see if that is closer to
their desired pinpoint. We often see this on real estate sites where
customers have
...@lists.interactiondesigners.com] On Behalf Of Erin
Walsh
Sent: Monday, January 04, 2010 7:31 AM
To: IXDA list
Subject: Re: [IxDA Discuss] Search Results Pagination (top bottom?)
Also keep in mind your sort options. If a very large result set is
returned and users are unable to adequately refine or sort
Information Systems
-Original Message-
From: discuss-boun...@lists.interactiondesigners.com
[mailto:discuss-boun...@lists.interactiondesigners.com] On Behalf Of Erin
Walsh
Sent: Monday, January 04, 2010 7:31 AM
To: IXDA list
Subject: Re: [IxDA Discuss] Search Results Pagination
I'd generally agree that real estate at the top of the page tends to be too
valuable to spend on pagination.
Some points:
- In e-commerce, pagination tends to be used to a greater degree than the
low/1% stat from web search
- The #1 use case I've seen for top of page pagination, while
Our site has a lot of data and I have Search on the top of the page
and pagination only at the bottom. The reason for doing this was that
the search on the top searches for alphanumeric characters across all
the columns and shrinks the numbers of row to have corresponding
value. Now, if this the
Don't forget about the case in which people are scanning a list or grid, but
after scanning down to the bottom, they decide to go back and review items
higher up in the list.
In this case - which I have seen play out many times in utesting of web-based
apps - doubling up the pagination and
I see. So the user who scrolls down, and then scrolls back up, would not have
to scroll back down again if he decided to see the next page of results,
provided the pagination were duplicated at the top.
I think in order to make this design decision I would need to measure the
clutter/scroll
Off the cuff I can think of a couple ways to operationalize a quick test.
But honestly, I probably wouldn't test it. There are plenty of good pagination
design patterns in the wild that wouldn't add any significant clutter.
-Paul
- - - - - - -
Paul Sherman, Principal, ShermanUX
User
