User Interface Designing Tips for Better HCI

User interface design is the process designers use to build interfaces in software or computerized devices. Designers aim to create interfaces which users find easy to use and pleasurable.

— User Interface Design Guidelines:

Following are some tips which should be focused in designing User Interface.

— Visibility of System Status (Feedback):

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

The upload button is enabled, until clicked. Then it is replaced with a progress indicator until the file has finished uploading.

— Match between the System and Real World:

The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms.

— User Control and Freedom(Navigation):

Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue.

Undo and Redo buttons are available in the toolbar, and can also be accessed with the standard keyboard shortcuts.

— Consistency and Standards:

The arrangement of UI controls ,their arrangements should be consistent through the system interfaces. Same color schemes should be applied. Users should not have to wonder whether different words, situations, or actions mean the same thing. For example, an icon that represents one category or concept should not represent a different concept when used on a different screen.

— Error prevention:

It is always better to design interfaces that prevent errors from happening in the first place. Even better than good error messages is a careful design, which prevents a problem from occurring in the first place. Whenever possible, design systems so that potential errors are kept to a minimum. Example: Make the primary action prominent with a larger click area. Cancel and secondary actions are just shown as links

— Recognition rather than Recall:

Minimize the user’s memory load. Make objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

— Flexibility and Efficiency of Use:

With increased use comes the demand for less interactions that allow faster navigation. This can be achieved by using abbreviations, function keys, hidden commands and macro facilities.
Accelerators — may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

— Help Users Recognize, Diagnose, and Recover from Errors:

Designers should assume users are unable to understand technical terminology, therefore, error messages should almost always be expressed in plain language to ensure nothing gets lost in translation.
Provides immediate feedback with specific instructions.

— Help and documentation:

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.