What are some good usability guidelines an average developer should follow? [closed]

Answer 1

• Simple is better than complex
• Complex is better than complicated (eliminate 'nested ifs')
• Intuitive (good elements needs no explanation)
• Follow the convention (for example, underlined means link, red means error, tab goes to next field, etc.)
• Use semantics to apply the logic (header reads first, paragraphs next)
• whitespace is important

Answer 2

Think about the users that will use your app. Why are they using it and in which context?

• Will the majority be pro users that know the domain in which the application is used and use the app a lot? Then don't be afraid of adding a lot of data to the screens as long as it arranged logically for users (normally that is not in alphabetical order :-). Think trade screens for stock borkers or airplane cockpits.
• Are users occassional users? Keep it simple. Avoid context switches (keep all/as much as possible of necessary data for a task on the screen at each time). Don't break expectations of how gui widgets normally work. Design for failures.
• Anything in between? Allow users to grow in the UI. Track usage so you can later determine where users seem to spend the most time so you can improve the most used areas of your app.
• Test your app on friends and colleagues (the corridor test) to see if they are able to use it efficiently.

That's a start.

Answer 3

I've posted related questions:

• What metrics for GUI usability do you know?
• GUI design techinques to enhance user experience

Answer 4

Source: http://stuffthathappens.com/blog/wp-content/uploads/2008/03/simplicity.png

Answer 5

I suggest to read these blog posts from the Enso creators.

Of course they repeat guides/ideas/advices from books such as
The Design of Everyday Things and About Face, but nevertheless, the posts contain quite a few insights and (IMO) they are a good read.

Answer 6

Remember that your application will be one of many the user will have to deal with. Don't do things just to be different or kewl. Don't come up with unusual graphics, behaviors, terminology, or interactions. Use the standard OS controls, conventions, utilities, and behaviors.

Let your app interoperate with other apps; allow cutting and pasting of data, save your data in formats other apps can read, and allow importing data from other apps instead of using your UI.

If you are making a desktop app, do not try to take over the user's computer. Leave the user's Documents folder, task bar, and application preferences alone. Don't change anything already installed on the computer. Allow scripted or command-line interactions.

If you're making a web app, do not try to take over the browser. Do not try to subvert the standard menu bars, history, layout, or fonts. Allow the user to change the page using Javascript.