- Don't look back
- Is support for OSS optional in your business?
- Nokia N810 Tablet + WiMax
- Vendors need to right-size their products
- Dolphins Invade Sun Campus!
- State of Open Source
- MySQL Workbench: open source data modeling
- Comments on The 451 Group's Database Report & Red Hat's 4Q revenue
- Kaplan: Guiding open source in IT
- Can the transportation market teach us anything about the software market?
February 13, 2008 | Comments: (0)
Why do cell phones suck so much?
On a recent Saturday night my wife and I went out shopping for cell phones. (I know, I know, doesn't sound like much of a date.) I'm going to replace my Treo 650 and my wife wants to replace her Motorola RAZR with something that's easier for texting.
We stopped by the local AT&T store to see what's on offer. (Although my wife's on Verizon.) Lots of choices but still pretty frustrating. There are phones that have 3G GSM and Wifi (but weigh too much) there are phones that have a great user interface (but no keyboard) there are phones that have a camera (but no wifi or vice verse) and phones that have all the right features but you'd never be able to figure them out.
I got to wondering a very basic question: why do cell phones suck so much? My thesis is that they suck because they've been designed by committees. I tried out several Windows Mobile 6 phones and they just seem to have the user interface wrong. Maybe I'm too used to the Palm Treo at this point to switch. But should it really take so many clicks to send a message? And why do I give up so much screen real estate for fancy windows borders, buttons? You get the feeling that the user interface is designed by someone who has no idea what the underlying hardware will be. And of course, that is how it's designed. So while there are lots of good Windows Mobile phones (AT&T Tilt, Samsung BlackJack II, Samsung I760 among others), they never feel like the software is designed for the hardware. More of a one-size-fits-none solution. Maybe I could get used to the user interface, but it's not always obvious how to do even basic tasks. You've got to guess your way through menus and options and I found myself unable to get back to where I started without going back to the Windows menu.
It's worth contrasting that experience with the iPhone. You can pick up an iPhone and figure it out in a couple of minutes. It works the way you would expect it to work. I don't know if this is because Steve Jobs is a relentless micromanager sweating every detail of the user interface. But that's my guess. And if it isn't Jobs doing it, he's instilled a culture that cares deeply about these things. (And that's pretty much the way things were at Palm and why I love the Treo user interface.)
I'm not saying it's easy to design a smartphone; it's the embodiment of deeply conflicting user interfaces and objectives. You've got to balance things like phone usage, battery life, screensize along with interfaces for a range of applications like email, text messages, web browsing and calendars. Not an easy task.
I think in the end it all boils down to a couple of things. If you want a good product, have a small team that cares deeply about the experience. It's worth sweating the details.
Maybe that's the reason Microsoft bought Danger...
Posted by Zack Urlocker on February 13, 2008 09:31 AM
RATE THIS ARTICLE:
-

- COMMENTS
I agree with this!
I've stuck with Ericsson/Sony Ericsson phones since 1998 simply because I can't bear the thought of learning a different interface -- Nokia, Motorola, whatever.
Posted by: Stephen at February 13, 2008 08:15 PMI just got a Blackberry 8310 and I am completely addicted. I think they did a great job and after installing Opera Mini, Facebook and iSkoot (Skype) and putting in an extra 2gb it's close to being perfect.
Posted by: Andi Gutmans at February 13, 2008 09:52 PMYou should try N95.
It's one of those "phones that have all the right features".
I insist: Zack, try it! It's amazing phone, with camera, wifi, applications, and other stuff.
The best thing of a Nokia phone is the operation system: Symbian.
If you don't know Symbian, this is a good time to learn about it.
Don't buy iPhone. It may be pretty and easy to use, but certainly it isn't the right choice.
Maybe an iPhone2 will be good enough.
However, right now, I think N95 has the best hardware and the best software.
Obviously, there are drawbacks: its battery, and its keypad.
Don't be silly. Microsoft buys companies that are doing it right so that they can force them to port stuff to Windows. Either it works or it doesn't, but either way the Sloth gets to suck without competent competition.
Posted by: David Stewart Zink at February 14, 2008 08:37 AMWhy buy a smartphone? I've got a Samsung Z720 that supports Java apps like Google maps and Google mail. Google calendar sends me text msgs for appointments. It's got an MP3 player and a microSD slot. I can tether it to my notebook (or the N800 I'm playing with) and run HSDPA at 1.8mb. It weighs 80g and is about 10x5x1.3 cm.
Posted by: Dave Beck at February 14, 2008 08:46 AMEarth to James: iPhone? Are you kidding me? Weak calendar app and NO TASK APP?!?! Ugh! Useless then, no matter how nice otherwise. I have a Treo 650, too. Maybe time to switch to a new Blackberry... I dunno...
Posted by: David Lamb at February 19, 2008 10:44 AMMost cell phones are sold by what are essentially public utility companies. The core product of these companies is really network access, not the cell phone. Product design is driven by the utility companies, not the cell phone manufacturers. Several years ago, Motorola made a breakthrough phone (the V710), which had Bluetooth, a reasonable file system, a decent interface, etc, etc, but the first thing that Verizon did was disable Bluetooth for anything except handsfree kits (no Bluetooth syncing; you needed to buy Verizon's $50 USB kit), disable MP3/ringtone support (so that the only ringtones available were the ones that Verizon would sell to you for a few dollars each), and on and on. The wireless companies have much more in common with the gas, electric, and water companies than they do with consumer-oriented companies.
Posted by: biff at February 19, 2008 11:26 AMI just did the same thing, new phone for me, new phone for the wife. I need my device to be a phone 'first' and after reviewing the many smart devices I went with Treo 700 because it simply had the best touch screen. Most units I tested have a delay that quickly becomes frustration when trying to dial a number and makes then not such good phones. The 700 uses Windows Mobile which might be a compromise for Palm but the unit is functional and has a decent battery life and seems to be a bit more business then toy which may be a good set of details to look at.
Posted by: Michael at February 19, 2008 06:43 PMThat's why I got a Treo 680. Strong integrated contact/task/schedule apps are available that sit on top of the native ones, good size and weight, excellent signal strength and voice quality as a phone.
I too wish that Palm would be more on the ball with updates, and sorely wish that they had WiFi, but I haven't found any other device that will do what I need on a daily basis as easily and as well as my Treo does now.
Posted by: Simcha at February 19, 2008 07:45 PM
- Get Started
- Port 25 Blogs
- OSS News
- Join a Project
{Open Source} Heroes Happen Here
Start today and order your own Hero Hack Pack – which includes Getting Started with Open Source, Windows Server 2008 and Visual Studio 2008 Trial. Each pack is a chance to win a free pass to OSCON 2008.
TOP STORIES
ADDITIONAL RESOURCES

- Remote Access: Maintain Security and Decrease the Burden on IT
- Beyond AntiVirus: Symantec Endpoint Protection
- What Every Enterprise Needs to Know About VDI

- Disaster Recovery in Minutes
- Protecting Microsoft(R) Applications
- Reduce Recovery Times and Tape Costs








