I have read The Design of Everyday Things. A usability problem with a slide projector in the first chapter turned out to be . .. a long click problem. Short click to advance, long click to retreat, but no way to know that without consulting a manual that was probably long gone.
I do have Long Click, in places that seem very appropriate. But I am moving away from it completely, hopefully by next week because no one will think to use it with seeing some instructions, or (more likely) emailing me to ask how you do something. And if they have to read instructions, I have to admit my design is poor according to Tim. In fact, many don't know how to get to the regular menu. Their previous phones probably all had the menu button. I finally realized this with a user after a long exchange and had to send him a picture of where the menu button is. You notice that Android is moving away form both context menus and offscreen menus in Honeycomb. Doesn't help the much larger population on smartphones yet. I'll acknowledge that needing instructions is a sign of poor design. And I'll acknowledge that my design is poor and I will need to provide some help for people to ignore until I perfect my design. But even when/if my design is perfect, it would seem I would still need help to give people for the nuances of their Android device. I've made the mistake of not updating docs because I think my new, better interface is just around the corner. And BTW, Linux Box Solutions is just "linkbuilding". Don't expect meaningful contributions to this discussion. Nathan -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
