OCGM is being presented at CHI 2010 and a prime example of OCGM

I know this is a bit late, because my co-author has already reported it, but I am very happy to announce that some ears have been listening. The CHI ’10 Workshop, “Natural User Interfaces: The prospect and challenge of Touch and Gestural Computing” has granted an audience to the new metaphor for design.

The workshop is going to be an all day event on Saturday, where each of the authors will present and offer discussion about their position papers. The real benefit of this is that in such a narrow expertise, you really get amazing peer reviews and leave with amazing new ideas. These types of scoped interaction gatherings are a wonderful thing to foster innovation and creativity. It’s like a specialty conference inside of a specialty conference.

One of the most interesting things, as I read the position papers that were accepted, was a cite from my writings.  In the paper, “Natural User Interfaces: Why We Need
Better Model-Worlds, Not Better Gestures.(PDF)”  the authors argue the need for separation between “symbolic gestures” and “manipulations.”

Manipulations are not gestures.
We believe in a fundamental dichotomy of multi-touch
gestures on interactive surfaces. This dichotomy
differentiates between two classes of multi-touch
interactions: symbolic gestures and manipulations.

They go on to define each specifically.

For us, symbolic gestures are close to the keyboard
shortcuts of WIMP systems. They are not continuous
but are executed by the user at a certain point of time
to trigger an automated system procedure. There is no
user control or feedback after triggering.

…

The opposite class of multi-touch interactions is
manipulations. Unlike symbolic gestures, manipulations
are continuous between manipulation initiation (e.g.
user fingers down) and completion (e.g. user fingers
up). During this time span, user actions lead to smooth
continuous changes of the system state with immediate
output.

It is a lovely way to differentiate the two and I couldn’t agree more. As the crevasse between the two interactions widens, we begin to see many more differences. I have gotten a few emails from bewildered Interaction Designers, both young and old, asking “why do we need this separation?”

The answer is not quite as apparent as it will be in the next few years. We need this distinction because designers and developers need to think about experiences differently. We need to plan and design for interactions in a fluid and responsive way. Arbitrarily throwing a manipulation on a destructive action, could have dire consequences for the user. Using a complex gesture for a simple help menu, would create a pause in your user’s experience.

Let me give you an example of the two with a nice crisp physical metaphor demonstrating OCGM

You have a pile of sticks.

Just a pile of sticks

Think of the sticks as Objects. Think of the table as a Container. Now let’s examine the relationship between the two. The container contains many objects, therefore operations executed on the container will have multiple effects on each of the singular instances of the objects.

Now, let’s give you a few things to do those operations. First, let’s give you a hand, which we will call a Manipulation. Then let’s give you a chainsaw, which we will call a Gesture.

To move the sticks, to rearrange them, to take them in and out of the container (on or off the table) we can use a hand. It might not be the most efficient, but it gets the job done and we can do these methodically. All the while, we can always undo our actions easily.

If someone comes up and talks to us, we don’t hesitate to respond because there is nothing really at jeopardy here. In fact, it might be nice for someone to come up and interact with us while we are doing these chores.

This also puts us at ease. We can do these things and if we get interrupted, we have no stress. Why? Because everything is undo-able. Things are easily moved back and forth with no real consequences. Even if we push the entire stack to the ground, we can easily pick them up and put them back. One handed.

This is the physical realization of a manipulation.

a Chainsaw "gesture"

Now, we take your chainsaw. This is a complex piece of machinery. This is going to take focus, intent, and possibly a plan to implement. The things we can do with this are destructive, irreversible, and should be taken with care because they could damage other things around the single container or multitude of objects.

We consult the manual, don safety gear, check the gasoline in the chainsaw, pull the handle, and then fire it up. Each one of these actions were simple and were not harmful, until they were combined. Combining all of these harmless manipulations results in a gesture that could do harm.

Let’s think about what we just did though. We had to do things in a certain order, we had to do each of them, and they were predetermined by something other than us.

Now could we take our gesture chainsaw and destroy the Container and all of the objects inside? Yes. Could we also affect other containers and things in the vicinity? Yes. There is no undo, when its done its done.

This is the physical realization of a Gesture.

So I digress….

Why is it important in interface design to distinguish between the two? To promote a better experience through expected interactions and results. Do you want your users concentrating on the most mundane of tasks? Let your user relax when they can. Do not make them concentrate on these details of where to move an object when they don’t have to.

Allowing your users to free up precious concentration allows your interface to become more complex. Right now, the main impediment for complexity in interface design is the user. By distinguishing between the two, we can begin to create more complex interfaces by relinquishing as much focus as possible, when possible.

Spray on liquid glass is flexible and will revolutionize the touch screen

I hope some of you are as excited as I am about this recent discovery.

This is spray on liquid glass on a microfibre. They caused this fissure to demonstrate the properties.

