On 1/23/08, squall <dlinder at kth.se> wrote:
> I'm currently starting a master's thesis work on a experimental GUI model for
> mobile phones,
> What programming language would be most convenient? The GUI is supposed to
> offer icon based navigation (very traditional mobile style like SE or
> Symbian Nokia), but no other applications (ie "dead ends" on UI nodes).
You are going to test on an actual device? If possible, you should -
interaction will be different when people have the device in their
hands as opposed to on a computer. Also, are you making any changes or
assumptions regarding the input mechanisms?
Assuming that as a student you have a very limited time and money
budget and hence want to test on a device but aren't making physical
changes to the device, what I recommend is finding a device that meets
your needs (touch screen? 4 way rocker?), then find a language to fit.
Flash Lite is nice but very limited: it's a small sandbox on the
device. If this is what you need, and you know a little Flash already,
then go for it. Python is supposed to be pretty easy. Also consider
the Neo1973 http://openmoko.org/ - designed for hackability.
> How do I decide the relevant user "types", or Personas (perhaps around five
> would be good)? I imagine there would be some studies on this already,
> preferrably for mobile phones directly or otherwise for computer users
> (hopefully somewhat similar).
Um. What market would your new UI be aimed at? Just to give you an
idea of implications, Nokia recently published personas for emerging
barbara at littlespringsdesign.com 1-785-838-3003
Barbara Ballard wrote:
> You are going to test on an actual device? If possible, you should -
> interaction will be different when people have the device in their
> hands as opposed to on a computer. Also, are you making any changes or
> assumptions regarding the input mechanisms?
Yes, currenty the idea is to test on the actual phone. On the other hand an
advantage with a simulation on a computer would be that I could conduct
tests via web (tracking user results) without me actually having to be there
in person - thus increasing the number of tests I could conduct. But, like
you, I'm worried that this would affect test results, especially for
inexperienced users. Input mechanisms are not considered in this thesis, it
only covers the GUI model.
> Flash Lite is nice but very limited: it's a small sandbox on the
> device. If this is what you need, and you know a little Flash already,
> then go for it. Python is supposed to be pretty easy. Also consider
> the Neo1973 http://openmoko.org/ - designed for hackability.
Basically, my needs are very small: just simple navigation in the GUI i
build, and tracking of the user "movement" to see possible dead ends or
misunderstandings. No other applications are to be coded.
> Um. What market would your new UI be aimed at? Just to give you an
> idea of implications, Nokia recently published personas for emerging
> markets: http://www.nokia.com/press/entrylaunch
The GUI would be aimed at a western, mature market (like western europe or
USA). Without going into much unnecessary details, I'm to develop a
user-adaptable GUI that's easy to use for the technically uninterested - but
still offers all the options for the more advanced. Because of this, I'm
looking to create personas (or maybe some sort of user groups) with a wide
range of different technical background. For example: an old grandmother who
only wants to call and reply, a nine year old kid who likes music and games,
a teenage computer fan etc.
View this message in context: http://www.nabble.com/Master%27s-thesis%3A-Mobile-phone-GUI-model-tp15039118p15045579.html
Sent from the ixda.org - discussion list mailing list archive at Nabble.com.
You might want to check out the book Mobile Interaction Design.
As far as personas go, all I can say is it depends. Who are your
users? What is the context. Start there. You have to understand who
your users are before you can start creating personas.
I know there is an extensive thread on personas if you look around
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org