Dear Reader
just a little tip for those who are annoyed by the “hide all windows” feature automatically activated when you [accidentally] move your mouse into the lower right corner.
It is easy to disable this, just by right-clicking the small empty bar in your lower right corner
and un-ticking the “Peek at Desktop” option:
Left-clicking the bar will still show Desktop.
At least it’s not activated accidentally.
Infrequent postings about: User Experience design, User Interface analysis, Mobile Computing industry, Computer Software Usability, Computing Hardware architecture.
Showing posts with label user experience. Show all posts
Showing posts with label user experience. Show all posts
Tuesday, June 24, 2014
Tuesday, August 6, 2013
Lost in phone, or another opportunity for iOS 7
Let me confess, I have been using Apple iPhone since 2008.
Back in 2010, my phone was stolen. A month later, we were moving to Australia and I did not buy a new one.
I have been using a Nokia phone for a year, it was a Symbian one.
Interestingly, I did not miss the iPhone. I was on the lookout for something new, something better.
It happened to be an hp pre3 powered by [ex Palm's] webOS operating system. But that's another story.
I tried to understand why I did not miss the iPhone, after all, I was a Mac user since 2001.
And I think I can explain why, at least to myself.
There are things in iPhone experience that simply make you bored.
The same old grid of same old icons, mostly static. Onerous App Switching functionality.
But now I also see things that actually enrage me, even if they used to do it subconsciously.
Let us talk about one.
Phones are many things to us now, but for me, they still must serve well as PHONES.
It seems that iPhone fell short on this, even compared to my first smartphone that I bought in 2004, the absolute flagman of the years and everything before the iPhone - Sony Ericsson P910i.
Consider unlocking your iPhone, you will see Phone and Contacts icons.
Inside the Phone icon, you will see Contacts tab.
Along the Phone app tabs, you will see "Favorites", "Recents", "Contacts".
As well as "Contacts" outside of the phone app, on the dock.
"Recents" tab is split in "All" and "Missed" categories.
Can you still follow me? :)
Guess what? THERE IS NO PEOPLE PHOTOS, NO USERPICS not in any of these multiple tabs. Huh?
All four tabs I have listed, have no people faces on them. Not even in Favorites!
To see a picture, you need to drill down to a particular contact! This is in 2013.
Many times we are trying to catch up with people on the go, while walking, some [unwise folks] even when driving.
No pictures does not help at all!
What is even worse, is getting stuck in "Recents"-"Missed" and trying to dial a number who you just talked to and said "I'll call you in a minute".
This is because Phone app remembers where you were last time, making navigation to where you want to be this time a process that takes more brain cells to coordinate their work, distracting from other things you're trying to do (unless you're sitting on a sofa playing the phone).
I took out my old SonyEricsson and checked the Phone application.
Always takes you to Favorites that have faces on them. Two-touch calls to Favorites are possible from wherever I am.
On the iPhone, if your favorite people are calling you then your Recents will look much like Favorites, but sometimes sans the guy you want to talk to now. Same-looking text in both tabs, no pictures. Frustration. No wonder they need Siri to help.
Finding yourself switching to less-often used tabs like Dialpad is OK.
Having to switch out of that rarely used functionality is not.
Another source of confusion is the double Contacts functionality.
Since there are two of the Contacts tab, and each remembers its own position, you will have to re-find (find again) the user that you have focused on, should you go to the "wrong" Contacts tab.
It took me some time to realize that in order to send an email, I have to touch the actual email address instead of reading all the button labels below in vain search for "Email" button, then trying to figure out whether "Send Message" button meant "email message".
There's simply not enough visual cues. Have a look at how it was done in the SonyEricsson.
One more thing about my ancient but greatly usable phone.
It seems to be the only 3rd party phone that Apple has written software for.
No kidding, Apple programmed for Symbian UIQ 2.1. Steve must have cared enough.
Here's a proof.
The iSync agent worked hand-in-hand with iSync Apple app for MacOS, making sure that bluetooth synchronization of Calendar, Contacts and such was impeccable. And it was, unlike my Nokia PC Suite experience.
Overall, with a couple of tweaks I hope that Apple will resolve these issues in upcoming iOS 7 - they just need more of that "attention to detail".
But maybe not - it does not seem to be about phone calls anymore...at least, this is not Apple's business.
Or is it?
Back in 2010, my phone was stolen. A month later, we were moving to Australia and I did not buy a new one.
I have been using a Nokia phone for a year, it was a Symbian one.
Interestingly, I did not miss the iPhone. I was on the lookout for something new, something better.
It happened to be an hp pre3 powered by [ex Palm's] webOS operating system. But that's another story.
I tried to understand why I did not miss the iPhone, after all, I was a Mac user since 2001.
And I think I can explain why, at least to myself.
There are things in iPhone experience that simply make you bored.
The same old grid of same old icons, mostly static. Onerous App Switching functionality.
But now I also see things that actually enrage me, even if they used to do it subconsciously.
Let us talk about one.
Phones are many things to us now, but for me, they still must serve well as PHONES.
It seems that iPhone fell short on this, even compared to my first smartphone that I bought in 2004, the absolute flagman of the years and everything before the iPhone - Sony Ericsson P910i.
Consider unlocking your iPhone, you will see Phone and Contacts icons.
Inside the Phone icon, you will see Contacts tab.
Along the Phone app tabs, you will see "Favorites", "Recents", "Contacts".
As well as "Contacts" outside of the phone app, on the dock.
"Recents" tab is split in "All" and "Missed" categories.
Can you still follow me? :)
Guess what? THERE IS NO PEOPLE PHOTOS, NO USERPICS not in any of these multiple tabs. Huh?
All four tabs I have listed, have no people faces on them. Not even in Favorites!
To see a picture, you need to drill down to a particular contact! This is in 2013.
Many times we are trying to catch up with people on the go, while walking, some [unwise folks] even when driving.
No pictures does not help at all!
What is even worse, is getting stuck in "Recents"-"Missed" and trying to dial a number who you just talked to and said "I'll call you in a minute".
This is because Phone app remembers where you were last time, making navigation to where you want to be this time a process that takes more brain cells to coordinate their work, distracting from other things you're trying to do (unless you're sitting on a sofa playing the phone).
I took out my old SonyEricsson and checked the Phone application.
Always takes you to Favorites that have faces on them. Two-touch calls to Favorites are possible from wherever I am.
On the iPhone, if your favorite people are calling you then your Recents will look much like Favorites, but sometimes sans the guy you want to talk to now. Same-looking text in both tabs, no pictures. Frustration. No wonder they need Siri to help.
Finding yourself switching to less-often used tabs like Dialpad is OK.
Having to switch out of that rarely used functionality is not.
Another source of confusion is the double Contacts functionality.
Since there are two of the Contacts tab, and each remembers its own position, you will have to re-find (find again) the user that you have focused on, should you go to the "wrong" Contacts tab.
It took me some time to realize that in order to send an email, I have to touch the actual email address instead of reading all the button labels below in vain search for "Email" button, then trying to figure out whether "Send Message" button meant "email message".
There's simply not enough visual cues. Have a look at how it was done in the SonyEricsson.
One more thing about my ancient but greatly usable phone.
It seems to be the only 3rd party phone that Apple has written software for.
No kidding, Apple programmed for Symbian UIQ 2.1. Steve must have cared enough.
Here's a proof.
The iSync agent worked hand-in-hand with iSync Apple app for MacOS, making sure that bluetooth synchronization of Calendar, Contacts and such was impeccable. And it was, unlike my Nokia PC Suite experience.
Overall, with a couple of tweaks I hope that Apple will resolve these issues in upcoming iOS 7 - they just need more of that "attention to detail".
But maybe not - it does not seem to be about phone calls anymore...at least, this is not Apple's business.
Or is it?
Labels:
Apple,
iOS7,
iPhone,
SonyEricsson,
UIQ,
usability,
user experience,
user interface
Tuesday, April 13, 2010
Opera strikes a false note
I was an active Opera browser user for about 10 years.But the time has come for me to stop that practice, and here's why.
To start with, I really like Opera. Or, liked - I should say.
It has pioneered way too many useful features to ignore -
built-in e-mail client with tagging and quick reply (M2)
built-in bookmark sync (Opera Link)
built-in BitTorrent client (although quite limited and slow)
Opera DialPad - replacement for your TV channels
page mini-thumb previews
tabs (yes, way way back before Firefox)
side panes for everything
notes
widgets
Magic Wand - you unobtrusive password helper, even for those site which do not allow to save it
and, lastly, Opera Unite and Opera Turbo (which I don't use)
Opera is a real all-in-one convenience, especially for multiple installations and platforms. It seriously helps achieve unified user experience across separate devices.
I had used it on two PCs, one Mac and two cell phones (S40 and UIQ2.1)
Bookmark sync was a bliss!
But, recent 10.x branch of desktop browser has been less than encouraging.
First off, there's been UI rehash in 10.0 to which one would have to accustom for quite a while. Then, there were some issues with my proxy detection PAC script - while easily processed by IE, it was not always taken well by Opera.
These issues were finally resolved, only to reappear in the latest 10.51.
But Oh, this 10.51 release is something.
The hideous thing is that it installed itself on top of my two 10.10 PC installations! No questions asked, no indication of a process given.
Sneakily and silently it installed itself, so when I reopened a closed Opera browser, the Windows Installer proceeded to set up my user environment and - voila - I had a new shiny un-asked-for release installed.
And guess what - I don't like it.
On one of my PCs, with User Switching enabled, it takes so much time to load. It also makes a simple wake-up operation take up almost 10 minutes with blank screen.
It clearly behaves in a CPU hog manner.
On another PC, it loses connectivity way too often, and I suspect "new and improved" PAC script logic. For instance, taking notebook off the docking station, I am losing Ethernet connection, then I dock it back - and have to restart Opera, because it obviously loses proxy connection, and goes direct.
I hate the new Microsoft-like "O" menu button in the top left.
This is the new Start button for you the netbook generation! :)
Takes one or two clicks more to do same stuff.
Mac version takes too long to start. Although I like the way it scrolls pages.
Smoooth!
So I have taken a look at three more browsers for PC - Apple Safari, Google Chrome, and Mozilla Firefox. And here's what I say.
Apple's Safari was my next turn, obviously, for having it on my Mac.
Once again, I was looking for a unified user experience, a browser I can rely on for both Mac and PC. (I am not using those cell phones anymore)
Safari pros:
- works great on a Mac
- works fast on a PC, too
Safari contras:
- has ugly unnatural looks on PC, trying to achieve mac's look with pc's means
- takes too much space in vertical dimension (three lines for my setup, IE8 takes two)
- bookmark sync is a paid option (mobileme.com costs $100/y)
FAIL (as compared to Opera I'm replacing, and the winner)
Google Chrome is very fashionable now, I see it more and more often, especially at web expos, where most of devs are Google-junkies/wannabes. So I took a spin on it and was not impressed...yet? "Yet" is too, the word which comes to mind when I think of Android. But I digress.
Chrome pros:
- fast
- Google-integrated, HTML5 support
Chrome contras:
- system colors are not respected nor used! I am on XP (Silver theme), do not show me bloody blue Vista-like buttons! WTF? Respect my environment, look and color prefs - do not supplant them!
- WTF with fullscreen (F11) mode? I raise the mouse to top bar - and see no menu, no address line only some useless nag?
FAIL ("yet"?)
By the way, "Chrome" is "lame" in Russian.
Not that I hate it, it's just "not there yet".
And the winner is: Mozilla Firefox
Why?
Firefox pros:
- nice look, respects colors and style
- fast
- has free bookmark sync plug-ins
- does not cause "hanging" when waking up
- does not hog CPU on user-switched setups
- most sites are tested on it (although Opera was also OK in that regard for me)
Firefox contras:
- not the same look on mac - but I guess I don't want it to look like Safari on a PC
- there were problems updating it on a mac, "locked" dynlib files in Trash, even after restart
- popular - could be exploited successfully - will need often updates
Well, I guess it still much better on PC than the rest.
It's not the fist time Opera screwes up. But it's time to change.
Thanks for 9.x-10.10 though, it's been a great ride.
Labels:
Apple Safari,
browsers,
Google Chrome,
Opera,
user experience,
user interface
Saturday, January 30, 2010
AOL fixes Sent Items
There's hope to AOL.
They have finally fixed the long-standing, pesky issue with sent e-mails, which they "managed" even for IMAP accounts, by placing them into "Sent" folder.
While that was quite OK for web clients, this functionality posed a problem for signed/encrypted mail, as well as duplication of saved sent e-mails.
I wrote to AOL earlier last year and later in October and 3 months later (today) they do the fix. Hurray!
And the response team strikes back:

I can only add that of all times I tried to ask Yahoo! Mail team for similar fixes (mostly related to handling of international char encodings), none succeeded.
I got usual third-world support banter instead, and promptly decided to close my Y! account, few years ago.
They have finally fixed the long-standing, pesky issue with sent e-mails, which they "managed" even for IMAP accounts, by placing them into "Sent" folder.
While that was quite OK for web clients, this functionality posed a problem for signed/encrypted mail, as well as duplication of saved sent e-mails.
I wrote to AOL earlier last year and later in October and 3 months later (today) they do the fix. Hurray!
Hello,
there are some issues in your e-mail service.
More specifically, digitally-signed e-mails become "tampered with" in status, as they are automatically moved BY YOUR SYSTEM (not my e-mail client) into Sent Folder.
I am including one of many such e-mails in attachments.
It is also of note that I previously contacted you about this "auto copy" functionality - this feature is completely unneded on IMAP interface, as most IMAP e-mail client programs are able to perform this on their own.
It is exactly this feature that causes also troubles with signed and encrypted e-mails as I described in first paragraph.
In case you need more info/descriptions, please connect me to developers/admins.
I am a system engineering architect myself, in telecom.
Thank you.
And the response team strikes back:

Dear cubeover,
If you access your email using third party software, such as Outlook or Thunderbird, please read this important message.
We want to inform you of a change to our email infrastructure that will result in copies of sent emails no longer being automatically placed in your Sent folder when sent via third party email software, as of Tuesday, February 2, 2010.
In order for you to continue having your sent emails automatically placed in your Sent folder on February 2, 2010 or later, you will need to make a change in your email software settings no later than February 1, 2010. Please note that you will not be required to enter your AOL login and password as part of this process.
Below are links to help articles on how to update the settings for the most common email software
Outlook 2007
Outlook 2002/2003
Outlook Express
Thunderbird for Windows and Mac
Mail on Mac OS X
Please make the necessary updates as soon as possible.
The infrastructure change we are making will only affect email sent through third party email software. Email sent using AOL software (AOL 9.0, 9.1, 9.5, Desktop), AOL webmail, or a mobile device such as a Blackberry or iPhone will continue to have copies of sent email placed in the Sent folder.
Thank you for using AOL Mail.
Regards,
The AOL Mail Team
I can only add that of all times I tried to ask Yahoo! Mail team for similar fixes (mostly related to handling of international char encodings), none succeeded.
I got usual third-world support banter instead, and promptly decided to close my Y! account, few years ago.
Thursday, February 12, 2009
Wii are the champions

Checking up Nintendo Wii for a week (bought it as a gift, in advance).
First impression - it's very tightly built, very good quality of materials, all connectors connect very easily and they have easily understandable, not confusing outlines and forms, and all use different colors. Gives you a nice feel to setup such nicely-built system.
Starting up gives you tons of warnings - you must be over 18 to legally set it up. Otherwise, you kiddies are breaking the Nintendo agreement and when you get injured boxing, or break that antique vase that cost your daddy 150K - Nintendo just wash they hands and smile happily. (Ask your parent to read EULAs and press A button!)
User interface is so immersive! Wii Remote gives slight rumbles when you point at buttons on screen. It also emits sounds in-game. Really cool and important for multiplayer (indicates who's turn in Bowling, for ex.)The "Channels" concept nicely replaces "PC programs" concept; instead of "PC desktop" you have "Wii Menu".
That's it - no wondering around. Just 4 screens of 12 channels each (max 48 channels).
I had 6 channels installed, but, after visiting Wii Shopping Store, increased to 9, for free.
It's really nice and easy, and good for your body. The best video-gaming for your body. Fitness is better - but, you know, there's Wii Fit set on sale...
What bothered me most in user experience is annoying Yes/No confirmation menu when you try for Wii Menu from within a game or an activity. If you press "Home" button on Wii Remote, you first get Home menu where you can select an action.Usually those include "Wii Menu" , "Reset" , "Wii Remote Settings" , and "Operation Manual".
You move the pointer, you get the rumble as you focus. You do confirm by pressing "A" button.
But, in case of "Wii Menu", you get that extra Yes/No confirmation dialog.
Why do they consider everyone so stupid - to make so many actions already and STILL get ANOTHER nag dialog - does not seem reasonable to me. Is this some cultural difference?Even if there's danger of mistakenly going to Wii Menu - why not every mistake is covered by confirming dialog?
This is Windows 95 style and ought to be avoided.
Those who do mistake, do learn and stop mistaking.
Why pester everybody on such common action?
Another note - and quite understandable - is that there are too many warnings in Sports Pack.
Those are usually to make sure you're strapped, have a jacket on Wii Remote, have enough space, have thumbs to hold the remote tightly etc.
Let's count them - I will recount for you all user interactions on my way to start Bowling, single user game.
1. Open "Disc Channel" from Wii Menu. You will see channel preview.
2. From the channel preview, pick "Start". This brings up a remote jacket warning.
3. From the jacket warning page, you either timeout or press A after some reading delay and you get new window.
4. Now you're asked to press A+B buttons simultaneously. Is this to check that you have a working thumb and index fingers?
5. Finally you get Wii Sports menu - here you select which game of 5 you want. Press Bowling.
6. Number of players, or training mode. Press 1.
7. Here you're asked to select Mii (artizans) per each player.
8. Another jacket warning! Press A to continue.
9. Al last, you see the game intro. First player is asked to press A+B to confirm.
10. Real bowl begins. Make a throw. If you do incorrect throw, Wii will warn you and make you press B to confirm.
11. Now you've (hopefully) scored a throw. Alt angle replay, plus cheering voice comment. Nice. Press A and repeat steps 10 until game end.
12. Game Finished. You see your final score, as well as all scores. Press A.
13. Final screen. You see your current Skill Level in chosen game, and it's dynamics. Nice. Press "Again" to go to 9 or "Quit" to go to 5.
Is not it a bit too much of confirming? You have to be pretty determined to get into play.
Makes sense to warn once, or maybe 3 times - but every time? I know we're talking about children here.
I can understand. I just wonder if there's another way, like fast voice warnings while the games load?
(By the way, not every child CAN read those warnings! I am not even talking about who WILL read)
Last up, my thought on improving the channel content - we need more free channels.
Why not turn it into something like Nokia WidSets, where anyone can write a useful bit of functionality (stock quotes, web clips, car alarm integration, world-wide web cams) and put it in for Nintendo's approval, and be sold in Wii Shopping Channel with some revenue split like Apple does in iTunes App Store?
Right now it seems rather limited - and I can understand that Nintendo wants us to spend more on GAMES.
What if I am not a gamer type but I like the console and I hate PC and I don't have a Mac?
Those types are mostly senior/disabled citizens, or there are some people who have adverse opinion on PC at home (I had one programmer friend who never had a PC at home, intentionally) - but anyway - they can be made a paying audience while their kids are at school.
Thursday, May 22, 2008
6 steps to better PC software from Nokia
Hello Nokians,
this is just some free advice, a private opinion from an engineer, software architect, AND a prosumer.
Take it or leave it.
What would I do if I had a chance to change Nokia Way?
1. N-series PC Suite and Communicator Marriage.
(get back Lifeblog moniker)
I would certainly evolve the N-series PC Suite, which currently holds the palm of Usability. The most obvious step would be to add messaging features that the suite currently lacks.
2. Ditch the Video Manager, Music Manager in favor of WMP integration.
Well, the time has come to confess - VM and MM are pure crap.
If I'd wanted so much to keep them I would put in into a niche of S40 Suite or something.
3. Nokia Music Client ("Euphoria") as a WMP Skin/Plugin.
While the current buggy beta is "beta than nuthin", and has the potential to keep the high UI standards of N-Series, I do not want a separate Music Database just to use my music with my phone. Either use the WMP DB, or "become the WMP", i.e. re-engineer it as a WMP Skin or Plug-in.
Knowing the strategy is cross-platform, I would then say - integrate with iTunes Music Folder/DB on Mac, integrate with WMP "My Music" and DB on a PC, and with some popular Linux player, too.
Administrative effort needed to use large music libraries with two players concurrently is not worth using Nokia Music Client, IMHO.
4. LifeBlog becomes the N-Series PC Suite.
With all the search for a "golden formula" of the PC Suite, why not consider ditching the PC Suite for good? I mean, you have LifeBlog, the pieces missing are Sync with Outlook, One-Touch Access, and Messaging.
Everything else is for geeks, geeks can get tools wherever.
I mean, why not nicely tuck all those under LifeBlog's wing and you'd have the iSuite for Nokia Phones!
Just make it ONE Window, ONE UI. Call it OVI/PC, if you please.
Let's think of consumers/prosumers, not mainly geeks. Severe some features in favour of majority. Knowing where to cut is important, remember Occam's.
Otherwise this is starting to look clumsy like Oxygen's Products.
5. Nokia Communicator rehash.
Well, it's just a beta. You have to pedal around it for the view to stay up-to-date.
Please make it sync everything without users having to click around.
6. Well. And. Of course, Fix all the bugs filed for PC Suite :)
this is just some free advice, a private opinion from an engineer, software architect, AND a prosumer.
Take it or leave it.
What would I do if I had a chance to change Nokia Way?
1. N-series PC Suite and Communicator Marriage.
(get back Lifeblog moniker)
I would certainly evolve the N-series PC Suite, which currently holds the palm of Usability. The most obvious step would be to add messaging features that the suite currently lacks.
2. Ditch the Video Manager, Music Manager in favor of WMP integration.
Well, the time has come to confess - VM and MM are pure crap.
If I'd wanted so much to keep them I would put in into a niche of S40 Suite or something.
3. Nokia Music Client ("Euphoria") as a WMP Skin/Plugin.
While the current buggy beta is "beta than nuthin", and has the potential to keep the high UI standards of N-Series, I do not want a separate Music Database just to use my music with my phone. Either use the WMP DB, or "become the WMP", i.e. re-engineer it as a WMP Skin or Plug-in.
Knowing the strategy is cross-platform, I would then say - integrate with iTunes Music Folder/DB on Mac, integrate with WMP "My Music" and DB on a PC, and with some popular Linux player, too.
Administrative effort needed to use large music libraries with two players concurrently is not worth using Nokia Music Client, IMHO.
4. LifeBlog becomes the N-Series PC Suite.
With all the search for a "golden formula" of the PC Suite, why not consider ditching the PC Suite for good? I mean, you have LifeBlog, the pieces missing are Sync with Outlook, One-Touch Access, and Messaging.
Everything else is for geeks, geeks can get tools wherever.
I mean, why not nicely tuck all those under LifeBlog's wing and you'd have the iSuite for Nokia Phones!
Just make it ONE Window, ONE UI. Call it OVI/PC, if you please.
Let's think of consumers/prosumers, not mainly geeks. Severe some features in favour of majority. Knowing where to cut is important, remember Occam's.
Otherwise this is starting to look clumsy like Oxygen's Products.
5. Nokia Communicator rehash.
Well, it's just a beta. You have to pedal around it for the view to stay up-to-date.
Please make it sync everything without users having to click around.
6. Well. And. Of course, Fix all the bugs filed for PC Suite :)
Labels:
NOKIA,
NOKIA Lifeblog,
PC Suite,
usability,
user experience
Wednesday, December 19, 2007
P1i user interface - is it any better?
I've finally had some time to spend it with SonyEricsson P1i, the avant-garde of "serious" SE smartphones. As I have previously confessed, their previous generation flagship product had been my device of choice for almost 3 years.
Must I say I had been quite excited and I had some expectations of increased usability, robustness and stability of the new runner-up P1i.
But it turned out, that the P1i device (again! after the lackluster P990i) is not up to pretty high usability/ergonomics standards that I had enjoyed on my trustworthy P910i.
And here's why.
1. First off, they left off the 5-way JogDial wheel.
This wheel alone is an "interface" on its own.
The whole menu structure in UIQ2.1 has been fully accessible with just your left thumb on jog dial!
You could open menus, close them, navigate within, select items, run them with only a thumb, single-handedly, even with the flip closed!

