How to write "good" user interface texts?

Answer 1

The resources found at Writing for the Web might be useful to you.

Answer 2

Read The Elements of Style. Then re-read it.

Also, anytime you are working with a program or website make a conscious effort to notice how they choose to do their writing. Imitate those you like.

Answer 3

The best tool for this is called "primary education". Many developers seem to have missed this, and I don't know how to fix that problem.

Also, this may be a British thing, but I think you mean "humor" and "going to Hell in a handbasket". :)

Answer 4

Since XP, I've been a fan of the Windows UX Guidelines sections that cover how to properly structure text (how to ask questions, how to make assertions in dialogs, etc).

http://msdn.microsoft.com/en-us/library/aa974176.aspx

http://msdn.microsoft.com/en-us/library/aa974175.aspx

Answer 5

This book has a lot of good advice:

GUI Bloopers 2.0

Short version:

1. Be consistent throughout your application or app suite. Don't call the same feature two different names, even if they're in different dialogs, etc. Develop a product lexicon that everyone references.

2. Use the same terms that people who use your software use (i.e. users don't refer to themselves as users).

3. Don't call two different things by the same name.

4. Put all of the messages displayed to the user in a central place (i.e. a resources file of some kind). This makes it easy to review all of the messages for spelling, tone, consistency, and whatever else you want to check.

5. Usability test your software to see if the messages make sense and people can use your software easily. If they can't, change the resources file and test it again.

Answer 6

I would suggest showing your UI to as many people as you can--preferably people who read a lot (Just because reading does wonders for your grammar and vocabulary).

Getting something out that people can examine, however, is awesome--even if it's just a demo of the GUI.

If you work at a company, get to know your QA and Tech Support people. They are usually really wonderful once they understand what you are trying to do--they will review your UI, give you input on text and usability as well as possibly new requirements nobody in engineering would come up with.

If you work on your own, try to find a potential customer or two to review your UI. Ask them to pay attention to the text...

The more eyes, the better. You might even ask your parents, wife or other family. What can it hurt?

Answer 7

Get your application's texts proofread by someone who does just that for a living. Then the UI walked through by someone who does usability for a living. Neither of these two people should have been involved in the development.

It's the only way to make sure.