Search Bar should be actual search bar and not launch a modal window, or a UX element that actually communicates it will open a separate interface.
C
Christopher Bridenstine
The "Search" bar in the header isn't actually a search bar. It only opens a modal window elsewhere on the page that can then be used to search/filter. Why is the search bar at the top visually communicated as a "Search Bar" when it doesn't function as one? I would ask that the team either
update the UX to have the search bar actually function as one with: 1) the search string present in the bar and 2) the relevant content expanding down from the bar instead of in a window somewhere disconnected from this UX element.
-OR-
Don't present the interface visually as a "Search Bar" and a button or other element that is visually indicates it is meant to open another interface.
The current UX makes utilizing the search feature cumbersome, more mental effort, and can cause UX errors when I interact with the elements in a way I expect but which the experience isn't meant for a user to do.
Log In
Ankit Mishra
Hi Christopher, just to make sure I get understand your feedback correctly - do you mean that opening search modal separately is the issue? Ideal experience would be to click on the search bar at the top and start typing there and see the results at the top itself rather than open the modal and type in it?