How Not to Build a Cellphone
Jamie found an NYT story about a new t-mobile Shadow phone which starts off by talking about how Apple is changing the phone game by wrestling power from the carriers, and then discussing what could be a reasonable piece of hardware. And then how it is wrecked by software. The phone has wait screens, a task manager, odd error messages etc. Makes for an amusing read.
Everything you need to know starts in paragraph eighteen:
And, this isn't even Microsoft's fault! It's T-Mobile's CEO who had the hubris to think he could design this thing just like Jobs. Not.
I think the article actually goes a little easy on the critique of the hardware. I doesn't break any ground. It has too many or too few buttons. The middle ground they took with the Blackberry licensed keyboard was just plain wrong. This phone is just a mess. Apple kinda pulled this feat off, designing a do-everything phone (I kinda disagree, btw), and now everybody else thinks they can do it too. They even think it's the right thing to do (it's not).
But, what were they thinking going with MS Mobile? Wth? Sheeesh... it even comes with a Task Monitor? Yeah, I'm gonna help my Dad with his new phone... "Bring up the Task Monitor... now click on the Processes tab. Now click on the CPU column twice. What's eating up the most CPU? ... That's the central processing unit....
ummm... Okay, now highlight the one eating up all the CPU and click the "End
Process" button.... " Not.
Another place the article "gets it wrong" trying to be kind in his critique:
Wrong! That's not an advantage, that's insane. At least, I can't remember the last time I was looking at my cellphone thinking, "Damn, I wish right now I could open up a Word document!", not even if one was attached to an e-mail.
I'm still waiting for the phone that sounds and works like a phone.
Bit of trivia, speaking of phones... Know what the little graphic on the Sprint logo stands for? Didn't think so. It represents a stop-motion pin dropping. Remember when Sprint's commercials were about phone call sound quality and how it was so good you could hear a pin drop? Didn't think so. Please, oh, please, let me hear the pin drop again!
Joel Spolsky does an entertaining job of ripping another phone with poorly-designed software to pieces here.
...talking about how Apple is changing the phone game by wrestling power from the carriers... Right. Apple has certainly wrestled control away from the carriers. Now, instead of just paying the carrier blood money and selling our soul for two years, we get to pay both Apple AND the carrier... and still sell our soul away for two years. Maybe Nokia can compete with Apple by coming out with a phone where I need to sign a 5 year soul sucking deal with the hell (like AT&T, but more pleasant), have the phone chomp on my balls while it is in my pocket, eat my first born child, and get a direct hookup to my bank account from where it funnels money into everyone's pocket but my own.Come on Google, buy the damn spectrum, open it up, and lets say fuck you to the ass pounding consumers are getting in the US cellular market.
It's not designed by T-mobile of cause (if it was sarcasm on the part of TFA, it was too veilded IMO) It was designed by HTC. It is in fact HTC Juno. As the HTC is a part of Google led Open Handset Alliance may be their next phones would fare better.
Windows Mobile 6 == teh sux
This message brought to you by: Article in a Nutshell (TM)
eleven plus two / twelve plus one
In all fairness, his comments assume that all Windows Mobile 6 editions are created equally which isn't the case. On this phone, we're looking at Windows Mobile Classic, which is a phone only implementation (without touch screen/stylus interface). While I for one don't have the patience (and nor does the author of the article) to click through menu after menu on a cell phone, I have moved to an interface that I find pleasing to use -- Windows Mobile 6 Professional. Being able to directly interact with the screen on the phone is the same as adding a mouse to your desktop PC. Imagine if the author was given a copy of Windows XP and only a keyboard to navigate... can you imagine the complaints? So as sexy as he perceives the hardware to be, clearly it needs additional functionality to be the powerhouse that he's looking for.
Looking forward to him eating his words when he reviews the HP iPaq 910 with Windows Mobile 6 Professional.
I've never found one that's well-designed. They may exist, but I've never had or seen one.
What I want:
1) The ability to turn the volume up or down in a wider scale than they give us. If I can't hear someone with the volume at max (usually when they're on a landline), the scale needs to go higher. My phone goes up to five; it should go up to eleven. It's a device whose principal function is the capture and transmission of sound, yet it has ONE thing you can control about the sound: inbound sound volume, in a limited range. This is ridiculous. This is stuff that could be included essentially for free, since it's all software that doesn't take much processing power. For instance, it'd be nice to have some sort of intelligent parametric EQ. Sometimes you get someone on the other end with a sucky headset and it'd be nice to be able to fix it yourself or have the phone do it for you.
2) The phone to tell me what the hell it's doing signal-wise. I've been standing on top of a mountain and looking over a canyon at a cell tower (~2 miles distant) and have no signal. Sometimes calls get dropped even though I have four "bars" of signal. Is it a SNR problem? The phone trying to do a tower swap and failing? Who the fuck knows? Give me frickin' iwconfig, please. It's like the Windows boot sequence. Either it works or it doesn't, and if it doesn't, who knows what went wrong. But Windows at least has Safe Mode...
3) A phone that doesn't fucking break. My old phone had a keypad that kept going bad. My new phone now thinks that there's a headset plugged into it when there's not. Sometimes it thinks I don't have a SIM card in it.
4) I hesitate to suggest this since they seem incapable of getting even simple things right, but replace SIM cards with SD cards (they're effectively a commodity now, $20 for 2GB). Poof, instant long-play pocket audio recorder!
You don't need mobile OS design experience to figure out that a phone has a terrible user interface. While I agree that his comment on a two-button unlock sequence is uncalled for (why have a lock function that unlocks with a single, accidental keypress?), but other than that I think all his gripes are perfectly justified because they deal with the end-user experience.
An old-timer with old-timey ideas.
I'm still waiting for the phone that sounds and works like a phone.
Why does everyone say this as if it doesn't exist?
I suspect it is because they want their posts to sound as though they possess some real down-home 'Murrican wisdom. Jesus. How many counterexamples do I have to find? All of these are "phones that look and act like phones."
Moreover, why is ANYONE "against" convergence? Seriously? Do you really WANT to be carrying around a camera, a phone, a PDA, and a laptop?
Wrong! That's not an advantage, that's insane. At least, I can't remember the last time I was looking at my cellphone thinking, "Damn, I wish right now I could open up a Word document!", not even if one was attached to an e-mail.
Yesterday, when I got an email from my advisor. Thankfully, I had my iPhone at the ready and it was quite capable of opening the document. I was able to answer her question immediately and it made me look like I was really on top of things. I guess that makes me "insane."
+++ATH0
What "necessity" is there to require two button presses? This sounds like pre-iPhone thinking. Not that I'm a huge fan of the iPhone, but one thing it has done is forced people to rethink both what's practical and what's "necessary" in a phone.
I had a Siemens candy-bar style phone about 5 years ago that only required one button press to unlock. I mention that it was a candy bar because that means its buttons were unprotected, and I walked around with it in my pocket. Never once did I unlock it by mistake. All it takes is a combination of the right resistance on the buttons and requiring a certain length of a button press (1-2 seconds) in order to successfully unlock it.
People have a tendency to get tunnel vision, and to get locked in to a certain way of thinking (no pun intended) just because "that's the way it's done". This is probably why, after 5 earlier iterations, Windows Mobile still requires going into a menu to hit "delete" on a text message. The one thing I will give Steve Jobs credit for is looking at things like this and saying "why does it have to be done this way?" If there's no good answer, he throws everything out and starts over.
That kind of questioning needs to be done at every level of every single product design. You can't just continuously carry things over from iteration to iteration without any justification as to why.
I fail to see how "wresting power from the carriers" is a bad thing. They do evil things with it. Two year contracts with "early termination fees". Phones locked into their service. Phones with software or hardware they've deliberately crippled (Verizon I'm looking at you). Phones that have had a nice GUI replaced with their branded crap. Charging absurd prices for downloads. Padding HTTP headers with data so you use more of their outrageously overpriced data plans. I could go on and on. But if you ask me, the more power the phones wrest from the carriers, the better off we'll be.
Question everything
Whats up with that ancient brick like thing with an antenna sticking out being used as an icon for cellphones in slashdot. Jeez can't they get a more recent pic? If not iPhone at least something from the stone age like razr or a clamshell? They are still using that fossil from Jurassic!
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Frankly, Windows Mobile 6 is a mess. Common features require an infinitude of taps and clicks, and the ones you need most are buried in menus. Apparently the Windows Mobile 6 team learned absolutely nothing from Windows Mobile 1, 2, 3, 4 and 5.
I wholeheartedly agree: I received a low-end HP PDA years ago for Christmas. Windows Mobile worked so poorly that I didn't even bother to get the thing replaced on warranty when it broke within two months (battery couldn't hold a charge to save its life).
I already miss the 'antiquated' Palm OS that ran on my Treo. The article was nice enough to bring up a couple of my favorite reasons as to why...
First of all, a cellphone should not display a "wait" cursor. Ever. And definitely not almost every time you change screens, as on the Shadow.
One of my favorites: I run a nearly stock version of WM6 on my HTC Mogul phone, with the only additions being the free version of Epocrates and an SPB Diary application. My phone has a more-than-adequate CPU, yet still lags while switching screens.
Do I need to "wipe and load" my phone to make it run faster? Sheesh.
A cellphone should not have a Task Manager. You should never have to worry about quitting programs because you've used up too much memory.
Amen! I also love how the phone has a knack for running out of memory right when an important call comes in. There's nothing more frustrating than a ringing phone that won't show me the phone screen and where the buttons suddenly don't work.
I have an iPhone, I also have a windows mobile 6 smartphone. I use one as a wifi ipod and the other as my communications tool. Why? Cause the iphone doesn't sync up with my corporate exchange server and push email to me from it. It's just a tool and as much as I love my iphone I have to use the other to get the functionality of the tool I need. For what its worth I think WM6 is pretty decent and I can work without a laptop and have access to my corporate address list, email, contacts, office documents anywhere I've got reception. not bad.
;)
Where the t-mob shadow really sucks is the half azz keyboard.
-Xen
Err... the early Philips (C12/Savvy) phones ALL had this - they were the first real phone that BT (back then Cellnet -> BTCellnet-> O2) released when mobiles started taking off. Trying to dial 999 or 112 was given as the reason - pressing 1 or 9 would undo the key-lock.
And yes, it was incredibly dumb. And more than once I nearly dialled random 4-5 digit numbers because it had activated in my pocket. It wasn't the only model to suffer from it, though. And I shouldn't think many modern phones emulate this "feature".
Matthew Miller from ZDNet's The Mobile Gadgeteer: http://blogs.zdnet.com/mobile-gadgeteer/?p=679
This is basically a blow-by-blow refutation of Pogue's article. Enjoy.
Yes, I had a siemens candy-bar phone with a one-press unlock. In the eight months it lasted before its power circuit broke, I recall numerous instances of arriving at work (after walking for 30 minutes) to find the boss expecting me, as he'd already been talking to my pants.
Steve Jobs didn't do diddly here. The basic design principle is: If you have a mechanical sliding lock, cool. Otherwise, you have to use buttons, and if you use buttons, use more than one. Because a "phone lock" that regularly unlocks in a situation where uncommanded forces are applied to the keyboard is no lock, but a nuisance.
Two button presses have a very good reason for existing. A single button is not sufficient when you're trying to protect against accidental presses. Even if you don't have a problem with it personally it is a problem. Making the buttons difficult to press is a terrible solution too, since it means wearing your fingers out to solve the accidental press problem.
Personally, I find the two button press option to be a pretty good solution in the case where your only controls are buttons. The op mentions how Apple came up with a new method to solve it, but apparently fails to realize that Apple was forced to come up with something like that on account of having only a single button on the phone. Frankly, the button press and finger motion on the iPhone seems like more effort than the two button press the op is complaining about. The article's author is dead wrong about two button presses being too many however, but I agree with him on pretty much all of his other points.
I read the internet for the articles.
"A cellphone should auto-format phone numbers with parentheses and hyphens when you enter them in the address book. When the cursor is in a number box, like ZIP code, the keyboard should automatically start typing numbers. The owner should not have to press the alternate-symbols key."
I, for one, don't want hyphens or parentheses in my phone numbers, and my zip code starts with a G, so I wouldn't want my keyboard to type numbers in my zip code field.
"A locking feature, which prevents the buttons from being pushed accidentally in a purse or pocket, is nice. But it should be optional. And one button press should suffice to unlock it; two in sequence is just annoying."
Sort of defeats the purpose of locking the keyboard if it can be unlocked with an accidental keypress.
"...looking stunning in your hand..."
Uhh, what? Are phones in the US really that ugly that this plain-at-best handset is judged stunning?
C-x C-s C-x k
When I read this in the article:
It made me seriously question whether the photo shown along side was actually the phone they were talking about. That thing is seriously the ugliest phone I've seen in a long time and reminds me of something from the late '90s. Seriously, how could anyone possibly look at that phone and think it's even remotely inspired by the iPhone/iPod?!
"A buttonless facade"??? What the? There are 7 buttons plus the wheel on the front, plus another 20 with the keyboard pulled out. Maybe I just don't understand what "buttonless" means these days".
By reading this signature, you hereby agree with the content of the above comment.
My original cell phone, a Panasonic TX-220, had a single-keypress lock function. However, it required holding down the lock key for 2 seconds to enable or disable (with an auto-enable after 10 seconds feature). Never had it accidentally lock or unlock on me, and I found it to be a lot more usable than the "top-left button, then bottom-left button" process to un/lock my current phone.
:) It's been done before, it's been done well, and lots of us really miss it.
Don't dismiss a single-key lock process because you can't think of a way to make it work.
While N800 (or its recent successor, N810) isn't really called a PDA, I've found it a nice generic tool for browsing, reading emails, making some notes, listening music and other moderately lightweight tasks. While there isn't a default calendar application, I think some are available separately (I have very few meetings etc. myself, so I don't really need a calendar personally). With WLAN and Bluetooth connectivity, I can access net pretty much anywhere and the 800x480 screen is pretty good for most uses.
On the downside it could use a bit longer active use-time (~4h of continuous usage in worst case), but I suppose that's the price of a large high-quality color screen.
Everyone who makes generalizations should be shot.
I think this person needs to understand what the difference is between WM6 and a company that has jacked it up. WM6 is not perfect, but the issues he's blasted here are either because of TMobile's implementation, or his lack of knowledge of the features of the OS.
-David
This phone has a flashlight, a single bright white LED in the top of the casing.
It's the epitomy of minimalism, but it's the only phone I've seen with this sensible feature. Not a xenon tube that needs a battery guzzling capacitor to charge for each shot, either.
how could anyone possibly look at that phone and think it's even remotely inspired by the iPhone/iPod?!
Agreed, Nokia's phones are usually based on the Nokia "look" more than anything else. But there is a whole new wave of big-screen phones emerging based on trends coming out of Korea. The first one of these was a few mutant Samsungs, which begat the LG Prada, which Apple then lifted for its own phone design. Compare and contrast.
Da Blog
Geesh... All I want is a freaking phone that allows me to play music and videos (podcasts), install 3rd party apps, has 3G connectivity & wifi, has gmail and push-email support, syncs with an ical feed, has an IM client that works with all the major networks, allows me to teather my laptop via bluetooth to the phone, has A2DP, and a web browser that renders like a web browser should (WITH FLASH FOR CHRIST'S SAKE.) Make your own MP3/AAC ringtones. Oh, and it needs to be on more than one carrier.
And it needs to be, most importantly, a GOOD PHONE. With GOOD RECEPTION, SOUND QUALITY, AND DIALING SHOULD BE SUPER-SIMPLE!!
Photo and video opportunities so that you could upload to Youtube/Flickr/Facebook would be cool too, but I'm OK without having that.
How fucking hard is it to roll that out???? Seriously, how fucking hard?
-nick
Like a moth to the flame, I am attracted to your flamboyant sparks.
Yes, the iPhone's design does relate a lot to being from Apple.
But no, Apple didn't "lock the phone," it opened up a standards-based web API that is in many respects better than anything on existing smartphones. The iPhone is also only 4 months old, and Apple has promised additional access in an SDK later this winter. Saying Apple locked the phone for development is ignorant. Saying Apple locked the phone to a single provider ignores the reality that all US phones are locked to one of two network technologies that inherently limits which provider you can chose.
Home activation through iTunes is a lot more consumer friendly than forcing the user to go to a phone store and wait for some dude to poke around on it for an hour, or deal with an online bait and switch as I suffered when I bought a Palm Treo from Amazon using Sprint, and ended up getting cheated out of promised rebates from Amazon while Sprint unilaterally changed my contract and then insisted the contract I'd originally bought wasn't something they offered any more.
No OTA updates for what, your calendar? Email updates OTA, and you can listen to audio and watch real video OTA, without paying and ARM AND LEG for Windows Media based rip-off video from Verizon/Sprint/AT&T garbage services.
Apple didn't brick phones; it warned users that if they modified their baseband or device firmware, that installing additional updates might be a problem. That is ALWAYS the case any time you hack at firmware.
What is a "real keyboard," a chicklet panel that slides out, making the phone an inch and a half thick, or a micro keypad that requires typing with your thumbnail? I've used a variety of "real" keyboards on mobiles, and have to say I'm typing much faster on the iPhone. I'd like arrow keys and a way to copy and paste text around, but the keyboard is fast, simple and very usable, and also gives me a very large screen I can use to play online games, watch movies, or browse the web. Those are all things a tiny screen paired with tiny keys can't do well.
What You Expected, What You Got: RoughlyDrafted Fact Checking
Ten Myths of Mac OS X Leopard: 10 Leopard is a Vista Knockoff!
Whenever I see a device that tries to be "Everything" I am taken back to the 60's to McNamara and his desire to have an airplane that had "commonality" and could serve as the "end all".
The F111 was designed to be both a fighter and a bomber. It was too heavy to land on carriers and could not carry the required equipment and payloads required by the Navy... did not even have gatlin guns on it for a while, and it was too small to carry a large payload and the range was too short to be an effective bomber.
So is the T-mobile a F111 or can these problems be worked out?
This is a time for the designer to eat his/her pride and make it work... if that is possible. It wasn't possible with the F111 and the T-mobile remains to be seen.
And in the end, the love you take is equal to the love you make
I have to agree. I've been using Windows Mobile on the PocketPC for several phones now, it may not be perfect, but it's very nice. The TyTN II ofcourse at this time being the creme de la creme in WM phones (if the battery life was longer, there was a decent DDRaw driver and it had a VGA screen, I'd say the phone itself was perfect) I've seen the iPhone, I've played with it, and honestly, I don't see what the fuss is about. It's not a phone for serious business, it's a toy. A WM device gives you office productivity when you're mobile. As one of the founders of a tech start-up I can honestly say I could not do without it. Syncing all my outlook things with the phone, accessibility to my mail everywhere, tethering, GPS, GPRS/EDGE/UMTS/HSDPA, full QWERTY keyboard, if needed open office documents on the go, and when I want it is almost trivial to develop my own applications for it. I almost feel sorry to say this, but the only thing that comes even close to WM is Symbian. Symbian is a bit faster and energy efficient, but it just doesn't offer the same level of applications and compatibility. To :parent:, I've not had a lock-up on my Kaiser in a long time. Don't run Batti, tweak with KaiserTweak (shameless plug) and if you're feeling adventurous, go to xda-developers.com , get the HTC rom and throw away all your AT&T muck.
(Chainfire @ XDA-Dev)
Because phones are tied to specific vendors/networks. These same vendors often restrict the software and hardware capabilities of their phones to encourage you to buy more services from them.