Now all that goodness is gone, since the P990...
2. They also left off the phone buttons.
P1i contains only qwerty keyboard, no "Answer"/"End Call" or other phone-related buttons.
What this means is that you have to use a mixed interface - you dial numbers on keyboard, then press on-screen "Call Button" (or press the jog dial inside). Switching from virtual keys for control, to physical buttons for numbers.
Sometimes the on-screen buttons are small and you need stylus... Needless to say - one hand/on-the-go operation becomes cumbersome. In P910i it was solved by a flip-closed mode, which beautifully shifted the complexity away, switching display sensors off while on-the-go. But here in P1i - another step back and dispersion of your attention.
3. The ubiquitous "More" button.
This is the most annoying and cumbersome feature of all UIQ3 user interface.
Whenever some application designers feel some "need of space" for all the menu features that don't fit into the 3 soft-buttons in the lower bar, they hide all the goodness into a single and impenetrable "More" button, behind which hell only knows how many useful (or completely not) features are hidden.
User often is compelled to press that button just to see what else that application can provide.
This is so inferior to the UIQ2 and MacOS paradigm of top-bar pull-down menus that I have nothing else to say. Just check the screenshots. This would have been OK for your dumb phones with buttons only, but on a touch-based smartphone! Duh.
How could hiding part of UI help user productivity and UI transparency I just can't imagine! I think we've been there already with Microsoft's "Personalized Menus".
4. The 3 ways of input.
User may interact with P1i using either:
-- keyboard,
-- side buttons and jog dial,
-- touchscreen+stylus,
-- touchscreen+fingers.
Having many options for control could sound as advantage, but those inputs methods are complementary throughout the UI, not replaceable!
For some features you HAVE to use on-screen soft-buttons, which are easiest and most conveniently pressed with just a finger; for others, such as very basic CLOSE button in the upper right, you better be holding a stylus since the button itself is quite small; for still others (CAMERA) there's no way but to press a side button.
This makes user experience tattered into pieces of using different input methods.
Especially funny when you see several "Close" buttons on the screen - one for the stylus (top right corner) and one for non-existing in P1i "three buttons row" (lower right)!
5. "Do you want 5, 15 or all of your apps?"
The paradigm of "More", "Even more" and "All" continues in the application strip at the bottom of the Home screen.
With touch screen, there could have been a better solution - a scrollable "infinite" ribbon of icons, with "inertia", like a wheel that would roll for some time after you clicked and dragged it. Such ribbon would effectively allow to do away with the application menu and the 12-icon mode. Customization would be accomodated by re-arranging icons order on the launch ribbon.
Instead, user sees 5 icons, by clicking on a divider a user can see 15 icons (with peculiar diamonds replacing empty spaces!) or, finally, the whole application menu.
Now what if I want space just for 7 or 19 icons? :)
6. The Ulimate Goal.
So what it is, the ultimate goal of such conformist UIQ3 UI design?
Compatibility with buttons-only phones.
And while I can agree that it serves them well (take MOTO RIZR Z8 for example), at the same time it denies the usability achievements of the past platform, UIQ2.1.
Such situation derails old-time users from UIQ and drives them in hordes to Windows Mobile in search of 'new cool' stuff and 'powerfull specs' stuff.
I have seen this situation en-masse in a well-known Russian online forum which used to be alive with the joyful sounds of P910i users, but not anymore. Most people left, only occasional newbies ask for a solution and some old-timers file their report on migration to Windows Mobile world. Some also express intent to migrate there since they did not like what they saw in UIQ3 devices from SonyEricsson either.
Would it not have been possible to create a separate, simpler version of UIQ, like Nokia S60's cousin, Series40?
'One size fits all' strategy failed, at least in the usability plane. And that means a lot nowadays.
What's most annoying is that SonyEricsson had 3 years since the P910i launch to improve and polish the highly valued hardware ergonomics and interface before iPhone hit the shelves! This very strategic blunder seems oh so familiar...
They were the closest shot to the "simplest stuff", the bread and butter of Apple Inc.
This may be also testified by the fact that Apple went as far to help SonyEricsson to write UIQ-based "iSync agent" for P910i, which installs on the phone the first time you try to sync it with a Mac. The sync support is full, up to the contacts pictures.
And yet SonyEricsson pursued some other goals [comments are welcome] and basically slipped down on the software, while mucking the hardware with a non-optional keyboard, and a shorter screen.
Yes, 3G, yes, WiFi, but why go away from marvels of past technology? Would you buy a PC with a faster WiFi but smaller screen and less convenient (and non-removable) keyboard and mouse?
I loved P910i and seeing SonyEricsson fall was a pain.
Such is my completely personal and biased old-timer SonyEricsson hardcore smartphone user opinion.
All comments with no offensive meaning will be published.
Must I say I had been quite excited and I had some expectations of increased usability, robustness and stability of the new runner-up P1i.
But it turned out, that the P1i device (again! after the lackluster P990i) is not up to pretty high usability/ergonomics standards that I had enjoyed on my trustworthy P910i.
And here's why.
1. First off, they left off the 5-way JogDial wheel.
This wheel alone is an "interface" on its own. The whole menu structure in UIQ2.1 has been fully accessible with just your left thumb on jog dial!
You could open menus, close them, navigate within, select items, run them with only a thumb, single-handedly, even with the flip closed!

