New answers tagged search-results
The multiple search tools has considerable disadvantages: New users may not know where to go to search for what Repeatability of a search scenario will first mean that the returning user identifies which search tool to use One solution would be to improve the search input to inform users that they are searching for products, brick and mortar location, ...
Both - start with the singular search box, then add Advanced search interface if there is enough budget left. For Power Users, it should be possible to type advanced queries in the original search box as well, once they learn the syntax - so the advanced interface should automatically update the original box for people to be able to learn by practice..
I think option one is not really an option: making users switch between two languages while they are trying to come up with a good query is not such a good idea. It's better to present results in both languages at once, as you are suggesting in option two (and as Aprillion and other commenters agreed). I suggest two adjustments: not splitting the ...
There are good answers, I wanna add: trial and error. Probably you don't know so much your users to arrive a good solution at once. And for sure, we don't know neither your users nor your website. So, you could implement several solutions and made statistics. First, use beta testers. Then, implement changes gradually (for a growing number of users). ...
Enforcing one language on an element within a multilingual experience might be confusing. If your users are using several languages on the app, then that should be respected. Otherwise it could be mysterious why all of a sudden everything appears in English, for example. However, to eliminate confusion on the auto-suggest element, you could simply allow ...
Don't ask the user a question if you don't have to. Same answer essentially as @Aprillion but explicit rendering can help user e.g. download bmml source – Wireframes created with Balsamiq Mockups Will work OK with up to 3 languages - so default to English + users locale + (optionally) IP based locale
For a bilingual search, do not detect the language, just search both and return results from both searches. E.g. when typing "ma" in the autocomplete search box, you could get: maçã (apple) ácer (maple) For multilingual, it wouldn't work that well, but if the search in the chosen language returns 0 hits, you could use a whole-word search in all languages ...
System itself will get confused when user starts typing only few characters (e.g. Portuguese), You could delay the search keyword matching until a full word has been entered. That way you can match an appropriate item (in either language).
Top 50 recent answers are included