“The single most important concept to master when designing mobile device interfaces is “context”. The context in which an application is used and the context of how information is input are both key issues; each must be understood before a well crafted design may be implemented. When these two notions of context are explored, it becomes clear that designing for a mobile device can lead to a solution that is worlds different than its desktop equivalent.”
Link: Challenges of Interface Design for Mobile Devices (yuiblog.com)
Comments 2
Input seems to be very sluggish for most mobile devices. In my field of work, like most there is a immense amount of Jargon that is job specific. I find that entering raw data/text/jargon on mobile devices is not worth my time. I either call in response to e-mails if I am out of the office, or wait until I can sit at my PC and type at full speed. I have a patent pending on a hardware software combination that may or may not be a solution to the speed problem on mobile devices. I am currently in the “What do I do next” phase, as well as the “who else is working on this problem, and can we team up” phase. Is there anyone else out there that is attacking this problem right now?
Posted 15 Sep 2008 at 12:14 pm ¶-John
John – I agree. There are solutions out there that try new things (as your design does), especially things like ShapeWriter from IBM. The problem is that people are so familiar with the QWERTY keyboard – it’s even hard to get people to learn T9. But if a new global standard can be created, it would be great.
Posted 16 Sep 2008 at 1:59 pm ¶Trackbacks & Pingbacks 1
[...] a Small Surfaces, descubro en Yahoo! Users Interface Blog un artículo sobre los principales retos en el diseño de [...]
Post a Comment