Now all that goodness is gone, since the P990...
2. They also left off the phone buttons.
P1i contains only qwerty keyboard, no "Answer"/"End Call" or other phone-related buttons.What this means is that you have to use a mixed interface - you dial numbers on keyboard, then press on-screen "Call Button" (or press the jog dial inside). Switching from virtual keys for control, to physical buttons for numbers.
Sometimes the on-screen buttons are small and you need stylus... Needless to say - one hand/on-the-go operation becomes cumbersome. In P910i it was solved by a flip-closed mode, which beautifully shifted the complexity away, switching display sensors off while on-the-go. But here in P1i - another step back and dispersion of your attention.3. The ubiquitous "More" button.
This is the most annoying and cumbersome feature of all UIQ3 user interface.Whenever some application designers feel some "need of space" for all the menu features that don't fit into the 3 soft-buttons in the lower bar, they hide all the goodness into a single and impenetrable "More" button, behind which hell only knows how many useful (or completely not) features are hidden.
User often is compelled to press that button just to see what else that application can provide.
This is so inferior to the UIQ2 and MacOS paradigm of top-bar pull-down menus that I have nothing else to say. Just check the screenshots. This would have been OK for your dumb phones with buttons only, but on a touch-based smartphone! Duh.How could hiding part of UI help user productivity and UI transparency I just can't imagine! I think we've been there already with Microsoft's "Personalized Menus".
4. The 3 ways of input.
User may interact with P1i using either: -- keyboard,
-- side buttons and jog dial,
-- touchscreen+stylus,
-- touchscreen+fingers.
Having many options for control could sound as advantage, but those inputs methods are complementary throughout the UI, not replaceable!
For some features you HAVE to use on-screen soft-buttons, which are easiest and most conveniently pressed with just a finger; for others, such as very basic CLOSE button in the upper right, you better be holding a stylus since the button itself is quite small; for still others (CAMERA) there's no way but to press a side button.
This makes user experience tattered into pieces of using different input methods.
Especially funny when you see several "Close" buttons on the screen - one for the stylus (top right corner) and one for non-existing in P1i "three buttons row" (lower right)!
5. "Do you want 5, 15 or all of your apps?"
The paradigm of "More", "Even more" and "All" continues in the application strip at the bottom of the Home screen.
With touch screen, there could have been a better solution - a scrollable "infinite" ribbon of icons, with "inertia", like a wheel that would roll for some time after you clicked and dragged it. Such ribbon would effectively allow to do away with the application menu and the 12-icon mode. Customization would be accomodated by re-arranging icons order on the launch ribbon.Instead, user sees 5 icons, by clicking on a divider a user can see 15 icons (with peculiar diamonds replacing empty spaces!) or, finally, the whole application menu.
Now what if I want space just for 7 or 19 icons? :)
6. The Ulimate Goal.
So what it is, the ultimate goal of such conformist UIQ3 UI design?Compatibility with buttons-only phones.
And while I can agree that it serves them well (take MOTO RIZR Z8 for example), at the same time it denies the usability achievements of the past platform, UIQ2.1.
Such situation derails old-time users from UIQ and drives them in hordes to Windows Mobile in search of 'new cool' stuff and 'powerfull specs' stuff.
I have seen this situation en-masse in a well-known Russian online forum which used to be alive with the joyful sounds of P910i users, but not anymore. Most people left, only occasional newbies ask for a solution and some old-timers file their report on migration to Windows Mobile world. Some also express intent to migrate there since they did not like what they saw in UIQ3 devices from SonyEricsson either.
Would it not have been possible to create a separate, simpler version of UIQ, like Nokia S60's cousin, Series40?
'One size fits all' strategy failed, at least in the usability plane. And that means a lot nowadays.
What's most annoying is that SonyEricsson had 3 years since the P910i launch to improve and polish the highly valued hardware ergonomics and interface before iPhone hit the shelves! This very strategic blunder seems oh so familiar...
They were the closest shot to the "simplest stuff", the bread and butter of Apple Inc.
This may be also testified by the fact that Apple went as far to help SonyEricsson to write UIQ-based "iSync agent" for P910i, which installs on the phone the first time you try to sync it with a Mac. The sync support is full, up to the contacts pictures.
And yet SonyEricsson pursued some other goals [comments are welcome] and basically slipped down on the software, while mucking the hardware with a non-optional keyboard, and a shorter screen.
Yes, 3G, yes, WiFi, but why go away from marvels of past technology? Would you buy a PC with a faster WiFi but smaller screen and less convenient (and non-removable) keyboard and mouse?
I loved P910i and seeing SonyEricsson fall was a pain.
Such is my completely personal and biased old-timer SonyEricsson hardcore smartphone user opinion.
All comments with no offensive meaning will be published.
Labels:
P1i,
SonyEricsson,
UIQ3,
usability,
user experience,
user interface
Friday, September 21, 2007
iPhone user experience comments
iGot iPhone :)And so I spent some time figuring out if there are some blunders in it's UI.
There were none. Good job Apple!
There are some functionalities missing, such as MMS or on-the-go media management, but I believe they are dropped by intent, to execute along a clear strategy.
Mac now is the digital hub. ("Oh, sorry PC, you too!")
The only obvious point I would improve is in the Mail client:
- if you happen to have many mailbox accounts (as you can see, I have three), you must go to each other Inbox separately, because the e-mail does not aggregate them into one place like Apple Mail on Mac does.
And so it takes 10 taps just to look into headers in all three mailboxes. This would be reduced to 2 taps if Apple chose to accept the Apple Mail's approach. Maybe this will be fixed soon, in the iPhone Firmware update 1.1.1.



