Tag Info

Hot answers tagged

215

It's no longer necessary to paginate for users, but content providers love it for advertising. Common knowledge among content strategists in my work is that you paginate in order to increase advertising impressions. A slideshow with ten slides gets ten times the impressions as an article with ten photos. And an article with three pages gets … well, you get ...


108

Exactly, I think this particular type of pagination caused me confusions lot of times. However Its already adapted by the population. I'ld suggest something like below So what really happening here is - Its clearly making Previous / Next very prominent and not causing any confusion. In page numbers three dots (...) followed by last two page numbers ...


92

I'm all against pagination on articles for two main reasons: If you paginate content like it was a book page just because it has a specific height, you end up with content that has to be clicked through in order to consume. That is several not very useful steps putting extra effort on the user - for no reason at all. If you need to hide content because of ...


89

What problem are you solving with this? This seems like a developer's solution to a problem they think exists. Let's actually look at how users use pages. They want to go to: a specific page the first page the last page a specific item held within one of the pages going to the next or previous page (oops, forgot that, thanks 3nafish) Jumping 10 pages ...


67

Etsy spent quite some time developing and testing infinite scroll in their search listings. They noticed fewer clicks on results and fewer items favourited from the infinite results page, and users stopped using the search interface to find products. They reverted back to traditional pagination. There's a good article about it here: ...


45

