+1
Completed

Tweak the display of the <after search text>

Cheehan Tee 6 years ago in Usability & Interface • updated by Sergey Stukov (co-founder) 6 years ago 3
The "after search text" now blends into the gray box (which contains the input box) which presents 2 problems. 
(1) It's not obvious and likely to be missed.
(2) From a content grouping perspective it's incorrect as it refers to the search results and not the content in the gray box. 

I suggest that you put it outside the gray box and call more attention to it with subtle use of colors etc.

Answer

Answer
Completed
  1. Removed contradictory messages
  2. Search completed notification message in more visible now
  3. Search query highlighted with bold style
  4. Added button that calling to action
Any suggestions and feedback appreciated.
Answer
Completed
  1. Removed contradictory messages
  2. Search completed notification message in more visible now
  3. Search query highlighted with bold style
  4. Added button that calling to action
Any suggestions and feedback appreciated.
Thanks for the really quick response to fix this. Here's my feedback:

The "+Post a new suggestion" button is unnecessary and should be removed because:
- It does the exact same thing as the "Next" button, so why have 2 buttons so close to one another doing the same thing?
- It confuses the user because it makes them think "should I click Next or Post a new suggestion?"
- The text doesn't flow right - "Your search asdf did not match any topics. Back. or Post a new suggestion"
- The text is wrong - it might be a question or a bug report

I also find the "Back" link unnecessary in the "did not match" message. If there's no match, I'll proceed to post my feedback, why would I want to go back. In any case, I can just adjust my search term if I want to. 

Actually I would suggest a bigger change:
- When you show the search result or the "did not match" message, show the submit feedback form at the same time. This saves the user from an extra click on "Next". 
- Alternatively, show the results on the side, like how UserVoice does it, which works very well. 



We thinking about removing "next" button instead. 
1) It will saves space for small width resolutions.
2) Only one button will appear after search and this remove confusion with two buttons.
I don't think that's a better option because 
1. The "next" button is much narrower than the "+post a new suggestion" so if you're concerned about width, you shouldn't remove the narrower button.
2. The "next" button is on the previous screen so it's consistent, meaning more intuitive for the user. 
3. The "+post" button crowds out the after-search-text and makes it hard for the text to flow nicely across both components. 

I hope you consider the "bigger change" I propose.