<--- iPhone Mail

That's how Apple mail aggregates mailboxes --->
Another thing I noticed is that there's no task switcher aside from the Home Button, that would take you to the main program menu. Although this initially feels as a drawback, this way the user has only one way to start a program, and the icons are always fixed in the same places, which decreases time-to-launch for every program as the user becomes acquainted to their location on screen.
There are some 3rd party utilities that allow you to have alternative task switcher (SummerBoard). You press in the lower right corner and drag to the centre some analog of "Sun wheel" whith all the programs sitting on it's "rays". The further you drag, the bigger the icons. Moving along the circle selects the program icon. There appears a separate button for lauching the selected application.
Quite innovative, but clunky and requires to use both hands for a faily basic task.
It happened so that Apple products had never had lack of style.
And this one is not an exception. The company has a track of setting trends for few industries already. All-in-one, translucent colors, USB, floppy-less, IEEE1394, OOP, media management and distribution, now cellphones...They are the true creative power, and have the guts to follow their vision, through the years.
To be competitive, just market share is not enough. One has to be as bold and creative as Apple, not just foresee the Future, but create it. And they made it.
Now the multi-touch UI is Present.
So if you are in UI field, or "just browsing", by all means check out this new level of usability.
I also welcome your comments.
Labels:
Apple,
iPhone,
UI,
usability,
user experience,
user interface
Friday, August 17, 2007
Why don't I shave with a RAZR?
I did another wild thing and swapped cell phones with my girlfriend for a week. Or two.

