Print

Zeichick’s Take: What is UX? An overloaded operator



Alan Zeichick
Email
April 6, 2011 —  I was recently at a party—okay, the speaker’s party at iPhone/iPad DevCon last week—where it was obvious that the speakers neatly bifurcated into two groups: those who recognized Mike Oldfield’s “Tubular Bells” playing on the stereo, and those who didn’t.

(You could also identify the Tubular Bells cognoscenti by the relative abundance of gray hair, compared to those grooving to the sounds of Girl Talk.)

Here’s another litmus test: What does “UX” mean to you? The definition may be revealing about how our world is changing.

If you see UX and think Unix (or perhaps UNIX), then you belong to the world of classic IT. Maybe you’re thinking about HP-UX, which is Hewlett-Packard’s version. Or A/UX, which I actually had running on a Mac Quadra a billion years ago. Either way, for me, until recently, UX==Unix.

If you see UX and think User Experience (not Unix), you’re part of a newer generation, perhaps inspired by Donald Norman’s classic “The Design of Everyday Things,” maybe thinking about AJAX or rich Internet applications. UI is so passé; it’s all UX now. They say there’s an app for that.

Unix lived and died by the command line, and by the ubiquitous and essential man pages, which told you everything. It was a world where a single mistake—forgetting an argument, making an argument upper-case instead of lower-case, putting parameters in the wrong order—would lead to disaster. If you knew what you were doing, you were a guru. If you didn’t, you were doomed.

Today’s User Experience-driven world is diametrically opposite. Android phones, Web applications and iPads have minimal controls. Everything should be modeless, whenever possible; everything should be obvious; pop-ups are bad; grayed-out options are bad. If it’s not intuitive, you’ve failed. If you ever watched a child pick up an iPhone or an iPad for the first time, launch an app and start painting or playing, you’ve seen what UX is all about.

There are no man pages for mobile applications or modern interactive Web applications. In fact, often there’s no help system or README.TXT or any end-user documentation whatsoever.

In object-oriented development, it’s a bad practice to overload an operator or a method with one that does the exact opposite function. (It’s like having to press the Start button to shut down Windows; it’s silly and counterintuitive.)

Yet that’s exactly what we’ve done by overloading UX. We’ve taken an abbreviation for Unix, traditionally the operating system that requires the most up-front knowledge by its end users. Now it refers to the goal of ensuring that users can simply figure out how to use a system intuitively, without any training or documentation or anything.

Like one of Girl Talk’s mashups, an app with a great UX should simply get you moving. What’s not to like?

Alan Zeichick is editorial director of SD Times. Read his blog at ztrek.blogspot.com.




Share this link: http://sdt.bz/35420
 
Most Read Latest News Blog Resources


Comments


04/09/2011 07:34:50 AM EST

Nice article. For me ux will always mean unix, but having it mean user experience also is fine with me. Give me a man page in a terminal any day, the extra information and immortality of it is like gold. I can't bring myself to use touch or iDevices.

Australiaundisclosed-ux


04/11/2011 03:54:56 PM EST

UX overloading does not bother me so much. That Unix relationshio is rather dated as demonstrated by the examples which are System V Unix systems. These days, most people think of Linux when they think of a Unix system. On the other hand, the vast majority of Unix users are not even aware that their MacOS, iOs or Android device are Unix systems. The change in definition of "UX" turns out to be a nice metaphor for the evolution of software. But, at least, Unix and User Experience have some relation to each other. The TLA overloading I hate the most is "IP" as in Internet Protocol or Intellectual Property. They are 90 degrees out of phase from each other and would normally not cross paths except that they may both be used in IT environments and sometimes depends on whether the speaker is wearing a suit or a T-shirt.

United StatesBrian Walker


Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
All manner of Unixes are finding homes
What has become of the many offshoots of Unix? We take a look at some Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
MAY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Creation
To write better software, cultivate your ability to be creative.
05/19/2012 07:40 PM EST

Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
05/16/2012 12:45 PM EST

How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
05/14/2012 12:18 PM EST

Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
05/12/2012 07:05 PM EST

The world as story
An artificial-intelligence system at Carnegie Mellon seeks to understand the world by making statements about it.
05/10/2012 06:39 AM EST

The Rise of the Brogrammer, or the Rise of the Sexist Programmer?
Women in Silicon Valley get vocal about sexist ads and campaigns that contribute to a tense work environment.
05/09/2012 03:14 PM EST

 

Events calendar tab
5/23/2012 to 5/24/2012
Chicago
IEG

6/3/2012 to 6/7/2012
Orlando
IBM Rational

6/10/2012 to 6/15/2012
Las Vegas
SQE

6/10/2012 to 6/15/2012
Las Vegas
SQE

6/11/2012 to 6/14/2012
Bellevue, Wash.
AMD