Responses are in line and I snipped a lot. On Jan 27, 2:54 pm, Peter Eastman <[email protected]> wrote: > On Jan 27, 3:40 am, Zero <[email protected]> wrote: > > yeah, flamewar time ! >I also believe we can all learn by looking > at the solutions other people have found to common problems. I don't > believe that more buttons or fewer buttons is inherently better, but I > do believe that designs can be rationally compared and, when one > design is objectively better than another one, we should use it.
I believe we all need to look at the iPad. Dissect it. Root it. Reverse Engineer it. Challenge the Apple p...@t3ntz. Risk pissing off Apple. > For example, is it better to have a physical Menu button, or to use an > on-screen Menu button? Physical button. The answer is almost always physical button, but you don't want more then 26+10+4+5+2+2 buttons where x is user preference. 26 letters, 10 numbers, the 4 Android buttons, an up, down, left, right and center button, a volume up, a volume down, an answer and a hangup button. I also like a period, an @ sign, a shift key, and a trackball myself. >Either one could be implemented well or > implemented badly, but Android's implementation is objectively > inferior to Apple's implementation in a very important way: users have > no way to know when a menu is available, and that significantly harms > the usability of Android devices. > Peter We are teaching users to always check the menu button. Some developers don't use it, but that is not a Framework or a User error, it is a Developer error. On Jan 26, 5:56 pm, Peter Eastman <[email protected]> wrote: > > If I instead press home and open my calendar then as you say, pressing back > > takes me to the home screen. > > As it should. That is consistent with the interpretation of Back as > "take me back to where I was before." Before opening the calendar you > were on the Home screen, so that is where Back should take you to. > > The example I gave was a different situation: you press Home, then > Back without opening any other application. In that case, it ought to > take you back to where you were when you pressed the Home button. > That is consistent with the idea of "take me back to where I was > before." But that isn't what it actually does. In fact, it doesn't > do anything at all. Home means clear the stack. Back should do nothing after you clear the stack. What does home mean to you? If you want similar functionality to Home without clearing the stack you can long press the home. On Android "Exit" is "hit back 7x". It should only take them back until the last time they hit Home. On Jan 27, 3:40 am, Zero <[email protected]> wrote: > yeah, flamewar time ! > <rant> > i couldn't disagree more. > a mouse with only one button is useless crap. > a phone with only one button is.... > </rant> A phone with only one button is crap. You need at least 2, 1 to answer and 1 to hangup. Do there already exist apps that let you use an Android device as a keyboard for a text editor, which is displayed on an iPhone screen? I'd like to use my iPad as a screen, and my Droid as my UI. I'm willing to slave a Windows PC in the middle if I have to. -Matt Kanninen -Mobile Developer -- 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.
