Our smartphones have a lot of features in them, yet this is causing a divide. When we as power users look at a new device, we're expecting our favourite features to be there, yet this depth of power can be daunting to new users. A survey from Mformation (see here on the BBC), linked to earlier by Tzer2, reports high numbers of users having problems with setting up a new phone and accessing the available services. Read on for my take on the issue...
Read on in the full article.
As always, I'm going to fly the flag for that totally customisable interface AAS did a news story about a while ago.
I can't remember the name, but it basically started with a totally blank phone and let you add whichever features you feel you need, leaving out the stuff you don't want. It only exists as a concept, but it's a very good concept, and I wish some manufacturer would implement it.
Because you would add all the features you want, and place them where you want, you would find it much easier to remember where everything is. It's very much like starting with an empty house and adding all the furniture yourself.
I think you�ve made a good point there Ewan � the interface hasn�t changed much since the 7650, but the user base has. The difference is that the new mass market users are less likely to tinker with the user interface to see if something works. Whether it�s fear of �breaking it�, or just being daunted by all the different options and general complexity � it puts a lot of people off.
I read on AAS a little while ago about a concept �fillable� phone � you started off with very basic functions, and �poured� more in as you wanted to add more features. That could work well for users with basic needs. Part of the problem at the moment is feature creep � manufacturers and operators want to make mobiles do more and more, because the market is something of an arms race. Features have increased (see Tomi Ahonen�s post on Carnival 157 this week about convergence) but the user interface has not kept pace in terms of dealing with this complexity. I think it�s also true that users have not kept pace with the features that are now present on phones, but UI designers cannot blame consumers for not using those features, if they are not exposed in a pleasant way.
@Tzer2
Exactly what I meant.
You have to wonder though - how many of those phones would stay blank and be returned... "That fing doesn't even make calls"
Mattrad, glad to know I'm not the only one who loved the idea!
One reason it might not happen though is the compulsion of networks (and even manufacturers nowadays) to bundle services with the phone, which they would be reluctant to give up.
I'd love to see it done though, and on home computers too. My parents always have problems finding things on their PC, I think they'd find it a lot easier if they just had the icons for the programs they actually use.
@Tzer2, I am going only by what you have written below, I have not read the original article, but I don't believe such a phone would be a success - since it would not be suitable for the vast majority of users who just want to use the device as a phone (make calls, send sms, maybe just maybe send an email or two). It has got to sell too. Such a phone would be an interesting concept for powerusers or geeks - kinda like doing a bare minimal installation of linux and then installing only the stuff that you will need - preferably compiling from source :biggrin:
I understand this article seems to be about the challenge of engaging both groups of users.
Personally I would like the concept of modes taken further. Rather than two sets of standby icons and themes and stuff, one mode could be a "Phone" mode and provide the basic functions and the other mode could be an "Advanced" mode where much more could be provided along with the basic functions. I am taking a page out of one of my favorite applications - Spybot S&D - there is a default mode in which you can search for malware as promised on the cover, and an advanced mode which gives a lot of options that most end users may not understand.
Microsoft apps may not have two modes, but they try to present the simple most common usage scenario directly on screen along with toolbars and all the complexity is buried in menus or application dialogs (which you do not need to access if you dont want to).
There is also the fact that, by providing the same view to both sets of users, one set is complaining that "S60 is too complex, but the other group may be feeling that the whole thing is too dumbed down. Why cant I as a non-hacker user have better connection diagnostics than what is provided by the Connection Manager? How about plain text configuration files for applications - if the messaging app settings were stored in a text file, it would be so much fun. Take the audiobooks application, for example - I am able to use it because I can build book indexes by hand if I want to (se-radio.net provides 1 download a week). Of course, in the new version, one has that phone-pc mapping thingmajiggy, but plain text indexes are still helpful.
Although I am not a mobile developer, I have used S60 long enough to know that this is not the way they prefer to do things. But then what is wrong in wishing aloud? 😊
Sorry for the long post.
Although this takes things away from UI, perhaps we will see a move towards somewhat specialised phones? We�ve seen the Skype phone, the Facebook (INQ) phone. This isn�t a UI trend, but it does make it easy for people who think �I�d like to make calls but also check Facebook, that�s all�.
since it would not be suitable for the vast majority of users who just want to use the device as a phone
Actually that's exactly who it would be suitable for.
Instead of seeing dozens of icons on their phones, they could just have the half dozen that they actually click on.
They would never have to fight through a range of mysterious functions they never use, because they would never add those functions to their phone.
The reason why this would work so well is because different people use different functions, and it would let the user tailor their phone to their own needs. For example if someone never uses e-mail they wouldn't select e-mail as a function, and never see e-mail as an option, removing unnecessary clutter.
Current interfaces have so many functions because they're unsure what the user wants, and offer the entire range. Interfaces which have a smaller range of functions aren't the answer either because the user doesn't have a say in choosing which functions go into that smaller range.
By letting the user pick their functions from a setup wizard, they're having the best of both worlds: lots of choice but no clutter.
kinda like doing a bare minimal installation of linux and then installing only the stuff that you will need - preferably compiling from source
Erm, It wouldn't be anything like that at all, no installation, no compiling or anything technical at all.
The concept of the "blank" phone which we were discussing is to have a GUI setup wizard that asks you which functions you want to use, and then adds just those icons to a graphical interface. It would say "do you want to send texts?", and if you answer yes it would add the SMS icon. "Do you want to play games?", and if you answer no it would leave out the games folder. etc. You would only have to do this once, when you buy the phone, and then you could add more stuff later if you wanted to.
There wouldn't be any installation or anything like that, it would be purely about hiding the functions which the user doesn't want to access.
@Tzer2, point taken. I guess I misunderstood you initially. That comment about installing from source was made in jest , although i imagined installation would be involved.
I guess the same concept is used when the Resco News app starts up for the first time. It asks you what sort of topics you are interested in, and proceeds to add rss feeds accordingly. Quite helpful really. And I can see what you mean.
LTV, apologies from me, I probably should have described the concept in more detail for the benefit of people who missed the article, sorry if I sounded a bit sharp.
The AAS news item about it (still can't find the link!) had a really good photo to get the idea across, it was basically a blank touchscreen phone with a sign saying "I am empty, click here to start filling your phone" or something like that, which then led to the setup wizard.
A lot of "web 2.0" sites and services do seem to do this kind of thing, but no one has used it as a main interface for a device so far. The nearest I can think of is the EEE PC's favourites tab, which you can set to be the default front page and fill with large icons that go to particular apps.