Avoiding The Uncanny Valley of User Interface
codinghorror.com
codinghorror.com
In my experience the metaphor doesn't stretch to RIAs. My start-up's main application is precisely one of those "RIA that pretends to behave like a desktop app", and thanks to Flex we've been able to get a good enough approximation. Result? Our users don't feel uncomfortable about it (although we have had the odd user who seemed to expect that everything would be instant even though it was a web-app). On the contrary, our users love it, and have commented on it positively many times.
I guess people care less about that last 1% when looking at a web application than when looking at a humanoid robot. Which means stretching the metaphor in this direction doesn't quite work.
I clicked on your profile and I assume you are referring to your website http://woobius.com ? I didn't try it out but I did checkout the screenshots. See, to me, your app looks like a web application. It borrows some of the visual metaphors of a desktop app, but the actual interface skin looks very much to me like a web app.
To take Jeff's metaphor, your app to me is like a C3PO. He's got all of the functionality and parts of a human (face, limbs, speech, etc.), but on the surface he looks like a robot, so it doesn't creep you out when he hobbles along with his stilted gait.
Anyhow, I thought the article was a bit long winded to make such a simple point, but for me the point resonated in the end.
For example, stupid cnnsi.com has a "main window" that has some things at the bottom that look, feel, and act like links. Yet I cannot middle click them to open them in a new tab. This annoys the bejesus out of me. Another example is desktop-emulating applications who don't have a fully-functional right-click menu like I'd expect.
By emulating other things, you put expectations into your user's mind about what sorts of functionality it should have. In this respect, it is analogous to the uncanny valley. The mimicry alone has created expectations that can cause frustration. But, that doesn't mean, that mimic'ing is inherently wrong or bad. It just means you have to do it right. You have to meet those user's new expectations.
I hate the idea of having "emulated" windows within a single browser window. It looks messy and confused.
So on that sort of point I agree. I'm not sure what other examples there are though.
Most web-apps that emulate a desktop app are still clunky and nowhere near as smooth to operate as their desktop counterpart. Meebo is one example, and all the web "desktop replacements" are another. You're always waiting for something to load, or javascript doesn't resize the window properly, windows that get dragged around don't move smoothly, etc.
Taking a tangential step, computer automation is similar when it purports to be able to help you, but doesn't understand you well enough to do so; like MS's "clippy".
In contrast, Google's "I'm feeling lucky" button is automation that fulfills its promise (though the name emphases that luck is involved). Google can predict so well what I want, that this button is (very often) right. An awesome achievement. I added a simple command-line google lookup, to go directly to the page, and it's freaking me out how well it works:
> cat ~/bin/g
firefox google.com/search?q="$*"\&btnI= & open "http://google.com/search?q="$*"\&btnI="
open -a "Safari.app" "http://google.com/search?q="$*"\&btnI="http://www.youtube.com/watch?v=bLiX5d3rC6o&fmt=18
Two years from now we'll be seeing that, or not seeing it as the case may be, in movies. Another two years after that it will be in the AAA video games with 9 figure budgets. And another two years after that you'll be able to do it from a Japanese cell phone.
God I love technology.
See, the valley can exist because humans stay the same, at least to our brains. We don't madly change form or shape every 20 years. But user interfaces do. So how do our brains know a web interface looks too much like a desktop interface? It can only know because we know what both are "supposed" to look like.
But kids being brought up on web interfaces that look like desktops will not have a valley because to them that looks normal. There is no set "desktop" look or web interface "look." Its only what we've created. Create something different, and the valley will go away.
If you have a web app that looks identical to a Windows/OS X desktop app, but behaves oddly, it will irritate your customers in subtle but significant ways.
I was pretty disappointed they didn't try anything different, but I guess the aim of that was to attract people who actually like Office in the first place.
Atwood, I think, is saying that web applications shouldn't be like desktop applications because it violates the user's expectation of how a webapp should be.
Applying the Uncanny Valley to this says that it's not bad for web apps to behave like desktop apps -- it's bad for webapps to signal that they have behave like desktop apps, and then fail to live up to that expectation.
This problem affects other products, too. For example, imagine a really awesome semantic search engine called CantorSet. You can throw all sorts of questions at it and it appears to come up with the answer. "What did Bush say at the last G8 meeting?" Wow! Amazing!
But then you ask questions like, "Why did my wife leave me?" No answer! Wow, this thing sucks.
It's less about what the webapp does or doesn't do, and more about the expectations it sets and whether or not it lives up to them.
If you look at 280 slides, it doesn't behave quite like a mac, but it's still intuitive. People understand the WIMP.
I think he's conflating crappy Swing java apps with webapp UX.
I guess I should write more frequently and more in depth.
As the complexity of web apps increases users will need to get used to the idea that they need to learn how to use each app to get the most out of it which is how it works with desktop apps. Try to compare the UI between desktop apps such as a music editor, 3DSMax and MSWord. Each uses different UI controls (sliders, knobs, text input etc). Each app is complex and has an associated learning curve. If people consider the app useful they will invest the time in learning how to use it.
I recently had to learn how to use Aftereffects. The UI and work flow were completely foreign to me - none of my existing knowledge was transferable, but I learned how to use it because I needed the features it provided.
Ultimately the market will decide. My guess is that the line between desktop and browser will continue to blur and will one day disappear.