Tag Info

New answers tagged

2

The requirements are: Brief and concise, to catch the sense in a fast way Minimal, as it's not the full notification view Clickable to reveal the details I think you should be less wordy and focus user on the important information only. Offer # isn't for humans, it's for computer. Highlight the numbers only and make them readable with monospaced ...


0

In my opinion. I think you should use following three altogether: Conditional Coloring View Details Link 3- Link all text or box to the details as well without giving them default coloring of links. Because: User can better/quicker understand with conditional coloring View link does not acquire much real estate but it will make user think that there ...


1

Another thing that might work is to use tabs which mark the Summary Stats rectangle... then automatically switch context over to Specific Stats as needed in your example above but leaving a clear way back for the user...


3

You would need to test it out but I believe that one of these buttons would more clearly communicate the described action to the user...


0

Labeling the button "back" may be general but that's the appropriate label. From your description, "Summary stats" and "Charts" are not related with each other. In this case you can consider a separation between them like the below. download bmml source – Wireframes created with Balsamiq Mockups In these cases the user will know that ...


0

I am feeling lucky : How about a simple arrow icons (<) on the right hand side or as an icon on the left (Back icon) Specific Stats . Nicely done visually. Instead of even writing Back. I feel its pretty clear even if users did this once. I think "Back to Summary" is ok. (are you having space and visual clutter issues then my suggestion is don't try ...


-1

I would suggest a pop-over that has a 'close' button for the detail view. Otherwise, if it's purely desktop, could hovering the table data expose the detail info?



Top 50 recent answers are included