Abstract user interface prototypes offer designers a form of representation for specification and exploration of visual and interaction design ideas that is intermediate between abstract task models and realistic or representational prototypes. Canonical Abstract Prototypes are an extension to usage-centered design that provides a formal vocabulary for expressing visual and interaction designs without concern for details of appearance and behavior. A standardized abstract design vocabulary facilitates comparison of designs, eases recognition and simplifies description of common design patterns, and lays the foundations for better software tools. This paper covers recent refinements in the modeling notation and the set of Canonical Abstract Components. New applications of abstract prototypes to design patterns are discussed, and variations in software tools support are outlined.
The arrow and its brethren are everywhere on our computer screens. For example, a quick examination of the Firefox 3.0 browser, shown in Figure 1 in its standard configuration, yields eight examples of arrows—Forward, Back, and Reload buttons, scroll bar controls, and drop-down menus that reveal search engine, history, and bookmark choices.
An interview with David Malouf on his article, Foundations of Interaction Design. We discuss several foundations of Interaction design including time, metaphor, abstraction, and negative space. David also provides greater detail to comments posted on his article from readers from around the world.
Keynote has been spoken about in the past as a great tool for creating wireframes and prototypes, but not much for animation. I love Keynote because it’s fast, free, easy to learn, and it works. Recently Andrew Haskin of Frog Design recreated Google’s Material Design Video in Keynote. I was impressed with his ability to recreate complex animations in what seemed like a very simple program. Using his Keynote file as a guideline, I dug in to the mechanics and mastered animating in Keynote in roughly an hour.
Prototypes often model one flow of interaction--the path that users are most likely to take. But when we create interaction designs with dynamic and complex flows, we often need to include deviations from the sunshine scenarios to see whether they work. In this article, we'll look at how to do this Visio and Axure.
There are a exponentially growing amount of applications being developed. Some of them vanish at an early stage, while others grow to be quite (and sometimes extremely) popular. What really dazzles me is how sucky many of them (both the popular and the unpopular ones) are regarding how they deal with user-interaction.
The vast majority of web sites commit usability and design violations that make it hard for users to find relevant content and functions. These problems are not difficult to diagnose or remedy. How many of these "user crimes" is your web site guilty of committing?
I recently conducted a study into the helpfulness (or lack thereof) of zebra striping—the shading of alternate rows in a table or form. The study measured performance as users completed a series of tasks and found no statistically significant improvement in accuracy—and very little statistically significant improvement in speed when zebra stripes were implemented.