Tag Info

New answers tagged

1

As an addition to Igor-G's answer. In my opinion, the best way to solve the problem of (1) not loading too much content at once and (2) not having to tap the 'next page' button multiple times, you should lazy load the content. To allow your users to get to the bottom of the page, you can just place a (preferably big) 'load more content' button to ...


1

You might consider using a drop-down menu (AKA a pop-up menu). This gives a quick indication of the size of the result-set, as well as allowing the user to jump to the first, last, and any interim page, with reasonable ease. This is from http://www.edinburghbicycle.com/browse/clothing/mens-clothing In user testing, I found the most important thing was ...


1

My main concern with your approach is scalability. How many pages of search results will there be? Consider how scroll bars work, and see if your solution will scale as well as they do. To use an example, let's assume we're using Microsoft Word on a desktop computer without a touchscreen. When scrolling through a long document, you have a lot of ...


0

I do it like this The ↻ is for refresh the current page first ⇚10 ⇐ ↻ ⇒ 10⇛ last


0

Keep the arrows for increment by 1, use a slider that increments by 10 for quicker navigation. Once the value in slider is selected the values above readjust accordingly. download bmml source – Wireframes created with Balsamiq Mockups


1

This will be confusing for most users, the arrow is commonly used to go back 1 page or go forward 1 page, i think it is indeed better to say something like +10 or -10 if you really want a user to be able to jump 10 pages. However as discussed in the following thread it's most likely not needed for users to be able to jump a certain amount of pages. ...


1

In your example, you could have buttons for page 1 and page 25. Perhaps add ellipsis in between to emphasize the gap. Here's a close example:


2

I also feel that the user needs to be able to reach the page that he wants to with the least possible number of steps. fibonacci numbers are cool but the least possible number of steps is by getting the number of the page that the user wants and jump there. If I know that something is in page 1512, I'd rather do that than play binary search with ...


26

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 ...


2

That may be a good idea if you assume that a user want to move to pages, possibly jumping. But still, it does not have to be a Fibonacci sequence. You can have a logarithmic scale of any base. But actually in the first place, I don't think any buttons of the kind other than "previous" and "next" (or equivalents) would make any sense. If users had a ...


15

Except for few edge cases, I think pagination itself is a bad idea. 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. What users want is to skip those noisy posts ("Great post", "WOW", "LOL", "Thanks"), and (hopefully) get to that cat ...


2

Taking a page from the our usual video player, a 'fast-forward' and 'fast-rewind' button can be added for faster navigation through the pages. But Fibonacci? Doesn't make any sense to me.


4

I think it stops after the cool factor. It's one of those "just because you can, doesn't mean you should" type of situations. It's best to follow what's conventional. Jumping ten steps forward or backwards is most common (after moving one, of course). I would think the next large number to move through multiple pages would be a common number we jump to in ...


2

It's an interesting idea, but the use of the Fibonacci sequence seems fairly arbitrary. With the assumption that the user wants to find a specific item that is positioned uniformly across the pages, and they know about the rank order of the item, the most efficient algorithm would be a binary search algorithm. So, it would be more suitable to use the ...


5

This is an issue of scaling, which is a common problem in data visualisation :) Your Y axis has data (page numbers), and ideally you would want to display all of it at once - but that won't fit, so you scale it. We scale by log(10) usually, because it is one of the easiest transformations for people to conceptualise - but you could go by any scaling ...


1

An interesting idea for sure, but if you plan to have hundreds or thousands of pages, browsing through all of them will probably be an unpleasant experience regardless. The cynic in me believes the creator's use case was showcasing the ability to solve a common programming challenge in writing an algorithm that prints the Fibonacci sequence.


79

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 ...


2

Yes, you should show them the data from the top (page 1). Assuming the user has looked at all rows up to say page 3. They couldn't find what they were looking for and decided to re-sort. There's no way to know in the new sort order as to whether data in the first 2 pages have been reviewed. In fact, because you changed the sort order, the assumption is ...


0

I like the approach of the http://www.kuantokusta.pt/ site: do not have first or last buttons at all. You can see it if you do a search, or I can give you the link of an exemple search: http://www.kuantokusta.pt/search?q=ténis&pag=11 . If you scroll to bottom, you will see every page number as a rounded rectangle around it, making them appear as more ...



Top 50 recent answers are included