Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

Has anyone seen any good examples of notifications systems out there, aside from iphone or android? I'm looking to design a notifications system that will give the user a gentle nudge (as they work in a desktop software application in a self-publishing capacity - their final deliverable will be a book, but we don't want it to have errors.) that will draw attention to mistakes they make along the way, but not interrupt their work flow.

Are there notification frameworks or systems that come to mind? If so, what was it you liked about it?

Would love to see some UI examples...

share|improve this question

closed as not constructive by JonW May 3 '12 at 12:42

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

4 Answers 4

Check out some of these MooTools notification widgets (demos included):

share|improve this answer

Not entirely sure of the context in which you are working (desktop?). I am assuming you don't just mean like a status bar with message, as these often do not get seen.

Lots of applications have clear but not very distracting notifications for spell checking, eg Word, Thunderbird, Chrome, etc. The notification is usually a wiggly coloured line under the error which you can choose to correct manually or get choices/help via a popup menu.

Many IDEs (eg Visual Studio, Eclipse, Qt Creator) have a vertical bar to one side which can indicate errors and their severity against relevant lines. This space is also useful for other information, not just mistakes.

Maybe this isn't relevant to your workflow - you don't tell us about the workflow that you don't want interrupted :)

Personally I find both these systems work just at the right level. I am aware that there is a problem but I can continue without losing train of thought. I can come back to it later. I can see multiple problems all at once when I do come back and I can choose which ones to resolve depending on severity.

It's a tough problem. Any notification in order to make itself known needs to interrupt the user - even if very slightly. The only non-interrupting notification is no notification. I even think sliding or fading popups are too much because they take too long to appear and disappear. Ones that suddenly appear are too distracting, and also once they are gone away, the notification can be forgotten.

I think a permanent but very subtle notification, shown as near to the problem as possible is good. The ability to see a notification in place allows the user to interact with it and find out more information about the problem right there in context.

You could opt to only notify in a stronger way if the user attempts to 'move on' without rectifying problems.

[Edit] I was just using MS Expression Blend4 after answering this question, and realised they used quite a nice notification system as you work. It did not come to mind earlier because it was not so distracting as to be annoying, remarkable or memorable. [Great ux doesn't get noticed!]. The benefits of this system are:

  • Tooltips appear pointing out a particular issue.

  • They are not in contrasting colours to the area I'm working in so they don't distract too much visually.

  • They point exactly to the particular control that is the cause or where I can correct the problem.

  • They do not take focus.

  • They do not hide what you are doing right at time.

  • They do not stop you typing or carrying on.

  • They do not go away as you change focus to other parts of the dialog.

  • You can click on them to dismiss/ignore them

  • They clearly state the problem and they automatically go away as you correct the problem or do something else that makes the problem go away.

  • I do not get a stronger error notification until I proceed to the next stage without rectifying the problem.

enter image description here

share|improve this answer
    
Thanks for those thoughts. The workflow involves making pages that will ultimately come out as a printed book, journal or calendar. –  Dassi Shusterman Jul 6 '11 at 16:47

I would only suggest notifications like those posted by VirtuosiMedia for alerting the user of 'background' activity (e.g. 'X has finished uploading').

I agree with Roger and feel that anything alerting a user to a mistake or error should be contextual like this jQuery plugin

share|improve this answer

Notifications are usually ephemeral, and alert the user to an event, rather than a situation. For errors in a document or process, I think you want something more like syntax highlighting.

Look at MS Word for text examples, or a fancy IDE (IntelliJ IDEA, or MATLAB from MathWorks) to get a feel for how this can work when you know a lot about the content's structure. These will not only flag problem areas (using underwaving and/or lines in the sidebar), but also give you on-the-spot explanations, and opportunities to correct common problems via a popup.

If you do mean notification, Growl, for Mac, lets you choose how alerts appear; there are a bunch of graphical variants in there that are quite pleasing and effective. They all follow the same general pattern, though (an area fades in quickly, persists for a few seconds, then fades out slowly). It is extensible, so you can write your own.

For more asynchronous alerts, there's Facebook's "red flag" approach, which persist unobtrusively until cleared. The system works because, once users know where to look, they'll poll for info from a persistent spot on screen.

share|improve this answer

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