Paging should be used to break content into semantic or task-related groups of content, such as by your categories in your menu bar on the left. This allows users to find content by what it is (e.g., the page title in a menu) rather than where it is (e.g., page number or relative position in a scrolling page). Generally user tasks depend on what (“I need to ...


41

How about just showing the last 10 years of awards with the 11th tab to take you to the previous 10 years? 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | ... | Older Most people are only going to be interested in the most recent awards, so having the older awards a second click away shouldn't be a big problem. Clicking on "Older" would show a page with the ...


32

Don't forget that some users want to print some articles. Pagination, of course, makes this a royal bother. To provide this feature, some sites put a link to an un-paged view on the article, but there will always be some poor users who don't find that link or don't even know to look for it.


31

If you really want to provide a possibility to choose any page from even 3000, there is an old soulution from karaboz. The idea is to make a page choosing like a scroll bar. For example, how it looks for 50 pages: You can move the scroll pointer (gray) very fast to reach a group of pages you really need at this momet. The orange marker - page wich is ...


30

The accepted UX terminology for this pattern is "infinite scrolling". It's becoming more and more common in rich web apps because it's a way to keep users engaged with a minimum number of roadblocks. The accepted viewpoint is that users prefer single page versions of content when given the choice (Google's own research backs this up), but that it's ...


25

The text should largely depend on the actual content itself. Is it time sensitive, like news, or is it content that will be relevant no matter when it is viewed? If it's time sensitive, it makes sense to use older/newer. If it's not time sensitive, previous/next seems like a better fit. However, I would argue that adding page numbers would increase the ...


23

[ Load More ] is certainly more "friendly" than a set pagination links, but there is no indication of how much more data there is that could be viewed, unless you add something else that gives that information - assuming it's available. If you don't know the total number of matches (thanks @Erics) then [ Load More ] is ideal. So, is it important for the ...


22

In short - it's appropriate when the main use case of the page is "light browsing", such as in Flickriver, when sharing (email, etc.) only one thing on the page is irrelevant and when SEO matters less. When I say "light browsing" I mean the user is basically just scrolling, looking for interesting things, without the need to commit or return to a specific ...


22

Booking.com experimented with it, conversion dropped immensely. Everything they do there is A/B-tested. I wish I could share statistics, but those are documented internally so you'll just have to take this anecdotal evidence for what it is: something a guy on the internet posted. That said, the reason no large e-commerce websites use it means that it ...


20

This may or may not be pagination done right, but here is how I do pagination in my web app: |< First, << Previous, Page [5] of 12, Next >>, Last >| The outer four options are links, while the Page [5] of 12 is a form, with the [5] as an input field. For users with JavaScript enabled, I hide the submit button and submit the form on the ...


20

Why not try some variation of the following (crude) sketch, with the circle indicating a touch point and the arrow a swipe?


19

Paging through lists or tables has always struck me as an awkward pre-GUI throwback necessitated by the limited bandwidth of the early web. Scrolling is generally superior to paging, providing more convenience, flexibility, and feedback to the user; plus it’s more standardized. I generally recommend loading all of a list into a page or scrollable pane ...


17

Maybe an approach... Show the user in page indicator under the list, there a more items available. The beneficial: the arrangement corresponds with user mental model and user sees the current page.


17

Pagination with select list When there is a manageable number of pages: Shows the current page number (selected attribute of option) Shows the last page number after one click (could also be added next to the select list if it’s important) Allows to jump directly to any page (including first and last) No confusing two sets of buttons (first/last and ...


17

Except for few edge cases, I think pagination itself is a bad idea. Question: How would a user know that there is an interesting cat picture in post 3 of page 1534? They don't. Users requiring to access a specific page is a non-existing requirement in common forum formats. What users want is to skip those noisy posts ("Great post", "WOW", "LOL", "Thanks"), ...


15

No. The amount of results per page should depend on: The display size of each result - the smaller the result the more you should show per page e.g. from small to large: thumbnail, one line, multi line, large image, ... The window size - the larger the user's window is (or device's screen if in fullscreen mode) the more results you should show. Showing 10 ...


13

I have the same opinion as you: I am not fond of infinite scroll. Tough, with time, this might change. In his blog post The End of Pagination, Jeff Atwood makes the point that Above all else, you should strive to make pagination irrelevant because the user never has to look at more than a few items to find what they need This satement does not quite holds ...


13

I like the textbox idea but I also see the point that people need to press enter and some might not get it. Maybe you can build a prototype and test it? The point about an SEO disadvantage due to less internal linking is also a valid one. However, I would add the number of total pages to your solution as users should know which page they can go to: ...


13

SURL did some research back in 2003 on this, in an article called "The Impact of Paging vs. Scrolling on Reading Online Text Passages" The findings from this study show that participants using the paging condition took significantly longer to read the passages than either the full or scrolling conditions. Participants also showed no significant ...


13

Disclaimer: I am not a native speaker of a language which does use guillemets as a way to denote quotes. But I wanted to offer a view on how context can help identify if the content being referenced is a phrase or a case of pagination I believe there are two aspects to it I believe this is one of those cases where users can visualize whether a phrase ...


12

Using the back/forward buttons shouldn't be an issue for a good implementation of continuous scrolling. It's possible to mitigate the issue by updating the URL fragment as you go. For example as I scroll down in forrst.com I go from: to giving URLs that work with back buttons.


11

You could have a '...' tab and use some JavaScript (yay jQuery) to "scroll" to the right when you click it and reveal the other tabs. Then you could have an arrow on the left so you can go back to the newer tabs. (TY @ChrisF for the inspiration)


11

I'd break them into three pages, but not because of scrolling. Scrolling is not a problem. Having 30-40 fields thrown at you all at once is intimidating, it creates an immediate overload that may scare users off. Dealing with them one group at a time is much easier.


10

The highest voted answer in the question linked to by the other answer suggests collapsing all the page links into an input field. I've seen this, but scrolling a list and clicking a page number is a mouse-oriented activity, so I've never been inclined to switch to the keyboard to enter a page number. Perhaps the input could be a super-input that takes text ...


10

I think pagination is another one of these cases where a good default value makes all the difference, and - as Amazon and Google show - it's then even possible to keep the burden of choice from your users altogether. In my opinion, a selectable value for the number of items per page really only makes sense if that one page contains multiple conflicting ...



Only top voted, non community-wiki answers of a minimum length are eligible