1

As a developer, I'm always confused about the three basic values of any application's alert:

  1. Title
  2. Message
  3. Dismiss button

What should be placed in those 3 values? FAQ for myself:

  • Should the title be a resume of what happened or where the message came from?
  • Should messages use exclamations?
  • Should messages be complete sentences (ending with a full stop)?
  • How much detail should the message contain?

Well, as a single question: there is some basic rules while writing alert/notification messages? Bonus if these basic rules answer my minor questions.

Please share your thoughts...

  • 4
    Welcome to the UX Stack Exchange, @cvsguimaraes! You're asking a lot of different questions at the moment. (If you have separate questions, it's best to put them in separate posts.) What's your main question for this post? – Graham Herrli May 3 '13 at 15:12
  • 1
    @3nafish Thanks! Well, as a single question: there is some basic rules while writing alert/notification messages? Bonus if these basic rules answer my minor questions. That's it. – kbtzr May 3 '13 at 15:46
  • 1
    About the punctuation questions see this: ux.stackexchange.com/a/44086/62535 and this: ux.stackexchange.com/questions/18671/… – DasBeasto Sep 12 '15 at 14:58
2

All of this is documented by Google in their writing guidelines.

http://www.google.com/design/spec/style/writing.html

Use contractions, avoid exclamation marks, be brief, keep it simple, use numerals in place of words, avoid slang, use punctuation when writing more than one sentence, use easy to understand language.

1

I'd say avoid using error codes like "Cannot do this stuff properly error : 321 " I don't think users really care about the error code as much as the developers do, For the expert users you can put a little
"> Show details". Next thing would be to be precise and brief about the error . Also one glance at the title should tell what the error actually is . The dismiss button is an important part, don't make the user agree to the error by pressing OK instead give the user an option to go and fiddle around with the settings to see if that solves the error or a CANCEL or DISMISS button .

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.