Recently I read a great article on UX/UI by Jared M. Spool, What Makes a Design Seem ‘Intuitive’? This reminded me some of the talk I heard on UX by Tommy Yi at the RefreshOKC meet-up. For those of you that don’t know, UX means user experience, and UI means user interaction. To quote another blogger who was quoting Wikipedia:
User experience design (UXD or UED) is the process of enhancing customer satisfaction and loyalty by improving the usability, ease of use, and pleasure provided in the interaction between the customer and the product.
User Interface Design is its compliment, the look and feel, the presentation and interactivity of a product.
5 things I Googled from this article:
Microinteraction: Microinteractions are contained product moments that revolve around a single use case—they have one main task. Every time you change a setting, sync your data or devices, set an alarm, pick a password, log in, set a status message, or favorite or “like” something, you are engaging with a microinteraction.
Security Design Pattern: Design patterns can be applied to achieve goals in the area of security. All of the classical design patterns have different instantiations to fulfill some information security goal: such as confidentiality, integrity, and availability. Additionally, one can create a new design pattern to specifically achieve some security goal.
Microinteractions Framework: https://marcabraham.wordpress.com/2013/07/10/book-review-microinteractions-designing-with-details/
Design Triggers: http://zurb.com/article/1286/pull-the-trigger-on-user-experiences-with
Microinteraction Experience: http://thenextweb.com/dd/2015/08/17/why-micro-interactions-are-the-secret-to-great-design/#gref
Why are microinteractions often overlooked?
Many microinteractions, like error messages and alerts, are unintentionally designed. Often, a developer rushing to meet a deadline, creates a solution to deal with a discovered edge condition, without giving any consideration to the experience users encounter.
In this specific microinteraction, what was the problem and what were Jared’s suggestions to improve the user experience?
In this specific microinteraction, the problem was that the timeout error message was confusing to the user. Jared suggested having the timeout be a silent design, one that only becomes relevant if the user tries to do certain things.
What do you think the best solution(s) would be for this example?
I think the timeout error message could give the user more specific information, like “your confirmation has been emailed to you.” That might eliminate some of the user’s confusion. I also think making it a silent design could improve user experience.
Find another good article on Jared’s User Interface Engineering website and share a link to it. Why does it look like a good article to you?
I read another article by Jared: https://articles.uie.com/why_sketching/
It’s an article about how great designers sketch for a variety of reasons, to organize ideas or communicate for instance. I like to sketch and after reading this article I think I will make it a bigger part of my process.