Re: [IxDA Discuss] Pagination best practices
I'm seeing more implementations of a more button rather than pagination controls. http://projects.nytimes.com/survival-strategies is a nice example of X more items. Notice how it adds just ten more items at a time and requires a button push, but adds content to the page, rather than moving you to another page. - Fredrik Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
BTW, the Continuous Scroll discussion from January 2008 also contains a number of great suggestions for and examples of scrolling-vs-pagination. → http://www.ixda.org/discuss.php?post=25287 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
Depending on how much text is displayed, users may use the browser's search (it's 'Find' in Firefox) to find an exact keyword in a list of results, therefore a the more information per page is better. Ancestry.com is another site that allows the user to choose how many results to display per page. The default is 50, but can be changed to 10 or 20. I also agree with Evan K. Stone about RSI. Minimize clicks and I'm happy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
An additional advantage of continuous scrolling is that we get to stay focused on what we're looking for, rather than fumble with the keyboard. Evan pointed out the challenges of RSI, but as the universal design adage goes, what works well for those with physical disabilities or injuries works even better for the rest of us. When using continuous scrolling, however, it's important to offer an easy way of getting at navigational elements. Google Reader has a left menu, others place a menu or menu shortcut at the top, etc. If you have a search interface with lots of filters or facets, you'll face height problems cramming them all in on the left hand, etc, but this can be solved decently in most cases. For those of you who enjoy continuous scrolling, http://autopager.teesoft.info/index.html offers a great Firefox plugin that enables continuous scrolling at most sites. - Fredrik Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
That is a great site. Thanks for sharing. (I like the surprise of different facets in the search box as well) Courtney -Original Message- From: discuss-boun...@lists.interactiondesigners.com [mailto:discuss-boun...@lists.interactiondesigners.com] On Behalf Of William Brall Sent: Tuesday, May 12, 2009 3:05 PM To: disc...@ixda.org Subject: Re: [IxDA Discuss] Pagination best practices http://search.ahp.us.army.mil/search/slideshows/ I'd like to say we did a decent job with army.mil's pagination. I would have liked the tabs to be larger, along with the clickable area. I would have liked to color the clickable items more obviously. I would have liked to omit the last link on the actual searches. (Google Search Appliances guess at the total number of pages... Making the last button very very broken) Thankfully, they also wanted a non-GSA based mode without a search. Which lets you see everything newest first. (Which the GSA also has trouble with) There are problems. But we were mindful to duplicate it at the top and bottom. Offer many number-per-page options, and the more savvy users will realize the URL tells them how many items per page and there is no limit to how many you want to get. Or the irrational numbers per page you might want to see for that matter... Over all I think we did well, just remember. Bigger. More obvious what is clickable. And don't include a last tab if you can't really predict a last page. Also. have not yet reached the point of ubiquity, or at least among people at the pentagon. But I think you can intuit what is happening once you try them. I'm a developer (And a contractor), so my sway on 'design' changes is limited. Will PS. Evan. I really like the idea of making the pagination keyboard accessible. I may have just found the next pet project for myself. :) Thanks! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
Rightmove (www.rightmove.co.uk) has applied a nice jQuery slider to their pagination nav at the bottom of their results page. See the UI here: http://www.flickr.com/photos/niklazell/3512730552/ Nik Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
An even more elegant version of a scrollable paginator can be found at www.designyoutrust.com The advantage of scrollable paginators is that you're free to move to any page at any time with a tolerable amount of effort. The Flickr paginator, for example, introduces quite a bit of complexity when you're on page 47 of 200 and want to skip to page 109 (unless you're clever and use the REST-y URL :-) It's worth remembering that pagination is an *arbitrary* chunking mechanism. It might be more interesting to use facets or filters to chop the result set into more manageable chunks. - Fredrik Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
However, when I tried Google's 10, 20, 30, 50, 100 results preferences, it was much easier for me to scan through 10 results, didn't require as much scrolling (which is painful to people with repetitive stress injuries, fibromyalgia, arthritis, etc.), Speaking as someone with RSI problems, I'd WYY rather scroll rather than paginate. Pagination is Pure Evil for me, and it is _much_ easier for me to Page Up/Down in a scrollable region than to attempt to line up my cursor with every page and click a next button (if it's even visible to begin with, which means you're back to scrolling AND wrestling with pages...).* The one exception to that is when the list fits exactly in a screen's worth of browser real estate (i.e. above the fold), and a Next button is consistently in the same spot every time and I don't have to move my mouse pointer (i.e. it just _happens_ to be on the same spot every time where the Next button resides). That situation is generally pretty exciting to me, and it is also... extremely... rare. So, if I can adjust a list to display 100+ items I'll do it! Here's an even better example, however: Google Reader. Its infinite scrolling** is awesome: it just loads up new items when it needs them. Awesome! ...and since it's pretty easy to get an enormous list of RSS feed entries (especially if you go away on vacation for a couple of days! ;), GR's mode of scrolling is very effective for me. Obviously, this is just how it affects me in _my_ particular case, and YMMV. HTH. ///eks * This got me thinking just now... perhaps linking Page Up and Page Down keys to previous and next (or the reater than/less than keys since they *look* like prev/next arrows) would be a nice way to enhance pagination? Anyone already doing either of these interactions on the web? ** If Google Reader has a scrolling limit, I haven't encountered it. They seem to employ a similar concept of Google Maps' map scrolling to a list of data. Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
http://search.ahp.us.army.mil/search/slideshows/ I'd like to say we did a decent job with army.mil's pagination. I would have liked the tabs to be larger, along with the clickable area. I would have liked to color the clickable items more obviously. I would have liked to omit the last link on the actual searches. (Google Search Appliances guess at the total number of pages... Making the last button very very broken) Thankfully, they also wanted a non-GSA based mode without a search. Which lets you see everything newest first. (Which the GSA also has trouble with) There are problems. But we were mindful to duplicate it at the top and bottom. Offer many number-per-page options, and the more savvy users will realize the URL tells them how many items per page and there is no limit to how many you want to get. Or the irrational numbers per page you might want to see for that matter... Over all I think we did well, just remember. Bigger. More obvious what is clickable. And don't include a last tab if you can't really predict a last page. Also. have not yet reached the point of ubiquity, or at least among people at the pentagon. But I think you can intuit what is happening once you try them. I'm a developer (And a contractor), so my sway on 'design' changes is limited. Will PS. Evan. I really like the idea of making the pagination keyboard accessible. I may have just found the next pet project for myself. :) Thanks! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Pagination best practices
Can anyone recommend resources (or offer advice) addressing how best to paginate data on the web? Specifically looking for info on when to paginate and how many items to show per page. There may have been a time when retrieving more than 10 items from your database at a time was too much of a load, but there's no technical reason why we can't show the user 100+ items per page. Is it easier for the user to click next 10 times, rather than scroll down a long list? Thanks in advance, Jonathan Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
http://kurafire.net/log/archive/2007/06/22/pagination-101 -mo- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
In theory, I prefer scanning a longer list to clicking next 10 times, as it seems like it would take less time and it gives you a better overall picture. However, when I tried Google's 10, 20, 30, 50, 100 results preferences, it was much easier for me to scan through 10 results, didn't require as much scrolling (which is painful to people with repetitive stress injuries, fibromyalgia, arthritis, etc.), and made me feel like I was making progress, which I don't really feel when I'm scrolling through 50-100 results (I felt no difference in the length of time or frustration with either of these). So, in practice, although I am annoyed when I have to click next so soon, it gives my scrolling hand a break, which makes a big difference in how long I can continue searching. On the other hand, if I get 10 pages (100 results at 10 a page) into a google search, I've pretty much given up on finding whatever it is I'm looking for. What about just going Google's route and show 10 at first, for easy viewing and to reduce scrolling, especially for small displays, but let those advanced, oft-times younger users with faster hands, set their preference for # of results? Something like this: View 10 20 30 50 100 results per page, with 10 being bold black text as the default selection and the rest being blue underlined links Thanks, Courtney -Original Message- From: discuss-boun...@lists.interactiondesigners.com [mailto:discuss-boun...@lists.interactiondesigners.com] On Behalf Of Jonathan Abbett Sent: Monday, May 11, 2009 12:07 PM To: IXDA list Subject: [IxDA Discuss] Pagination best practices Can anyone recommend resources (or offer advice) addressing how best to paginate data on the web? Specifically looking for info on when to paginate and how many items to show per page. There may have been a time when retrieving more than 10 items from your database at a time was too much of a load, but there's no technical reason why we can't show the user 100+ items per page. Is it easier for the user to click next 10 times, rather than scroll down a long list? Thanks in advance, Jonathan Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
Hi Jonathan, If you're looking for some inspiration I've started a Flickr set ( http://www.flickr.com/photos/doos/sets/72157612901305343/) of various pagination styles and patterns from around the web. Good luck. -- Rob 2009/5/11 Jonathan Abbett jonat...@abbett.org Can anyone recommend resources (or offer advice) addressing how best to paginate data on the web? Specifically looking for info on when to paginate and how many items to show per page. There may have been a time when retrieving more than 10 items from your database at a time was too much of a load, but there's no technical reason why we can't show the user 100+ items per page. Is it easier for the user to click next 10 times, rather than scroll down a long list? Thanks in advance, Jonathan Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
Serverload is one thing to be taken into consideration - client load another. Depending on what you are displaying, some of the more run-of-the-mill clients (older laptops, older browsers, etc.) may have difficulties displaying a too large amount of search results - which means users have to wait, wait, wait. That's why I always found the 10 / 20 / 50 / 100 (or similar) option with 10 results as the default the most useful (the default of course depends on the type of search results - is you have videos, for some 10 may also be pushing the limit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
I think it depends on what the actual task is and what users need in order to make a choice. It might not serve you well to make a decision based on best practices and rules of thumb rather than actually addressing the particular set of assumptions and expectations at hand. -joanie -- Original Message -- Received: 09:06 AM PDT, 05/11/2009 From: Jonathan Abbett jonat...@abbett.org To: IXDA list disc...@ixda.org Subject: [IxDA Discuss] Pagination best practices Can anyone recommend resources (or offer advice) addressing how best to paginate data on the web? Specifically looking for info on when to paginate and how many items to show per page. There may have been a time when retrieving more than 10 items from your database at a time was too much of a load, but there's no technical reason why we can't show the user 100+ items per page. Is it easier for the user to click next 10 times, rather than scroll down a long list? Thanks in advance, Jonathan Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
Very weird-- was just asking about a pagination pattern on Twitter earlier. There's another concept, which it looks like we're calling inline pagination, in which our intrepid user clicks a Next 30 results button or link, and the items add to the current scrolling list. So instead of navigating back to the first set of results, they're right there in the scroll list. See Twitter's More Tweets feature (scroll to the bottom of your timeline page), as well as iPhone's load more SMS messages button while looking at lengthy SMS history. Just another pattern to add to the toolbox. Apparently Bill Scott and Theresa Neil cover this (thanx @ilowelife): http://is.gd/gmkc - Nasir Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
Hi Jonathan, I think it's important to consider the content of the page that you're paginating. If you're displaying thumbnails, it is easy enough for a visually inclined user to scroll through a large list and mentally keep track of what they are looking at. If you're scrolling through a ton of textual summaries however, it's going to be a lot harder for that user to keep track of what they're looking at, or even find what they're looking for. I like limiting the number of items per page to around 20. I think it's a good amount for a user to process and manage in their memory and it doesn't feel like you're clicking next every two seconds. Best of luck! - Kelly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
I am in the Tufte camp here around data density. Most pages are way too short with not enough data. There is no such thing as too much information; just badly designed information. Data is much easier to compare if it's within the same viewport - by requiring clicking to paginate, you remove the ability to compare as simply as you can with with scrolling (or reducing font size or other tricks to bring more of the current document into the viewport). So, I am a big fan of larger result sets. That said, I think there are arguments to be made about context - most people don't view past the first page (and even less the second page ) of search engine results. This is a different situation than say, comparing a table of portfolio stock positions where all of the rows tend to have meaning and add up to a larger picture. In the search engine situation, the user goals are different (help me navigate or answer what the temperature is right now - very concrete tasks). Phone books give a lot more than ten results per page - way higher data densities than more web pages. I think this is a good thing to think about (another Tufte-ism). I also don't entirely buy the accessibility arguments presented here (and I'm a big fan of universal design by the way). If you really need to paginate, there are ways to create keyboard shortcuts to facilitate scrolling and pagination. And, by putting more data on the page, you can put less interface on the page - that's almost always a good thing. Anyhow, that's my attempt at an answer which doesn't rely mostly on it depends! cheers! Brian www.rhythmspice.com Rhythmspice Media p.s. all this said, it depends. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
In my experience users prefer scrolling a long list over clicking through separate pages. If there's a reason for pagination, consider creating logical pages: instead of grouping per xx items, it might be useful to group the data -for example- per letter (A, B, C...), per month or per price category. If the user can change the sort order of the data, then the logical grouping will have to change according to the chosen sort order. - Yohan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Pagination best practices
I did some research on this a number of years ago - this began before Google became dominant in search which gives you an idea! Towards the end though, Google was a clear winner. I found, quite reliably, that many search engines satisficed and satisfied most user's needs within the first 10 links so there wasn't so much need to present many more. This depends upon a) how good a search engine is at extracting relevant information while leaving non-relevant information, and b) the information requirements of the user (is it a single, simple answer to a question like, what is the height of mount Everest; or is it more complex such as, what is the history of the Beano comic for which multiple sources may be needed for an answer that at least satisfices). This doesn't really answer your question as more information about the specific tasks is needed before any kind of practical answer can be provided. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41915 Welcome to the Interaction Design Association (IxDA)! To post to this list ... disc...@ixda.org Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
