Timeline for Should I redirect the user if there's only one search result, or still show the results list?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:51 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jun 25, 2015 at 15:33 | comment | added | plainclothes | @Niavlys 1) More is not necessarily better, but letting the user know about related results often is. Take them to the results they asked for, but let them know that there's more in the system. 2) You also have to be careful about changing the pattern. If the user doesn't come to your system daily (or more), variations of a flow can cause confusion and disorientation. In the case of a movie database, redirecting may seem easy, but are users more likely to be irritated by the extra click or caught off guard by the change in flow. That's what testing it for. | |
| Jun 25, 2015 at 15:12 | comment | added | sylbru | “The system knows, for example, that if they would only have changed one word in the search, they'd get 5x the results.” Do you mean the more results the user gets, the better? I figured it's better to give them what they searched for, not 5x more. If they typed the exact name of a movie, isn't it better to have them directed instantly to the page dedicated to the movie (in the case of a movie database), instead of displaying a result page consisting of one line? The page could possibly include a line of text indicating "we redirected you here because there was only one result." | |
| Apr 20, 2015 at 16:23 | history | answered | plainclothes | CC BY-SA 3.0 |