Bugzilla Bug 591 - dialing from contacts needs to be
pauric at pauric.net
Mon Jul 16 14:56:57 CEST 2007
Thats a very good point Emre. One thing to note when looking at the
iPhone is it is heavily dependent on syncing with itunes. This pushes
the user towards filling out their contacts list. Note in the video
http://www.youtube.com/watch?v=yfrHoAPQvZc that the dialing keypad is
buried within the address book.
When I played with the iPhone I dont think I saw an easy way to simply
initiate a call with a keypad.
Some things I've observed in mobile phone usage. (nokia & moto)
1)The address book is a pain in the ass
1.1) Therefore is easier to remember your friends number than it is to
pull it from the address book
2)The 10 most recently dialed numbers is like an address book
2.1) Most recently dialed is also similar to a 'favourites' (analogy -
I think we can leverage a lot of the research Apple has done in their
design, BUT! there is a huge amount of room for simplicity.
So, back to you excellent point.... we need to think of a design that
gives the user no more than 2 clicks to
Is this a good idea for everyone?
If yes, how do we present this four button splash screen (along with
the other apps on the phone)?
Does anyone have any idea when the developer phones start shipping? I
placed an order but have not been charged or received an email
thanks all - pauric
On 7/14/07, Emre Turkay <emreturkay at gmail.com> wrote:
> What about two different redundant applications. There is a need for
> an address book application anyway. Select a person, see info, send
> sms, send mail, dial options. Allows to edit various information, etc.
> The second application would be only a dialer-lookup, which is only
> used to dial someone. Go find a person, tap it and it dials. Launching
> this application should be as simple as possible (a physical button or
> a finger gesture), after all this is a phone and it seems to me like a
> good idea to emphasize it.
> On 7/13/07, pauric <pauric at pauric.net> wrote:
> > I should also point out, in my experience, its worth deciding on these
> > fundamental interactions early in the design. Known as a 'style
> > guide'. Having a common method of interacting with all the
> > application will - greatly- aid the user experience. Its needs to be
> > as simple as it needs to be to perform the most common user tasks, not
> > more simple, not more complex.
> > Something like, in all applications:
> > tap-hold performs the primary action on an element.
> > tap-release brings up a menu with 'secondary' options.
> > Forgive me, I have not been through all the screens/application yet.
> > I would be interested in hearing about applications that will have a
> > problem with this basic, common, interaction method
> > thanks for helping me get up to speed.
> > kind regards - pauric
More information about the openmoko-apps