One of the biggest drawbacks to a public mounted touch screen is the transfer of germs from bystander to bystander. This is not as much as real as it is a psychological boundary we have encountered. In exit interviews from User Experience tests we consistently get feedback about the cleanliness of the surface and the other participants hands. We had to put antiseptic baby wipes near the Surface units to help alleviate this problem.

Cleaning touch screens is an odd process. Depending on the material used, be it a rough or smooth material, it usually had special instructions about cleaning. The typical monitor has a special non-glare coating and recommends using soap and a damp cloth. Using non-glare finishes on touch screens have similar recommendations. Do not use cleaners or antiseptic solutions because they will damage the finish and possibly remove the protective coating.

What this amazing discovery gives us is something that will innovate the market in the eyes of the public.

Here is the main article about the glass.

Spray-on liquid glass is transparent, non-toxic, and can protect virtually any surface against almost any damage from hazards such as water, UV radiation, dirt, heat, and bacterial infections. The coating is also flexible and breathable, which makes it suitable for use on an enormous array of products. (via physorg)

This is amazing. This gives us the ability to spray a coating on a touch screen and then the ability to clean it with antiseptic germ killing chemicals without the harmful side effects of destroying the surface or the experience. It is also so thin it allows the transference of touch to the unit.

Long live physics!

Gesturcons: an icon language to describe natural user interface gestures

One of the prevailing themes of my writing is the ability for everyone to gain common grounds when discussing interactions. I believe one of the keys to this is a common metaphor, OCGM (Objects, Containers, Gestures, and Manipulations) as well as a set of icons for use in design. When sketching out the user experience it’s important to note the interactions. This is especially true in state diagrams, specs, and other interaction design documents. In my first installment of Gesturcons, I present to you the Gesturcons : Touch Pack 1.0. These are being released under the Creative Commons License and I hope that you all find some good use for them in your designs and experiences.

This is the first batch, for touch. I also have Spatial, Voice, and a few others in the works.

Updates

I’m using a simplistic graphic design language to represent the actions by a user. If we use OCGM to boil down each action, we get just a few basic actions that all can be constructed from. To combine these actions together I use only two different states. They either happen at the same time, or they happen consecutively.

After we have established exactly when the action takes place, we can then talk about the specific actions. I use only a few different types of basic actions as well. The only addition you see here is the Location Specific Icon. That means that the exact placing of that particular input is predetermined by the system for the manipulation or the gesture to be successful. As an example, the Red X at the top right of Windows is a location specific manipulation.

The path icon is pretty straightforward. It means that the path the user has to take to accomplish the goal is specific and is going to be bound by guidelines. Those rules are what you have devised, but the path is specific.

The rotation icons are dual purpose. They can mean an actual spin of the input or a spin of the action. This could be boiled down to a Path, because they have to follow a certain pathway to achieve success. I find it easy, but others find it difficult to also put a rotation as a simple path. So I added it here for ease of use. Notice the use of Twin when its dual simultaneous inputs.

To sum up the use of the Gesturcons, I present an example of how you could build your own gestures using this language. In this example I demonstrate the visual identifiers to show a gesture of the question mark.

I’ve also updated the Zip file with all these new gestures. Enjoy and happy designing.

Here is the ZIP, which contains all the PNGs, the Illustrator File and an EPS as well. These are being released under the Creative Commons, which means you can use them internally as much as you want but you cannot package them, redistribute them, or include them in any professional product.

License here

Gesturcons by Ron George is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License.
Based on a work at blog.rongeorge.com. Permissions beyond the scope of this license may be available at http://blog.rongeorge.com/design/gesturcons/.

Dear Ron: Any Advice for someone to escape the ‘telecommute’ career path?

I get this question quite frequently, so I thought it best to address it in its own post. Here is the question.

Any advice for someone with tons of experience as a designer and developer, but stuck in upstate NY with a dearth of telecommute opportunities?

Answer

The first thing I would tell you to do is to watch and read everything from Daniel Pink you can get your hands on. If you are like me and you just want the lazy route, atleast watch this video of a talk he gave at TED (embedded below).

I’m a big fan of Daniel and the things he has to say. Basically, he sums up the threat of telecommuting and how innovation and decision making will solve many problems. Anything that can be done by telecommute, WILL be done by that method. If it does not require decision making, it will be done by telecommute. It’s cheaper, easier, and faster. Many of the offshore development houses have an unlimited amount of resources they can throw on the project, so scalability is never an issue.

The key to success in this day and age is in design and decision making. Put yourself in the position to make decisions that directly affect the product’s success. Being a designer that can actually shape the product is the key to accelerating your career path. Make an impact and ensure it’s success.

Development is a great skill, but you only need to know enough to make good design decisions. The ability to work out a specific worker algorithm to accomplish a task is beyond the scope of your needs. If you are talking about web design, then development plays a much higher need. The ability to understand and incorporate web development into your designs will save you, your team, and the development team tons of wasted cycles.

Summary

Know enough development to propel your designs to the front of the pack. Concentrate on a specific part of design or interaction and own it. Become it.