I'm just curious about the system status in the modern web app design. In some old windows applications, they have warning(yellow colored), error(red colored) and success (green colored). In the modern web design, I haven't seen any warning status been used explicitly (except some dialog). So I was wondering if the warning status still make sense today? If no, what can be done to minimize the warning if such application goes to web? Thanks.

enter image description here


Applications should try to resolve the situation, instead of simply sharing their worry with a customer.

4 Things That Oracle Did Wrong

  1. In our example, Oracle uses such a bright colors to call attention for a completed task.

enter image description here

Completed is too bright

Anything "completed" is fine. You don't need to shout about it. People have other things to do.

  1. A warning can possibly be better handled. I don't know what happened in this case, but in most cases, it can be eliminated with some extra code (sometimes too much code though).

  2. The warning should be better explained.

enter image description here

Warning what? What happened?

Instead of writing "Warning", Oracle had enough space in that cell to explain what actually happened. Examples:

  • Queued
  • Timeout
  • Empty dataset

    1. The text file should come to the point.

enter image description here The reason for the warning is nowhere in sight

Back to your question:

  • Warnings should be eliminated whenever possible.
  • When warnings are inevitable, the status should tell what happened, not just "warning"
  • Nothing wrong with yellow color.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.