Re:Why Nokia failed: 'Wasted 2,000 man years' on UIs that di...
by frent on Thursday March 10, 2011 @04:11PM
(#2310798)
With that said Nokia's brick phones have some of the easiest interfaces to use of any device ever
As someone who uses a recent Series 40 phone, I have to disagree with you. I think their last decent brick was the 6230i.
I got an XpressMusic (don't know the exact model number) Series 40 phone in 2009 , and, although it does the basics well, it has some serious design flaws.
It is a music phone, but it lacks a "stop" button to go with the play/pause button on its side. Therefore it is always on pause, so that, if it is in my pocket, and the "play" button is hit accidentally, a preloaded song called "The Dance of Shiva" starts playing. Very embarrassing.
And if you want to send an SMS, you need to save the number first as a contact, since the SMS UI doesn't allow for numbers in the "number" field.
These are shockingly obvious design flaws that Nokia missed. Something went wrong with Nokia a few years ago, and it wasn't limited to their smartphones.
As someone who uses a recent Series 40 phone, I have to disagree with you. I think their last decent brick was the 6230i.
I got an XpressMusic (don't know the exact model number) Series 40 phone in 2009 , and, although it does the basics well, it has some serious design flaws.
It is a music phone, but it lacks a "stop" button to go with the play/pause button on its side. Therefore it is always on pause, so that, if it is in my pocket, and the "play" button is hit accidentally, a preloaded song called "The Dance of Shiva" starts playing. Very embarrassing.
And if you want to send an SMS, you need to save the number first as a contact, since the SMS UI doesn't allow for numbers in the "number" field.
These are shockingly obvious design flaws that Nokia missed. Something went wrong with Nokia a few years ago, and it wasn't limited to their smartphones.