My experience with the k790 is a great lesson in why product managers and designers continue to fight about whether features or experience should drive product development. I bought the phone primarily because I wanted a phone with a "real" camera and at the time it was (arguably) the best cameraphone out there (3.2 megapixels, auto-focus, xenon flash, etc.). I did lots of research and so on and bought it primarily on a features basis. After using the phone and camera for a few weeks, however, I realized that while the k790 has an amazing camera for a phone, especially for stills, it's going to be a while before any cameraphone is going to hold a candle to a decent dedicated point-and-shoot camera (e.g. Canon Elph) let alone a digital SLR. So much for features.

So, you'd think I would have been disappointed but in fact I had already grown to love the phone based solely on the software interaction design. It's among the most impressive pieces of small-device UI design I've encountered (and that includes the iPod which is obviously amazing, but has a much, much easier job description). It's far from perfect, of course, and there are some patently silly things as with all phones (for example, when looking up contacts, you can only search by first name rather than first or last, so typing "JO" gives me "John Zapolski" but not "Oliver Johns"). But, there are so many places where the designers got it right. And, what I mean by getting it right is that they understood the context the phone would be used in, figured out the most likely thing or things that you'd want to do, and then designed the interface to make those things either extremely easy or automatic. I regularly find myself pleasantly surprised by the interface which is rare indeed, as we all know from countless bad experiences. And, as an interaction designer myself, I can tell you that it is incredibly difficult.

It's the little things like when scrolling vertically through a list of your contacts you can then scroll horizontally through their different contact methods (home phone, work phone, email) and choose the one you want. It (mostly) just feels incredibly fluid.

By contrast, the Nokia suffers from having to support a lumbering, generalized operating system so that I have the option of downloading lunar calendars, golf handicapping systems, and all kinds of other pseudo-useful Symbian applications but at the expense of doing the things that matter with any degree of subtlety.

(Note: This was all written pre-iPhone, which generally out-fluids the Sony.)

Designers of mobile applications have long understood that mobile devices are operated within a context of significant constraints and environmental distractions. Despite this knowledge, however, many mobile applications are designed as if they were merely shrunken desktop or Web applications.

To encourage consideration of the specifics of context for mobile interactions and to highlight new user-meaningful opportunities latent in always-on, always-carried devices, this article describes a context model for mobile interaction and a set of design heuristics for successful mobile interactions.

Feedback welcomed!

...man in the normal use of technology...is perpetually modified by it and in turn finds ever new ways of modifying his technology. Man becomes, as it were, the sex organs of the machine world, as the bee of the plant world, enabling it to fecundate and to evolve ever new forms. The machine world reciprocates man's love by expediting his wishes and desires....

In contrast to the expectations of many of our technology clients, we have found in our research that youth discourse about telephones focuses much more heavily on emotions rather than technology and features. The implications for designers of mobile devices and services is to focus more on the human side of this emerging technology, new youth identities, and popular desire for entertainment, fashion and companionship.