And here's my MOTOROLA RAZR UI analysis.
Here I go again, focusing only on points which could be improved, given due attention to detail and a good sense of usability.
May I call it my "6 steps to make RAZR sharper" guide? :)
Point 1. Right-to-Left.

Okay, this is very obvious for everybody. MOTO sticks to its tradition (against everybody else) of putting affirmative buttons on the right, negative action button on the left. It would have been memorizable, had they also chose to reverse the red&green call buttons. But they had not! So to Accept a Call, bear to left. But to Accept an Action, bear to the opposite side :)

Okay, this is very obvious for everybody. MOTO sticks to its tradition (against everybody else) of putting affirmative buttons on the right, negative action button on the left. It would have been memorizable, had they also chose to reverse the red&green call buttons. But they had not! So to Accept a Call, bear to left. But to Accept an Action, bear to the opposite side :)
Point 2. Scrolling.

MOTO has it's own way of fast scrolling. You do it by pressing numbers! So 1-2-3-ish, from early 80s era! Yes, you need to estimate on the numbers of lines you don't even see!
Or else - press'n'hold'n'wait while watching the lines slowly click by, along with the precious seconds of your life.
A simple scroll acceleration after a certain amount of press time would be so much better!

MOTO has it's own way of fast scrolling. You do it by pressing numbers! So 1-2-3-ish, from early 80s era! Yes, you need to estimate on the numbers of lines you don't even see!
Or else - press'n'hold'n'wait while watching the lines slowly click by, along with the precious seconds of your life.
A simple scroll acceleration after a certain amount of press time would be so much better!
Point 3. Personal Tones.


