Is the iPhone stunting mobile phone R & D?

A few weeks ago, a colleague and I were talking about the iPhone and postulating about the catalyst to its touch-based approach.  For starters,  I think the company was considering adding phone functionality to to the iPod.  With that in mind, I imagine that one day, Steve Jobs was browsing the web on his phone and became frustrated with the experience: small screens, super slow load times, improper page rendering (if pages even load at all), and painful navigation.  He challenged a design team to improve the experience, and the first piece of the puzzle was to somehow increase the screen size without significantly increasing the phone size.  With a bigger screen, more of a web page obviously would fit on the screen.  But, what about scrolling and clicking on links and buttons?  Those tasks can be awkward or inefficient when using a directional pad or some other type of control.  But what if the screen became the input device?  Well, the rest is history…

On the other hand, my colleague believes that Apple intentionally set out to design a device based around a touch screen because, unlike a fixed keypad, a touch screen’s controls can morph based on the application.  If you’re using a phone, the screen displays a number pad.  If you’re messaging, the screen displays a keypad.  If you’re browsing the web, the screen displays browser controls.  If you’re playing a game, the screen displays controls customized for the game.  The phone’s screen is a shape-shifter, allowing the device to morph into a phone, an internet browser, a gaming device, etc.

I found that theory pretty interesting.  My colleague’s a hardcore Apple fan, so might he be giving Apple a little too much credit?  After all, before the iPhone, Apple didn’t show much commitment to touch screens.  Apple remains one of the only major notebook manufacturers without a tablet model.  And wouldn’t the iPod, a device that could benefit from touch-based controls, have been an obvious candidate for a touch screen makeover long before the iPhone came around? 

Who knows.  I suppose I could do some digging to see if I can find out the history of iPhone’s design.  But, I’m not really concerned about that.  I’m more interested in how the iPhone has been a disruptive technology causing a flood of touch-based phones to hit the scene.  Every touch-based smart phone is inevitably compared to the iPhone, and analysts began writing off stalwarts like RIM and Palm with every month that went by in which they didn’t have a serious competitor.  Same goes for Microsoft and the delays around the more touch-friendly Windows Mobile 7.  And we all saw the hype around Google’s entrance into the market, though that seems to have died down given that apparently no manufacturers displayed Android-based phones at the Mobile World Congress (guess the analysts were wrong). 

What I worry about, though, is whether touch screens are unintentionally stunting further innovation in mobile input technology.  Don’t get me wrong, touch-based phones certainly are innovative and have a lot of benefits.  But while the technology lends itself to improved web browsing and multimedia functions, it’s not as adept at core phone functions like calling and messaging.  Because the interface isn’t designed around a particular function, it ends up having a jack-of-all-trades, master-of-nothing effect.  I don’t think touch screens are a fad, but I’m not the only one who questions whether they are the be-all-end-all input method (see here and here).  There are interesting alternatives.  But as manufacturers continue chasing after Apple and the iPhone, I worry that R & D around other input technologies will move at a molasses-like speed until touch screen hype fades and touch-based devices become status quo.

In a follow-up article, I challenge whether touch screen technology really is a step forward based on observations as well as my own experiences with a touch screen phone, an HTC Touch Diamond that I’ve been using for several months.  In the meantime, what do you think about touch screen phones?


Posted Mar 23 2009, 08:09 AM by Brad Moczik

Follow Me on Twitter

Did you enjoy this article? If yes, then subscribe to our RSS 2.0 feed or

Comments

Civisi wrote re: Touch screens: love ‘em or hate ‘em? (part 1)
on 03-23-2009 10:08 AM

It's simple, really. The iPhone is a touchscreen because Steve Jobs doesn't like buttons.

Brad Moczik wrote re: Touch screens: love ‘em or hate ‘em? (part 1)
on 03-23-2009 11:20 AM

You’re right.  Well, he at least doesn’t like a lot of buttons.  The problem is, touch screens aren’t really eliminating buttons per se.  In fact, rather than confining developers to a fixed control scheme, touch screens are doing the opposite: they’re providing developers with a blank canvas.  Sure, there’s constraints within the development tools, but really, each app theoretically can display its own unique set of controls, which can be as few or as many buttons as developers want.  

While the visual aspect of touch screens makes discerning buttons’ functions a little more intuitive, it does so at the expense of the familiarity that comes from the sense of touch.  Imagine if the keyboard on your laptop was replaced with a touch screen.  Could you still type without looking at the keys?  Probably not—at least not at first.  Maybe eventually you could as long as the keyboard controls were statically displayed on the touch screen.  But what if one minute the touch screen shows a keyboard and the next minute it shows a Wacom tablet?  It would be even harder to train your fingers to learn the key locations.  I’m going to talk about this a little more in part 2 of this article.

Thanks for your comment!

download games wrote re: Is the iPhone stunting mobile phone R & D?
on 12-05-2009 4:24 AM

iphone is getting familiar with users so this is now not very tough to do R & D with it. But yes there are many online games and apps which are really new for users so those will take some time.

Add a Comment

(required)  
(optional)
(required)  
Remember Me?
Windows is a registered trademark of Microsoft Corporation.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems Themed By nb development