Infinite scroll has its uses, but a search result page is not one of them. Infinite scroll relies on discovery and exploration. This works well for when you're not looking for anything in particular; when you're sifting through a massive amount of data until you find something that hooks your interest. This format lends itself extremely well for social media ...
There is no official statement regarding this, so no one can give you a 100% accurate answer.
One of the biggest reasons might be the ad placement of Google.
They earn money with every search, and since they use pagination they can even earn money multiple times with only one search, try it yourself.
For example if you search for "toaster" (in Germany), ...
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 ...
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 ...
Since no one posted it yet, to me the main reason against infinite scrolling is shown in this XKCD comic:
The tool tip reads:
Maybe we should give up on the whole idea of a 'back' button. 'Show me that thing I was looking at a moment ago' might just be too complicated an idea for the modern web.
Here is the Explain XKCD page for the ...
For this situation you can use an empty state which can be just text or a graphic with text and an action button.
Example of an empty state from Product Hunt:
Good empty states will give the users an action button which can push them in the right direction. A button with something like "Rephrase your search" might work in this case.
It doesn't make ...
Infinite scroll has the added downside of hiding the ...
There's a very simple reason for this: you want users to know there is an end to the amount of data they are shown. Humans have a need for closure and control, and the Last button helps with that; along with the First button, it marks a clear beginning and end.
Now, whether a First or Last button will serve as more than just an overview marker, will depend ...
Order of data transformation
As explained in Sorting a Paginated Record Set User Experience Expectation, and as illustrated there by the following order of data transformations:
You can see that both filtering and sorting come before pagination.
This means that whenever the order changes (sort), you should repaginate.
Back to page one?
Whether or not ...
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 ...
Both solutions have their pros and cons.
Pro: Users can easily orient where they are and go back directly to the page they were before in cases like: browser restarts, swictching from device to device etc. ("John, I have found some interesting ads, gone through the first five pages of them, can you continue, darling?")
Con: a lot of them will ...
I would hide Showing "0 results from 0 results".
Instead I would add in place a Blank State image with a button for the user to add data. ( If the user adds the data ).
Displaying a pagination where there are no results is purely an artefact of a not so good UX.
Allow the user to see how many are selected, and give them the option to select the whole data set beyond the pagination.
Gmail has this pattern. Once you select 'All' via the checkbox, a message appears stating:
How many are currently selected
A link with the number of the whole data set, and the ability to select the entire set
You didn't really describe your exact use case, but I can share some uses I see for the "last" button, and I hope these are helpful to your particular needs:
In many forums, there are massive, multi-year threads that span hundreds of pages. Often times, facts and available information change over these years, and what was correct and accurate when ...
Except for few edge cases, I think pagination is a bad idea, especially when it comes to forums.
Edit: Looking back at this after 4 years! Now infinite scrolling (I called it dynamic loading) seems to be the go-to solution for modern apps. Case in point: Reddit.
Question: How would a user know that there is an interesting cat picture in post 3 of page ...
Pagination works better for several reasons:
Because the resulting HTML isn't complete, some browsers display NOTHING, while others display what comes back. So, browser compatibility would be one reason.
Because with pagination, Google can place sponsored ads at the top of each page; with infinite scrolling, that's more complicated to do
Because with ...
For completeness, there's a canonical bad solution to this that is extremely common: quietly (maybe even silently) generalize the user's query until the set of results is non-empty, and show them results that they weren't looking for. Sometimes this takes the form of guessing at other searches they might have meant, Other times it's just putting ...
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 prev/...
Keeping the page number after changing the order makes no sense. The page number is the same but the page isn't, let alone that going back or forth between pages lost the idea of coordination. What use would that have for the user? If you test this on real users you can expect them to be confused by this. They probably expect to see the first result on page ...
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 is ...
The simplest way would be to let the user know that new content is available. These can be found in many different applications that dynamically load new content. For example say, the user has scrolled down a couple of times in an application with infinite scroll you can do something like this,
For paginated applications, consider not updating content in ...
Google is already testing progressive load...
Google loads content progressively on Google images, but they don't do that on web results. There are many reasons for this, as already mentioned in other answers, but the most likely reason is to provide control to users
Think about this: I know I saw that interesting results on Page2 is way better than "I ...
Google follows both models; pagination and progressive loading at the same time but for different pages.
e.g. for images like here, you can see that there is progressive loading and after a certain moment, a CTA saying "Show more results" come which can show the other set of results but when you search in general like this then after a certain points, ...
I often type in the URL bar so that I can go directly to the page I want. An input box letting the user type the direct page would be a great boost in UX and usability.
You can make the current page number (the one that shows as active) turn contenteditable when clicked (make sure to auto-highlight) and let the user type a number and hit Enter. You can also ...
I suggest you go with Infinite Scrolling because we see it ourselves everyday that the number of times we click on the page 2 of Google Search.
When we don't find what we are looking for on page 1 - we simply change the search keyword. But that doesn't happen with Facebook, we just keep scrolling down and down and suddenly realize we are spending too much ...
I'm sorry not to answer your question directly, but I'm actually quite alarmed by the the whole idea...
So your friend has decided to put high-school teenagers through the torture of having to answer 160 questions? Does he or she has any idea how cognitively demanding such a task may be?
(PS, to get a faint feel for it - please go ahead to the ...
Convert the current page indicator into the input field.
Similar to Adobe Acrobat (see pic)
Adobe Acrobat Page Navigation
Then distinctively style the page number and prev/next buttons differently to this input field to make the input field stand out as such.
Use a style for the buttons that differentiates them even more from the input ...
Previous answers cover the human perspective, but there are also lots of non-human bots and webcrawlers that browse paginated websites.
The bot for the crawling project I am personally working on relies on those links to the last page, since it works like this:
Given a list of URLs for articles, download the first page of each.
In each loaded page, look ...