Reviewing User Interfaces



Designing a user interface based proven usability principles or based on product requirement guidelines may be an easier task. But reviewing the nitty-gritties of user interface is a very intelligent task, as this process can also be attributed to 'user interface holistic testing'. It can be layered technique of reviewing user interface components of in depth testing and reviewing of them. Normally what we call expert review could be done even before the design implementation to weed out the redundancies of the interface.
Has your boss or a client ever asked you to review a user interface for a Web or desktop application? Perhaps the request went something like this: Can you just look over these new screens for us? Oh, and can you check the error messages, too? It won’t take long! And, by the way, we ship next month. Whether you are an interaction designer, usability professional, technical communicator, quality assurance engineer, or developer, reviewing a user interface typically means identifying :
  • usability problems related to
  • - the layout, logical flow, and structure of the interface
  • - inconsistencies in the design
  • non-compliance with standards
  • ambiguous wording in labels, dialog boxes, error messages, and onscreen user assistance
  • functional errors
While user interface (UI) reviews often occur at the end of the development cycle, I recommend that you get involved early in the process, preferably when the designers create the initial wireframes or paper prototypes. Why? Making changes early in the process reduces development costs. Plus, if you identify usability issues early, it’s much more likely the team can remedy them before launch, preventing bad reviews like that shown in Figure 1, negative word-of-mouth, and the lost sales that result from them.

>> Read more about 'Reviewing User Interfaces'

Babels of slum and Rahman



Today, my morning started with Oscar awards show in TV. It was the triumph moments for Indian movie fraternity. Slumdog Millionaire won many awards . I am sure that's what the pinnacle minute for director and everyone. Awards came to most of movie departments except except for acting department, I am sure acting part was not nominated ! 

Personally I liked the movie for its technical enrichment. Story & acting wise it's just another ordinary weaving. I was sure editing would win the award as movie's asli strength is in its tight editing.

Though Rahman won award for background score, he was 'the best' in Lagaan and I'm sure he missed academy award for it, though he was nominated for it or not. Certainly music in Slumdog Millionaire was not top notch v/s his other compositions. May be sound engineering has given a special attraction for the background score. You should listen to his Azaadi song in netaji subhash chandra bose -movie, that's the best rendering than jai ho.

But again it's proved. you do gods-own-quality movie, unless it's marketed well to International audience with much fan fare, no movie is going to win academy awards. I was quite curious about what Indian netizens think about it. I am sure there's a better place to record their voices and chaos in rediff discussion

The $300 Million "Continue" Button

Do usability analysis and implementation still holds a profitable edge for corporations ? Certainly. And it mattes a most when co can earn $300 million just by renaming the button :) !

Seems exaggerating at first glance, but this is the true facet of effective and usable design if much forethought is put into practice while designing a user experience. I am sure, not only intelligent interface design matters but also, usability analyst should have good foresight business needs and comparative analysis of design implementation. This is about registering process in a website where registering and entering valid email ID is very much needed to continue in the site.

Given a scenario of fast business trend and bursting competitive edge, I am sure this is one niche example of usability-school-of-thought:

UIE studied people actually using the site, and it turns out that the prospect of registering was enough to turn some users away; meanwhile, even return users had problems logging in because they didn't remember the email address or password they signed up with. (45% of users apparently had multiple registrations—a few had up to 10.) Granted, these represented a small portion of users. But for a retailer with $25 billion, even small portions signify huge lost profits.

So UIE redesigned the site, replacing the "register" button with "continue." They also added a message, saying that registering wasn't required to checkout, but was optional and might be helpful if you returned.

Sales went up 45%—$15 million in the first month, and $300 million in the first year.

Given UIE's success, it's a wonder how often you still see byzantine registration forms on websites. But there's a bigger lesson: That empirical research into how people actually behave matters far more than the intuitions of any designer, no matter how experienced that designer might be.

More at: The $300 Million "Continue" Button
and also at uie.com

Corporate Accessibility

Good web development and standards based development, which one is right or wrong ? If a web application is compliant to web standards based development, will that be fine to call it as a good web development ?Do corporations really put time and money in making the website fully accessible web app ? And what point is called 'accessibly compliant' web app ? Ensuring if it's achieved AA or AAA ? I found a interesting article about these details:

One problem with corporate accessibility is that while corporations generally care about accessibility in the abstract. which can lead to a grudging attempt to be accessible, because a corporate lawyer will naturally try to do the minimum required to stay in compliance; minimizing risk while minimizing costs.

The way to overcome this is to focus on the customer. I find the following arguments successful in getting accessibility discussed in a positive, “good-to-have” way rather than in a legal compliance “oh-well-if-we-must” way:

Find more in Think Vitamin > accessibility