7 posts tagged “experience”
I know I can come up with something and it shall be launched! In the meantime, check out this new design I made. At some point I should actually put some content into the design, but I enjoy this. This one is called Plenatude.
It's not nearly as complete as the others, but I like the colored rays. I think I'll build on this one and get back to you. Here's another view without the navigation links, you can see the rays better.

I also made a "People's Software Manifesto". This should count as content.

In user interfaces, since Windows operating systems have rolled out several editions now, supposed standards in interaction have been acquired over time. The cursor has become a very important tool for interaction as it relates to its visual context. The difference between the cursor as a pointer and a cursor as a hand could mean the difference between moving and clicking. There are certain controls that have been acquired into user interfaces for standard interactions. For instance, buttons, radiobuttons, comboboxes, listboxes and checkboxes. Toolkits enable us to build interfaces fast but they can limit the possibilities in excellent interaction design for our users, but that's another post.

Interaction design not only requires a bundle of testing but it requires a lot of personal experience. As a developer, it would be incredibly difficult to design a product without any familiarity to the end result. Without personal experience to the end product, emotional attachment will be bias in favor of ease of development. As an interaction designer it is important to remember that product experience to users, no matter what the product, count on tasks being obvious.


Taking a quick glance at the two remotes above, what tasks can you determine will be obvious to complete. Let's suppose that the person will be watching TV in the dark. Without being able to look at the remote, will it be easy to figure out what buttons to press? The remote on the right uses differing shapes, placement and space around the buttons to distinguish tasks from one another. The user will be able to learn how to use the remote during daylight or under the light. Familiarity with the product soon begets the obvious nature to complete tasks.
Of course, on the left, lights allow the user to see which button is which and how to complete a task like changing the channel. However, due to the number of buttons and the few spacing there is between them - the user will have to look at their remote every time they want to use it.
Obvious interaction is not so obvious when it of course depends on perspective. Anyone on a team will have a differing perspective of obvious interaction when they are looking at the same product. However, the key point in making things obvious is about taking away prerequisites. So for instance, in the remote example lighting was taken away. Without looking at the remote which is easier? How often will the user need to relearn the interface? How long will it take to learn the interface the first time? These are a few important questions when thinking about obvious interaction.
I decided to write a quick prose on interaction design and software. It's simple, but I think it gets the point across.
Since the dawn of time we have learned to progress by
connecting and building off of the world around us. We
have learned how to communicate, explore and create
through example, experimentation and evolution. Yet,
in a world becoming more and more dependent on IT,
we are only beginning to understand the many ways to
interact with the content around us.This is our journey. Our passion is software.
- Thomas Holloway

Gmail, adds a few shortcut keys to navigate around the site. Use K to move up and J to move down in the list of e-mails. Hit O to open an e-mail, X to select it, # to delete it. These are subtle additions that can make a great interface even better to use. Another great example - Microsoft's Visual Studio.

We underestimate our ability to take advantage of the keyboard in most applications today. Keyboard commands often get supplemented by menus, buttons and other pieces of user interface that typically will break our train of thought. Can you imagine what it would be like if we wanted to know a method for a class in some object in Visual Studio without intellisense? Imagine how much pain we would go through if when we wanted to go to a website we had to choose from a listbox instead of typing in a url to one or searching for it.
While this video is substantially old, it is certainly a good one to watch. Tim Sneath talks about a lot of the different aspects of Silverlight, it's capabilities, performance aspects, bits and pieces about the lightweight embed CLR. Not only that, he makes a few great points on web experience and providing a platform that takes advantage of client processing power, with multi-threaded multi-core computing, in shifts with fundamental changes in software platforms.