Observing the new generation of web and App design, a new trend (or style) is taking the world of UI design by storm; flat design.
The usability crisis is upon us, once again. We suspect most of you thought it was over. After all, HCI certainly understands how to make things usable, so the emphasis has shifted to more engaging topics, such as exciting new applications, new technological developments, and the challenges of social networks and ubiquitous connection and communication. Well you are wrong.
Direct manipulation was introduced by Ben Shneiderman in 1982 and is a style of Human Machine Interaction (HMI) design which features a natural representation of task objects and actions promoting the notion of people performing a task themselves (directly) not through an intermediary like a computer. Virtual Reality can be viewed as a field which can draw upon the principles of direct manipulation for Human-Computer Interaction (HCI) design or as an example or extension of direct manipulation itself. In VR, not only can task objects and actions be naturally represented, the task environment can be naturally represented as well. With either view, an understanding of direct manipulation principles is essential for the successful design of human computer interfaces in virtual environments. The remainder of this article will discuss the characteristics and benefits of direct manipulation along with its relation to virtual environments and the foundation areas of computer science.
Many designers mistakenly think a sketch is a wireframe. They are similar but they are not the same thing. Both are useful for illustrating an interface concept, but a wireframe and a sketch are done in different mediums and produce different results.
By now, you’ve probably seen the navicon — an icon with three stacked lines representing a navigation drawer menu that can be shown or hidden.
The transformicons design concept — which We’ll talk about in just a bit — adds to the navicon by smoothly transitioning it to another icon after it’s clicked.
To code or not to code? For designers, that’s a very contentious question. Clients like designers who code because (among other reasons) that’s one less body on payroll. Design advocates, on the other hand, often see code as a technical limitation that stifles creativity. To make matters worse, the information ecologies we all work in refuse to stand still. By looking carefully at some of our favorite arguments, however – and by taking them within the context of our ever-evolving digital landscape – we can begin to make a case for when working in code makes sense.
Several years ago, Andrew Maier penned an article on the use of prototypes in website design and development. In light of my own recent work in prototyping, one of the comments to that article stood out:Any kind of prototype that involves programming or markup sounds scary to me –that’s the fastest route to a “developer-y” looking site rather than a truly designed –graphically as well as functionally designed –site.
The selection of UX guides and books has grown exponentially in the past few years. Rosenfeld Media and A Book Apart are just two of a number of publishers with a UX-focused audience. The expanding supply is exceeded only by the demand for more data, more depth, and more detail
It’s a new age for healthcare – medicine is getting more advanced and technology is helping us take better care of ourselves. As more and more smartwear are getting primed for monitoring one’s fitness, alongside their counterpart health apps, this opens opportunities for apps that help you monitor your health problems as well.