If you set a personal call tone, say, for a friend, you also get it for the SMS from the friend.
So, setting and mp3 tune gives you whole lotta noiz at SMS arrival! Fun fun fun!
(Some SMS are sent at night, not to disturb with a call and a ring. Or across timezones.)
Point 4. Your e-mail is too long and will be deleted.

I know it sounds funny but it's not so when you wait for an important e-mail, and you finally get it, and you see:

I know it sounds funny but it's not so when you wait for an important e-mail, and you finally get it, and you see:
Looks like some arhitecture limitation?
Point 5. Bleeps and moans.
The phone uses sound signals profusely.
It will not let you ignore an unread message, unanswered call, low battery.
You're better off fix it now or switch off sound.
There should have been an option to turn off such signals, akin to Service Jingle and others, that are controlled in Settings - Network.
Point 6. No repeated alarms.

You may set the alarms only as 1-time events.
Minor things:

There's a menu called Initial Settings. Hmm? Sounds like a place you only go once you turn it on the very first time. The right wording would be Basic Settings. Anyway, the only way to set up text entry modes is when you go to a place where you can enter some text and there you may invoke a context menu with Entry Mode and Entry Setup.
Oh, and don't forget! Your settings may change depending on the text field settings -try to go to e-mail setup and you'll see that now dot is not where it was, but @ ate it's lunch.
Themes are not in Settings - Phone, but are in Multimedia menu.Okay, maybe 2 weeks was not enough to adapt myself? My answer is - the phone has to be supportive, not distractive.
All-in-all, I think this phone has rather impressive and solid UI, it is totally less cumbersome than on smartphones - and here we get to the point - either MOTO pays more attention or ... the phone is plainly simpler than the smartphones.
Whichever you think matters more in the case?
Friday, July 27, 2007
6 steps to improve UIQ usability

