Category: UX Design
This category features quality articles on usability, information architecture, interaction design and other user experience (UX) related topics for digital (Web, mobile, applications, software) and physical products. Through these articles, experts and professionals share with you their valuable ideas, practical tips, useful guidelines, recommended best practices and great case studies. Curated by Chui Chui Tan. .
Popular tags in this category: Usability, Design, User Experience, UI, Psychology, Process, E-Commerce, Content.
I sincerely believe that the user experience community should add game design to its toolbox of competencies. If we’re truly committed to creating satisfying user experiences, then there’s no reason why games, which can satisfy people so richly, should be excluded.
Operating successfully in the games domain means learning a new set of competencies, and I don’t want to oversimplify the challenges of designing high-quality game experiences. However, if you’re in a position to jump in and start designing, then I can at least offer a primer to help you steer clear of some of the most common mistakes.
Today we'll have a look at a few projects in which the consistent use of the well-known term "emotional design" can result in a great personality. Positive attitude often leads to people sharing and even advocating for your product with their peers.
Positive emotions instill positive memories and make users want to interact with your product in the future. There’s also an additional benefit: In pleasant, positive situations, people are much more likely to tolerate minor difficulties and irrelevance. While poor design is never excusable, when people are relaxed, the pleasant and pleasurable aspects of a design will make them more forgiving of problems within the interface.
The way you present your product or service is essential to its success — or at least it could be if you know how to do it right. The first impression you make on people is crucial. When selling a product, you want that first impression to be as positive and remarkable as possible. If you have managed to draw them in, you will need to introduce the product within a few seconds.
Show them that your product is just what they want, that it’s useful and that it adds some kind of value to their lives. A smart product presentation does all of that. Here, we will cover different aspects of a product presentation and give examples of how to use them to your advantage. The idea is to give you an overview of the different elements that make a product page successful.
Good Web designers know what many others might not realize: that creating a truly beautiful website requires care, time and craft. And similar to how a craftsperson molds their creation by combining raw materials, skill and unwavering focus on the vision, a beautiful design is planned and executed with exceptional focus on what is to be achieved by the website. It is important, however, not to confuse a beautifully crafted website with one that simply brushes over the content with attractive visuals.
This article provides a small selection of tried and true methods that Web designers regularly employ to give a website that bespoke look and feel. Make no mistake: these methods do take extra time, and they often result in improvements that the untrained eye might not consciously register. Users will leave with a smile and a lasting impression or relationship with your website, even if they can’t quite put their finger on why.
Error pages for form-field validation are dreadful. You’ve just filled out 20 form fields, yet you get the same bloated page thrown back in your face because a single field failed to validate. I clearly recall the often loud sighs of despair during our last usability study each time a test subject encountered a validation error page.
We reflected on this problem and got an idea that we call “error fields only” — which is exactly what this article is about. Before exploring this idea, let’s look at three traditional types of validation techniques: “same page reload,” “optimized same page reload” and “live inline validation.”
Have you ever wanted your users to click a link but didn’t know how to get them to act? When some designers run into this problem, they’re tempted to use the words “Click here” on their links. Before giving in to the temptation, you should know how using these words on a link can affect how users experience your interface. Not to mention that having proper link titles is a major accessibility requirement since the term ‘click’ is irrelevant to many assistive technologies and isn’t descriptive enough for screen readers.
Using the word “click” on your links takes the user’s attention away from the interface and on to their mouse. Users know what a link is and how to use a mouse. Calling attention to the mechanics is unnecessary and diminishes their experience. Instead of focusing them on the interface and its content, “Click here” diverts their attention to themselves and their mouse. Not to mention, you might also make them feel dumb by suggesting that they don’t know what a link is or how to use a mouse.
Emergency car shopping is no fun. This past month was the second time I had to shop for a car in a short timeframe without advance warning. Like most informed shoppers, I went online to get a feel for my options, armed with knowledge of what I was looking for: apart from safety, gas mileage and reliability, it had to comfortably seat six and not require me to take out a second mortgage.
I felt like a persona out of a scenario that I had role-played a few years ago when our UX team conducted a global UX benchmarking project for General Motors. That year, a JD Power consumer satisfaction study revealed that 68% of GM’s US websites were below the industry average, with two in the bottom 10%. This time, though, the experience was personal and made me think about the lessons to be learned from the experience of shopping for a car online that could be applied to any website.
We’d like to believe that we use established design patterns for common elements on the Web. We know what buttons should look like, how they should behave and how to design the Web forms that rely on those buttons. And yet, broken forms, buttons that look nothing like buttons, confusing navigation elements and more are rampant on the Web. It’s a boulevard of broken patterns out there.
This got me thinking about the history and purpose of design patterns and when they should and should not be used. Most interestingly, I started wondering when breaking a pattern in favor of something different or better might actually be OK. We all recognize and are quick to call out when patterns are misused. But are there circumstances in which breaking the rules is OK? To answer this question properly, let’s go back to the beginning.
You cannot plan for and design a responsive, content-focused, mobile-first website the same way you’ve been creating websites for years—you just can’t. If your goal is to produce something that is not fixed-width and serves smaller devices just the styles they require, why would you use a dated process that contradicts those goals?
I'd like to walk you through some problems caused by using old processes with responsive design. Let's look into an evolving design process we've been using with some promising new deliverables and tools. This should provide a starting point for you to freshen up your own process and bring it into the responsive age.