I have encountered the following problem several times at my current job as a IxD-er without finding a satisfying solution:
"What to do when a search is executed with no input, thus an empty search query?" Concretely, this means hitting the search button next to an empty text field.
I am doubting whether this should show all results, especially if you have some filters (think of genre for music for example), or no results at all. In the latter case, an extra <return all results> button or something of the kind could be used.
Is it good practice to display Search as a prominent function on a Blogging
I'm of the opinion that search should be tucked away in a corner for users
who really want to use it, as I feel that most users would tend to browse
and not search on this site.
Are there any rules regarding the display of the Search function?
My team and I are currently designing a desktop application that
contains a search. I have been trying to find out what the magic number
is for displaying search results before the user finally gives up and
enters more criteria to narrow the results. More than likely, these
users know exactly what they are searching for and probably would not
return a list of 10,000 results, but we have decided that we wouldn't
prevent them from doing this.
Our current solution is to display "x" number of results, but inform
them that "x" was found. Does anyone know the magic #?
I'm putting together a UI that enables people to search for alternates and
replacement items. The main use case is:
"I have item X - show me if it is valid. If not, show me the alternatives".
Does anyone have any good examples of online (web apps) that deal with this
nicely from a UI perspective?
The trick here, to me, is that the UI needs to clearly show that the
original item (the one the person searched for) is or isn't valid. If it
isn't valid, displaying the alternatives in a clear manner.
There are some other minor constraints that I'm dealing with as well...
Keyword search is lousy when you're exploring an entire category.
Faceted navigation is pretty nice -- when it exists for the data
you're interested in. Finding items when you need to express a few
different requirements at the same time is... well, a disaster. We
need better tools for browsing and comparing.
Can anyone point to examples of sites or applications that you feel
do a good job at supporting this type of behavior? Got any thoughts
on what would characterize a search/browse engine of this sort?