The UX SLASH UI Analogy

If you imagine a product as a motorcyle, the frame represent the code which gives it structure. The engine represents the UX design: measuring and optimising against input for supporting the riding function. And UI design represents the cosmetics of the machine–its presentation, its handling and those final touches of chrome.

Despite how simple that may have sounded, there are many complications and misconceptions when it comes to the differences between UI and UX design, and I have seen plenty of heated discussions at UX Meetups and forums. The amount of times a hiring manager has emailed me asking for a UX-SLASH-UI Designer I feel it needs a whole new category!

As far as I understand and to put things very simply a User Interface design is the part of the product that faces the user when he looks at the site, and the User Experience is how they feel when they look at the site, please correct me if I am wrong?

Good user experience is the art of weaving through traffic, pulling a wheelie (I'm not condoning this of course) effortlessly. Though, in contrast, the shaping of the bike helps it make those turns is good UI, and the Pirelli tyres so you don’t slip off the road, is also good UI. In short, the ENTIRE package is what makes it good UX, whereas good UI is the framework that makes it work.

I'd be keen to know if people agree with this and whether you have your own distinction?

Be sure to follow visit InterQuest Group website for more articles and maybe even a UX job or two.

?(One of my better User Experiences)