![\"Education\"](\"https:\/\/www.mrc-productivity.com\/blog\/wp-content\/uploads\/2010\/11\/Education.jpg\")
No web developer wants to create a bad user experience. Nobody sets out to make a confusing and frustrating interface that drives users away. But, the sad truth is…this happens far too often. <\/p>\nNo web developer wants to create a bad user experience. Nobody sets out to make a confusing and frustrating interface that drives users away. But, the sad truth is…this happens far too often. <\/p>\n
How often? <\/p>\n
According to the online marketing institute<\/span><\/a>, the problems caused by a poorly designed interface are substantial. The numbers indicate that: <\/p>\n The fact is, usability is becoming an essential aspect of web application development. User expectations have changed. Modern end users expect to pick up a web app and understand how it works. Confusing interfaces will only frustrate users and drive them away. <\/p>\n However, many developers build applications which do just that. They unwittingly make development mistakes that hurt their web application\u2019s usability. In doing so, they accidentally alienate their users. <\/p>\n What are these mistakes? In what ways do developers accidentally create interfaces that frustrate their users? We posed those questions to a few experts in the area of usability, and have compiled their feedback below. Here are 7 development mistakes that kill web application usability: \n\u201cMost usability mistakes on the web involve developers forgetting that people don\u2019t want to have to struggle to figure out how to use the interface,\u201d explains Steven Swimmer, Web and Digital Strategy consultant at Swimmer Media<\/span><\/a>. \u201cThings that may seem obvious to a developer are not at all obvious to users. Unless your odd interface adds utility, then it\u2019s not worth doing. If there is an odd interface that adds some utility but is misunderstood by users, you need to provide some integrated means of showing people how to use the app.\u201d\n<\/p><\/blockquote>\n The desire to create something \u201cnew and innovative\u201d can become one of the biggest stumbling blocks for developers. Delivering a unique user experience, or new approaches to common functions, is more likely to confuse users than impress them. Most users won\u2019t bother figuring out how your great new interface works, or will simply become frustrated when a seemingly common function doesn\u2019t behave as expected. Here\u2019s one great example:<\/p>\n \n\u201cUsers expect that commands will be the same from site to site or app to app,\u201d says Ian Lamont, author of Twitter In 30 Minutes<\/span><\/a>, Google Drive & Docs In 30 Minutes<\/span><\/a>, and Dropbox In 30 Minutes<\/span><\/a>. \u201cBut it doesn’t always work that way. Take Dropbox. I tell users that deleting a file in Dropbox is like trying to kill a vampire. You may think you’re deleting something by selecting a file and clicking the “Delete” key, or dragging it into the trash on your desktop. The file isn’t dead yet. The only way to drive a stake through its heart is to log on to Dropbox.com, use the “Show Deleted Files” option, and then select “Permanently Delete”. Sound complicated? Absolutely. Dropbox has reasons for setting it up this way, but it’s not intuitive, and leaves a lot of users frustrated or vulnerable.\u201d\n<\/p><\/blockquote>\n When a user makes a mistake, or attempts an unauthorized action, what happens? Do they receive a confusing error message, or an error message with clear advice on how to resolve the issue? In my experience, it\u2019s typically the former. Most error messages mean nothing to the user, and provide no guidance as to the user\u2019s next steps. The result: frustration. <\/p>\n \n\u201cPoorly written or ambiguous error messages can be frustrating to users,\u201d explains David Ciccarelli, CEO and co-founder Voices.com<\/span><\/a>. \u201cDon’t give the users an error number and code that means nothing to them. Instead, say \u201cSorry, that didn’t work. Try this instead\u2019.\u201d\n<\/p><\/blockquote>\n One of the most common ways developers annoy their users: They accidentally turn their applications into scavenger hunts. They place navigation elements, or essential buttons, on different places across screens…which frustrates users to no end. <\/p>\n \n\u201cChanging where an element is located from page to page or screen to screen will cause your users to hunt for a feature,\u201d explains Ciccarelli. \u201cI once used an enterprise application that had the main navigational tabs change order depending on which part of the app I was in. Terribly frustrated, we ended up terminating our contract only to switch to a competitor who is often praised for good usability.\u201d\n<\/p><\/blockquote>\n Your application must provide the user with a clear path. Take the screenshot below, for example. When a user logs in, the application delivers three clear options. Sure, the application is capable of many more tasks, but adding all of those options will only complicate the process for the user. Don\u2019t focus on the application\u2019s capabilities. Focus on the user\u2019s goals. <\/p>\n \n\u201cWhile the user should be in control of the experience, too many competing options can make decisions difficult,\u201d explains Caroline de Gruchy<\/span>, an experienced web designer. \u201cThe options on a page should be mutually exclusive. I had a client who wanted three different calls to action leading to 3 very similar pages, leading back to the same information afterwards. How was the client to decide where to go? Clicking 3 separate pages that tell you the same thing wastes my time and shows no respect.\u201d\n<\/p><\/blockquote>\n One of the big complaints surrounding the healthcare.gov fiasco was the registration process. Users were forced to complete a lengthy registration process (that frequently failed) before they could see available healthcare plans. This is a usability no-no. If you must ask for user information before granting access, keep that info to a minimum. Lengthy registration processes will only drive away potential customers.<\/p>\n \n\u201cSome designers\/developers like to have 10 pages for a new registration,\u201d says Jeanine Swatton<\/span>, an engineer \u2013 iOS and Ruby on Rails Developer \u2013 who teaches iOS development at Silicon Valley University and UCSC Extension. \u201cDon’t they realize that after the 2nd page, they lose the potential customer? Keep it simple – a one click sign up process asking minimal information. Allow users to add their profile later.\u201d\n<\/p><\/blockquote>\n Another point on this topic: Make sure you tell the user just how much time the registration process will require. Nobody wants to get started on a registration process, only to realize later that the registration form is 10 pages long and requires a half hour of their time.<\/p>\n \n\u201cBecause your visitors might be using a keyboard and mouse with a widescreen monitor or a smartphone with a small touch screen, you need to design your UI with both users in mind,\u201d says Noah Nehlich, owner of Structure Studios<\/span><\/a>. \u201cSmall text links can be very hard to click successfully on a mobile device, and might drive people away in frustration when they can\u2019t reach the information they need.\u201d\n<\/p><\/blockquote>\n This is an issue on two levels. First, clickable areas must be as big as they appear. What does that mean? The image below highlights this issue. <\/p>\n You\u2019ll notice that what appears to be a clickable button is actually a small text link inside a box. Clicking the button itself will do nothing…unless the user clicks the text. Imagine how frustrated your users will become when they repeatedly click an apparent button that doesn\u2019t actually do anything.<\/p>\n Secondly, creating small clickable areas (as described above) can prove frustrating for the growing number of mobile users. These days, you must build an application that functions well on any device…which calls for links and buttons that are easily clickable on a touchscreen. Brian Maggi, Director of Product Marketing at Sencha<\/span><\/a> shares a good piece of advice for making web apps usable on a mobile device:<\/p>\n \n\u201cDesign for a single thumb,\u201d he says. \u201cThis means making UI hit zones big enough for the thumb, the fattest finger. Make related things closer in proximity too, because it\u2019s also the shortest.\u201d\n<\/p><\/blockquote>\n I\u2019m seeing a problem crop up more and more: When cloud-based software companies redesign their interface, they blame negative user feedback on a \u201cfear of change.\u201d While that does happen, it\u2019s a dangerous approach to user feedback. Sometimes, interface redesigns remove features that users loved, or complicate common actions. While many users do dislike change, don\u2019t automatically group all complaints in that bucket. <\/p>\n \n\u201cI get the sense that some developers and UX designers are not thinking about the needs of their users when they try to follow minimalist interface ideals that seem to be the rage in San Francisco and Silicon Valley,\u201d says Lamont. \u201cNot everyone wants that. I think minimalist interfaces actually create more clicks and more frustration for users when the apps have a lot of functions or features. People also don’t like it when software companies make a radical change to an interface. Microsoft was criticized when it switched Office to the ribbon interface. Now a lot of Web software companies are feeling the heat.\u201d<\/p>\n \u201cI have documented one case involving Hootsuite, a popular Twitter client that recently changed a critical UX element that infuriated many paying customers. The company blamed customers’ “Fear of change” as the reason for the outcry, instead of acknowledging that the UX change had been poorly thought out in terms of its most dedicated users.\u201d\n<\/p><\/blockquote>\n What do you think? Would you add anything to this list? If so, feel free to share in the comments.<\/p>\n","protected":false},"excerpt":{"rendered":" No web developer wants to create a bad user experience. Nobody sets out to make a confusing and frustrating interface that drives users away. But, the sad truth is…this happens far too often. How often? According to the online marketing institute, the problems caused by a poorly designed interface are substantial. The numbers indicate that: …<\/p>\n\n
\n<\/a><\/p>\n1. Inconsistent approaches to common functions<\/h3>\n
2. Ambiguous error messages<\/h3>\n
![\"photo](\"https:\/\/www.mrc-productivity.com\/blog\/wp-content\/uploads\/2013\/11\/origin_3575367541.jpg\")
3. Changing navigation element location<\/h3>\n
4. Giving the user too many competing options<\/h3>\n
![\"The](\"https:\/\/www.mrc-productivity.com\/blog\/wp-content\/uploads\/2013\/11\/Main-menu1.png\")
<\/a>5. Lengthy Registration process <\/h3>\n
6. Small clickable areas<\/h3>\n
![\"clickable\"](\"https:\/\/www.mrc-productivity.com\/blog\/wp-content\/uploads\/2013\/11\/clickable1.png\")
<\/p>\n7. Blaming negative feedback on a \u201cfear of change\u201d<\/h3>\n