Hello again,
I am back with some notes on how to improve SonyEricsson's UIQ user interface.
The UIQ is a great platform. To help make it even greater, in this blog I am focusing only on deficiencies in the usability, and show ways to fix them.
As a reference point let me use SonyEricsson P910i. I know, I know. Not the latest & greatest, but I think the most convenient and stable of the currect P-series smartphones. 5-way jog-dial and detachable keyboard seem to me quite hard to give up.
I have used P910i for 3 years. I really liked it, before I got N95.
I will be doing a new analysis on P1i once I get my hands on it.
Point 1. No Task Switcher.
There's no quick and easy way of switching from one running program to another. You have to go back to Applications menu, and reselect the application, as if you want to relaunch it. Install another 10-30 applications and you have to scroll a lot, just to switch tasks. Yes, there are 3rd party task switchers that allow you to close apps and switch between them.
SMan is free, but cumbersome, Magic Task Launcher is the best but it is not free.
Why not make such basic tool a UIQ feature?

Point 2. No "Send a Message" in the Call Log menu.
Go to the Call Log, and select an entry. There's no easy way to send a message to that person. There's no Send SMS nor Send MMS in the menus.
Even better would be to have clickable buttons, like the ones in the Address book.

The workaround it to go to Edit - Copy Number, then go to Messages - New SMS - and paste the number.
How cumbersome!

Point 3. Not easy to scroll to top and to bottom.
OK, this one is minor, but with a large number of items (I used to have 1100 SMS) it is really hard to get to bottom of the list. You open an application, the item list is at the top, and there's no way to reverse the sort order.
All there is to do is press the small "page down" button (depicted) and hold it, until you get to the bottom. This could take some time.
Why not save user's time by placing two small buttons more (Top/Bottom), above and below the PgUp/PgDn buttons?
Point 4. "Jots" are sorted in wrong order.
This one is related to inability to quickly go to bottom (previous point).
It is perfectly within human nature to use recent data more often than old (possibly obsolete) data. It's hard for me to realize why developers decided to put recent jots to the less accessible bottom of the list. I used to have 200 notes in my Jotter, so getting to the last one took me quite some effort.
A stack organization of jotter would have been just perfect.
I just screams for reversal of the sort order.

