Letting the user know that there's not much useful information found is useful information.
If you don't show the search results list in case there's only one result, you save the user some time – but I doubt the user will actually appreciate it. The user basically doesn't know whether there's only one result – or if there's an inconsistency in how the ...
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 ...
Do not auto-redirect user. Remember to let the user have the control on your sites. Make them the ruler of your site.
The user might also want to revise their search terms. As a user, when I tried to search for common items and got 1 result, I might feel something wrong with my search terms. I would tried to generalize the search terms.
On another case, ...
Consistency is important in UX
This is a general principle but it's especially true for consumer-facing sites where users may be new or have varying levels of familiarity.
In real life, when you open your fridge to start cooking you expect to see food inside. It's confusing and cognitively dissonant if you open your fridge a second time and see a stovetop ...
There is a question you need to answer (which can be stated in different ways):
How big is your dataset?
Is "everything" a finite set?
Is it sensible that the user might want to see everything?
If your dataset is small or finite, or it's sensible that the user would be able to deal with everything, then you could return everything.
If your dataset is ...
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 ...
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/...
I vote for option #4.
A search from the main page should show mostly videos and a few pictures to hint to the user that there may be more content types on the site than they realize.
If they're searching from a picture page, show mostly pictures but a few related videos as well.
download bmml source – Wireframes created with Balsamiq Mockups
I did a quick check on how Google and Bing handle this and their flow is to just ignore the search request if there is no search value entered and keep the user in the same page.
While that does make sense since the user might be confused if search results are contrary to what he expected and if he gets some random results he might be confused as in his ...
There are two psychological key aspects that are in play when it comes to this matter.
Users want to feel as they are in control
Users (people) want the ability to choose
The I'm feeling lucky feature does not cater to either of these aspects.
It is true that the user and the SEO will agree on the most suiting search result on a majority of the time. ...
Things are given numbers largely for two reasons: so that they can be referred to or so that they can be counted. In short, the reason Google (and all other major search engines) don't number individual entries is that it's largely meaningless extraneous information.
Part of the interest of the first style of numbering system is that the thing the number ...
TL;DR: Use a multi factor ranking system.
A good example to follow is the way that Google rank search results. We of course don't know the precise details of their ranking algorithm, but they have arguably done the most research on this and have the most success. What we do know for sure is that Google include a large number of factors and apply a ...
It also depends on the kind of search, for example if the user is searching for a customer number in a CRM. When entering that number while on the phone with a customer, the number is unique and the user expects one match. He/she will probably find the result list redundant. A partial number may return the search list for further exploration.
If the application is for providing exact items for which users may know the title, redirect to the item but provide a means to show the full search results.
Wikipedia does this if you search for an article with the exact name of your query unless you navigate to the full search results. This is useful because the user will most likely want to visit that ...
A search should ALWAYS end up in a search result page no matter if it's a structured results or actionable results. This is standard behavior on all available search engines whether it’s online or in an application.
However, you have the possibility to display the search results in different ways, as in this example of Actionable Results Illustrated.
This sounds like a composite of two patterns. It's not a hybrid, borrowing some aspects from autocomplete and some from federated search; it's nothing more or less than auto-complete and federated search used together. Therefore I think your calling out the existing patterns is preferable to using a unique name, even if someone has already coined one.
When you consider that much effort (hopefully) goes into the design of other pages on the website, it's wrong to think that the search engine results page (SERP) should receive any less love.
There are several steps at which the zero SERP can be avoided or improved.
The first point of prevention is at the query formulation using as-you-type suggestions, ...
Moving to more human-like computer system, you could give to the system some human features:
Politeness -- don't make use blame himself of his error (this effect is described by D.Norman in The Design of Everyday Things). Just point it gently.
Forgiveness -- both computers and humans make errors. Forgive the user and he will forgive the system's error once. ...
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 ...
If you're referring to the UK postcode areas, then according to https://www.mjt.me.uk/posts/falsehoods-programmers-believe-about-addresses/ Warwick University has a single postcode of CV4 7AL which refers to 6,000 students. It also gives a French postcode of 75015, referring to 230,000 people.
Forces' BFPO numbers are a single postcode, so a single aircraft ...
We can use common sense to answer this question. Let's say you put pagination on the top of your SERP and it has 6 results, only 3 of which fit above the fold. This is the first SERP page:
| 1 2 3 4 5 6 7 |
| Result 1 |
| Result 2 |
| Result 3 |
. Result 4 .
. Result 5 .
. Result ...
It's generally accepted that most searches are for navigation purposes, rather than discovering content; here's some recent data by Google on this. One key factor here is whether the user already knows that there is only one relevant endpoint.
For example, if users search for a Ticket ID in a defect tracker like Apache Bloodhound, they likely already know ...
You can use a Search Thesaurus, which basically is predefined synonymes stored in your search engine. So if the user search for programmer, your thesaurus should translate this to search for "developers" and "coders" as well.
The real problem here is to find out which terms your target audience use. The best option here is to look through your search ...
It is almost always better to both (a) cut out unnecessary steps, and (b) immediately show the user results of an action. Automatically filtering results when the user clicks a check box does both of these things, and having a "Filter" button does not, so the first design is better. Of course, it should also be easy for the user to undo or change the ...
The convention on search result pages is to present the actual content looking almost the same. The reason behind it is that's it easier to scan content and find keywords representing the thing the user is searching for.
Filtering search shouldn't be done in the actual result list but in a faceted navigation tool to the left of the search result listing.
Frankly, this is contextual. For a single word, generally 2-4 letters are kept as minimum to initiate the auto complete feature. There are at least two reasons for this.
One being the performance as you pointed out. There is no need to fire up a filtering call when you know that the resultant dataset will be huge.
Second being, the number of results you ...
For questions like this, especially around customer experience in e-commerce, I sometimes try to imagine the situation as it might occur in the brick-and-mortar world.
In an actual shop, would you ask your customers to stare at a wall until they told you what they were looking for? Of course not.
Customers want to browse.
Informing users what's going on is never wrong. Assuming that we’re within time limit (<100 ms) and do not need to do anything is always wrong.
How can you tell how long it takes for user X to download content Y from your site Z at any given moment? There must be at least 200 unknown variables here that you do not have control over. That’s the reason we ...