10 Principles for UI Design
September 5, 2007
These are ten general principles for user interface design. They are called “heuristics” because they are more in the nature of rules of the thumb than specific usability guidelines.
Visibility of system status:
The system should always keep users informed about what is goin on, through appropriate feedback within reasonable time.
Match between system and the real world:
The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
User control and freedom:
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. Support undo and redo.
Consistency and standards:
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
Error Prevention:
Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
Recognition rather than recall:
Minimize the user’s memory load by making 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:
Accelerators — unseen by the novice user — 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.
Aesthetic and minimalist design:
Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
Help users recognize, diagnose, and recover from errors:
Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
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.
By Jacob Nielsen
At 17, she has built a million-dollar web site
August 30, 2007
Here is an amazing and inspiring story of a teenager Ashley Qualls, Founder Whateverlife. She may not have an MBA, a high-school diploma, or even a driver’s license yet, but Ashley Qualls already has an influential and lucrative Web site. Whateverlife.com attracts more than 7 million visitors a month — mostly teen girls, a valuable but typically elusive niche audience. In just two years it has generated more than $1 million in ad revenue.
more in here
World’s Highest Website
August 28, 2007
Trek the World’s highest website which is currently 18,939 kilometers high. Guys who are tired of trekking can take elevator too. Here you go World’s highest website.