Point 5. Crappy browser.
The built-in browser is now mostly dysfunctional.
It mainly supports cHTML and WAP sites, most pages load forever, it often crashes the phone with a white screen, or hangs, or just refuses to load pages.
The picture on the right shows the phone's default pre-set Start Page at SonyEricsson. It used to be accessible 2 years ago :)
Luckily for all, there's the saviour - Opera Mini v2.
It allows for full-screen view, saves your traffic, does it with style and animation and the web images quality is great.
They dropped support for fullscreen view in v3 so I stayed at v2. No big deal.
Point 6. No alarms in power-off mode.
Unlike NOKIA platforms, UIQ does not wake up from power-off to ring you an alarm in the morning.
I don't know if it's a hardware or a software limitation, but certainly a setback in total product usability.
That was my 3rd review of "unusabilities" in major cellphone platforms.
Stay tuned for more!
Labels:
interface,
SonyEricsson,
UI,
UIQ,
user experience
Tuesday, July 24, 2007
6 steps to improve NOKIA S60 UI
Hello pundits,today I continue the "UI improvement ideas" series and today our guest is.../drumroll/...
NOKIA S60 platform, as captured in it's N95-1 incarnation (f/w 11.0.026).
For the purpose of this review, I was using only default settings, and it's worth to note that some of my points could be alleviated by changing the defaults. But changing them could be even a tougher task.
Here's the brief: yes, the S60 is more complex than S40, and so it's less intuitive.
But it gives you whole lot'o'features!
Anything on Earth in mobile smartphone arena - you can have it.
The price? You must subdue to arcane logic of it's user interface.
Get used to it or get lost.
Here I will focus on how this UI makes you focus more on what you want, instead of trying to get out of your way.
Point 1. Bag of buttons. Think hard before you pick one.I am not against buttons per se, just let me show you how confusing they can be.
The three most-used features of a phone are
a) call register,
b) contacts book and
c) SMS messages.
With S60, you have to think hard which button you press for doing those tasks, the phone buttons are all close to each other, and on the same left side by default.
It makes it difficult to pick the right button for the task, without a considerate and significant focus on what you're trying to accomplish. Thus, it all makes UI less intuitive and more cumbersome for everybody but the S60 fans or long-term users.
Ex. 1. Let's go to Contacts.
Unlock the phone. By default, the Contacts label is selected in the shortcuts strip near the top of the screen. Looking at the top of the screen and knowing (from many mobile phone UIs) that the right-side button [usually] Exits, and the left-side button [usually] Opens, I click the left button and... go to Calculator instead. That's because I was not attentive enough to look at the bottom of the screen. Of course, my fault. But what if I am in the street? Or in a car? For sure, I need my attention for other things. So how can I have my attention also in two places of the screen? Only by getting used to S60. But that's counter-intuitive.
Ex.2. Call register on-the-go.Imagine you are walking the street or driving a car.
You remember you promised to call back, while you were busy in another conversiation.
You take the phone, unlock it, and looking at the screen, it's not easy to understand how to go to the call register. There's no icon for it. You have to remember to press the green call button.
So here we get to the next
Point 2. Which calls you want? [think harder]The call register is split into 3 parts - Dialled numbers, Received calls, and Missed calls.
In your mind, you have the name of a person, not the type of call. So now one more time to think harder and remember your recent history of communication with that person.
Or else - flip through all three logs, one by one, looking for that person's name.
A much better call register would have all calls in one list, with appropriate call type icon beside each entry. But that would be so UIQ-like...
Oh wait! You still can do this UIQ-like trick in S60! But what it takes?
Go to Menu - Applications - Log. Click Right button.
You will see all call activities, including packet data, SMS, MMS and WLAN access.
Of course, you can set the shortcut to Log on either the standby labels or to one of the soft-button.
And I like that flexibility.
But how many users notice and actuallty do that, instead of routinely hacking through the default setup of the interface?
Point 3bis. "No files".
Put some music files onto phone. Take some pictures.
Now, imagine you have taken some really nice pictures, and a lot of them.
Close all applications. Start the Gallery - Images & Video.
Right after the application start, it shows "(no images or videos)" on screen!
That's when the heart breaks. The more pictures you have, the longer your face grows while you try to understand where the stuff went. That's because the application scans the memory for files. If the progress takes some time, a progress bar says "Opening" but this is understood as "opening the application", not as "yet scanning for your files".
And you could still see the scary message in background.
Why not put another message, say, "(scanning)"? The same behaviour goes on in the Music player while it scans for tracks.
Point 4. Not every program born equal. [So dig around before you find the right place, or use your memory]
Let's install some 3rd party programs into the phone.
Let's count now how many clicks you need to get to one of them (phone unlocked).
Click1 - the Menu button. Two more "Up" clicks to select Application item.
Centre click to Open. Now you have the Nokia apps at the top, so you have to scroll.
OK, the fastest way to scroll is Up. And the final click to Open the app.
Total=6 clicks as bare minimum for a 3rd party app with no pre-set shortcut.
Here's the same feat in UIQ2.1 - (flip open).
Scroll by using the jog-dial until you select the app. Click the jog-dial inside.
Here's the same feat in iPhone (unlocked).
Press the icon of the app.
Point 5. Locked away from a user.Imagine you use your phone at your work desk.
You leave it on the table, so there's no need to lock the keypad.
But also, there's no way for the phone to know that.
Now, you put in a charger cable in.
This is one way for the phone to know that a keypad lock is not needed.
USB connection is another way.
The lock is needed only when the phone is being carried, right? It was designed to prevent accidental dials and keypresses when on-the-go.
Now, there are 2 cables in the phone (it is hardly being on-the-go) and it still locks the keypad!
No way I need that behaviour.
Ex.1. Four clicks to see new SMS or use USB cable.
Every time I get an SMS I need to do 4 button clicks instead of just one!
2 clicks to Unlock, one more to make the unlock message go away (which is another botherance, since I prefer to get a message only when there's something that needs my aditional attention), and one final click to show me the SMS. Quite annoying.
The same "locked nature" of S60 show itself when you want to use USB cable to sync it, or transfer music, or print images, or use it as a flash disk.
You connect a USB cable and the phone recognizes it, and asks you to choose one of four options - PC Suite, Mass storage, Image print or Media transfer.
But the phone does not unlock itself!
Quite contradictory behaviour.
Point 6. Kid's e-mail.
This one is pretty simple. The e-mail client does not support HTML.
Not to say of animated GIFs inline and such.
EDIT: You may still see the Attachment.html in the Web browser, though, but it requires 3 extra clicks per message.
So I'm adding Point 6bis for a balance-
There's no visual clue to how much progress the battery charging process made.
It could be 4 minutes left to full charge or 44 minutes - there's no way to tell.
This concludes my short review of NOKIA's newest mobile phone user interface, commonly known as S60 v3 FP1.
Watch this space for our next "guest"... from SonyEricsson!
Monday, July 23, 2007
NOKIA S40 user interface comments
With this post I begin a review of all major cellular phone's user interfaces - NOKIA's S40, S60, S80, S90, and SonyEriccson's UIQ2.1, UIQ3.I will start with the most mature (being the oldest of all) mobile platform UI - NOKIA S40.
It is used in most phone models manufactured by NOKIA. In my review I used NOKIA 6170, not the newest but the neatest (to me) of them all.
http://europe.nokia.com/A4144202
These ideas should help developers to focus attention to details and continuity of user experience, thus enabling more competition for consumer mindshare to products of companies with a history of better attention to user interfaces and software interface design (Apple Inc. being major example).So here's my "6 steps recipe" to improve S40 UI:
Let's start with the main piece of UI - Menu. Press the centre button of the joystick. Now what we see is many items, and the label of the centre button has changed to Select.1. Incorrect! We do not select items here to perform an operation in second step (this is PC desktop metaphor). A proper name would be Open. This is what this button does - opens an application or a lower-level menu. We select what we intent to open by using the cursor buttons.

2. Now let's go to Settings. Here we see the most confusing part (and I have just seen again an engineer trying to make his way here) - three ambiguos items - Configurations, Phone, and Call Settings.
Very confusing! "Phone"? All I have in my hand is Phone. What else? I may just as well go there directly without thinking. Hence - this submenu needs to be eliminated completely, and it's content disseminated into others. Maybe, call it Personal, and place Shortcuts, Main & Mini Display inside? Settings - Configurations? Hmm... Now that I know what it is. It's Access Points, that's the name for it, and why not move it where it belongs, to the Settings - Connectivity submenu, along with Infrared and Bluetooth?
A usage example from life - "I want to change Configuration of Phone Calls. Which of the 3 items should I Open? :)"
3. While we're still here, Enhancements (please see the word definition at http://webster.com/)- a strange name for Accessories.

4. Now on to Scrolling. Open some Contacts, or Messages window with a lot of items. Start to scroll down. And as you cross the "invisible border" between the last item and the first item, there's no visual clue except for the item number in the upper-right side of the screen. But rarely any user keeps an eye on it, simply because the attention is on the items themselves! The cursor does not jump from bottom to top to indicate the "end of file" situation. Why not? The same goes with the reverse scrolling...
5. The first thing a user does to new phone is set it's Date & Time. Luckily, it's done automatically the first time. But if you later want to change it, you're up for a S40 surprise. A logical place to go would be Settings menu. But no, in fact it's [hidden] in the Organizer. (I take it back - it's not so on all phone firmware versions)
6. Wizards. Now, I'm not being a pro-Microsoft fan, but there's some sense in them using Wizards in Windows almost abusively. In S40, if I go to some application that does not have settings (like E-Mail), it just throws me back with an error message, instead of nicely taking me to a Wizard that would let me set all missing settings, step-by-step.This concludes my brief analysis of S40 UI.
And while I admire the S40 as a mobile platform (ever-stable, works like TV) - compact, robust, fast and nice design of the 6170 phone, but it think there's still a lot to be done to improve the average user experience. And I showed you - how.
While this review shows only what the manfacturer might call "minor" issues, it is clearly instrumental in showing how all those issues add up to confuse the user experience.
Subscribe to:
Posts (Atom)




