Dialer UI Design
hiretto at gmail.com
Mon Sep 29 13:33:34 CEST 2008
> Hey all,
> I'm just sending this out there for anyone working on a/the dialer UI.
> At the moment with the qtopia (ergo, 2008.*) dialer the same part of
> the screen is used for "answer call" as "end call", and since the UI
> is laggy (see below), I naturally hit answer call a second time and as
> a result hung up immediately. Probably should avoid this UI design
> pitfall in future dialer (and other) interfaces.
> A note on UI response times: 10ms should be the MAX response time,
> anything that takes longer has just 10ms to let the user know it's
> going to take longer (progress bar, hour glass, etc), otherwise the
> reaction is disconnected from the action that caused it in the user's
> mind and worse, the user will press the control again.
> On the day *I* go to work for Microsoft, faint oinking sounds will be
> heard from far overhead, the moon will not merely turn blue but
> develop polkadots, and hell will freeze over so solid the brimstone
> will go superconductive.
> -- Erik Raymond, 2005
> Please avoid sending me Word or PowerPoint attachments.
> See http://www.gnu.org/philosophy/no-word-attachments.html
> Openmoko community mailing list
> community at lists.openmoko.org
Qtopia sux, it's ugly and not pratical.
We need absolutely the FSO with dialer, sms and contacts ( instead of zhone
) or SHR.
View this message in context: http://n2.nabble.com/Dialer-UI-Design-tp1125436p1125600.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
More information about the community