You Are Here:

Getting started

Register Today

Register with Forum Nokia now and you'll enjoy the full benefits of the Forum Nokia membership.

Register Login
Community Highlights

Wiki article of the week

Zoom and Rotate Gestures in FlashLite for touch-enabled devices

Champion of the month

Jackson Feijó Jackson Feijó
Read more about Jackson on the Champions website.


Forum Nokia Events

Nokia Developer Days in South Africa
December 01, 2009
Johannesburg, South Africa

Forum Nokia Developer Conference ’09, India
December 07, 2009
Bangalore, India

LeWeb
December 09, 2009
Paris

Web Runtime Coding With Aptana WRT Plug-in
December 09, 2009
9am New York | 2pm London | 4pm Helsinki

Web Runtime Coding With Aptana WRT Plug-in
December 09, 2009
9:30am New Delhi, noon Beijing


View all

Good usability is often understood to mean simply a good user interface, but it encompasses more than that. It includes the product, the user, the user’s goals, and the context of use. All these things should be considered when designing usability. Compare a busy young executive to a retired grandmother. There’s a huge difference in their needs and in how they perceive the world, but both might be using the same device or service to accomplish their goals.

Questions to be asked:
WHO is the user?
WHAT is the user trying to accomplish?
WHEN, WHERE, and HOW is the user using the product?


A usable product is a joy for the user. It is easy to learn, it makes the user less prone to errors, and it enhances productivity. In other words, the product itself creates satisfaction and trust. But the user is not the only one to benefit from usability.

Knowing which features are necessary before starting the development process will also cut down development costs and time because the development team can concentrate on issues that matter. And when users are able to accomplish their goals without strife and trouble, they are less likely to demand support or maintenance; hence costs after development are reduced as well.

Usability evaluation reveals issues in the user interface that are important to address, but that may be very difficult or even impossible to notice on the code level. The developer’s job becomes infinitely easier when there are well-defined UI and usability specifications, with less need for drastic redesigns in the middle of the project.





Rate This

Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
User Rating: qfnZuserE5FratingQNx5E2E0000X
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fwwwE2eforumE2enokiaE2ecomE2fTechnologyE5fTopicsE2fE44esignE5fandE5fUserE5fE45E78perienceE2fUserE5fE45E78perienceE2fGettingE5fStartedE2fX qfnZupdatedQDx2009E2d05E2d15X qdcZtypeQUqfnZE45E78cludedFromGeneralE4CistingsQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqfnTypeZE52esourceQ qdcZtypeQUqfnTypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZdistributionQUxhttpE3AE2FE2FforumE2EnokiaE2EcomE2FX qfnZtypeQUqfnTypeZE52esourceQ qfnZtypeQUqfnTypeZWebpageQ qmarsZlanguageQUxhttpE3AE2FE2FswE2EnokiaE2EcomE2FlanguageE2D1E2FenX qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqfnTypeZE52esourceQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqfnTypeZWebpageQ qrdfZtypeQUqrdfsZE52esourceQ qrdfZtypeQUqfnZE45E78cludedFromGeneralE4CistingsQ