Wednesday, April 14, 2010

android user experience

see what I did there? no? it doesn't matter, you're not even reading this.

since I've recently twisted my own arm into spending more than 2 quid a week on my mobile phone, which was actually 2 quid a week on a sim card which was hoofed into a handset from 1999 running symbian s60 which I didn't like when I was using it and like even less now that I'm not, I've been wondering how I might somehow get into experience design for mobile platforms. I've been designing for web and web-based channels for donkey's years and more recently working on complex applications for trading platforms, but I've not really delved deeply into mobile as yet, other than the wap sites we pushed out for Sun Microsystems many years ago which amounted to 17 links in 5 languages that didn't really go anywhere, but we did make the logo really much smaller than we were supposed to, which, in itself, was a triumph of vectors and transparency.

a few weeks ago, I was interviewing for a user experience design position with Qualcomm, which was to be working on their next-generation mobile platforms alongside and incorporating brew, plaza and lots of other nice things that you rarely see in carphone warehouse, but that position went the way of many other full-time permanent user experience positions. that's to say it didn't go anywhere at all. I was phoned before the second interview to say that the position had somehow vapourised internally by law of the corporation and that they were very sorry but it just doesn't exist now so you can't do it. despite it not coming to anything it did at least pique my interest, since I did my usual copious research on the subject in order to perform well at the interview I didn't end up doing.

what has piqued me even more, if there are levels of pique, is that when I started my current position at Tobias and Tobias, working for financial services clients in the city, was the fact that not only does almost every single person on the train, on the tube, walking down old broad street or sat in bishopsgate, own, and is permanently conjoined with a smartphone of some descrption, they own, and are often conjoined with a smartphone of some other description. at the same time. and three on the go is not as uncommon as you might imagine, or at least I imagined. for at least 70% of these people, bleating into an iphone is their preferred interaction, for which the pied piper of hand things is undoubtedly most pleased, but other smartphones are available. you know that. right? and with all these smartphone appendages dangling in front of me, I feel like I'm missing a trick if I don't get some kind of experience designing for those platforms.

now I'm one of those people doing the train, tube, hammersmith, broad street, bishopsgate, liverpool street, tesco thing, I thought I really should get some kind of proper phone which lets me monitor trades on an AMOLED screen or something. or at least doesn't hang for a full minute when I send a text. since I also have a tendency to avoid technology trends (meaning, usually, I can't afford to be an early adopter), I had, a long time ago, discounted an iphone. actually, I like iphones, but anything that requires me to use bloody itunes just doesn't make it onto any list I have. apart from the list of things I won't buy that I have. and, since I'm already a google person, I was already looking for a phone built around a mobile platform that integrates all my googlist activities which of course is the moble platform that google make. it was really just a question of handsets and platform versions. which, granted, isn't an insignificant consideration. suffice to say, after I'd bought a pile of 'what mobile' magazines the size of a small child and reviewed acres of adverts with the occasional technology blog in the middle, I'd determined that the HTC Desire with Android 2.1 was the very thing. which it is.

I really rather like Android. I really rather like HTC's Sense UI, although it really doesn't do an awful lot after you've worked out you don't need to flip between 7 home screens that often. and I really rather like the Desire, even though its a bit, well, brown. all three together, notwithstanding the usual caveats around battery life, seem to support an all-round user experience that suits the way I want and need to use my smartphone to do the things I bought it for. my most basic requirement was for excellent support for multiple email accounts that exist on multiple servers. I was also looking for excellent social network integration. I was also looking for excellent clocks. truth is, limited as the Android apps store is, there's just enough there to enhance the user experience by one or two degrees. mind you, the apps bundled in 2.1 and the google support built-in, means that I'm pretty well set up without needing to go anywhere near the app store. unless I want better clocks. for which there is probably an app. called 'better clocks'.

in a nutshell, which is kind of what my new phone reminds me of, first impressions of the Android user experience on the HTC Desire are very favourable. I've had a week to do the thing where you turn everything on and then turn everything off again. I've tried all combinations of widgets, programs and shortcuts. and turned them all off again. I been through every single setting screen and religiously observed the state and behavioural changes that occur as a result and determined whether I like those changes. I've settled on a default configuration for everything. I've installed the advanced task manager to kill everything I've left running, because, excellent as multitasking is and nice as it is to have updates and notifications going of all over the place all the time, is does rather reduce the usable uptime.

next step is to work out how I might begin to design and build something that runs on my own phone, just to go through the development process. with all that spare time I have. I'm writing this on the train you know. and my tea's gone cold.