On Sat, Jul 14, 2012 at 6:48 PM, Mark Murphy <[email protected]> wrote: > On Sat, Jul 14, 2012 at 12:34 PM, limtc <[email protected]> wrote: >>> That does not preclude having some sort of menu button in a corner. It >>> also does not preclude bringing up a menu based on some other trigger >>> (certain tap sequence in a corner, certain gesture, etc.). >> >> 1st option still take up space in canvas. > > Put it there anyway.
Mark, with all due respect, don't go this way. Don't succumb to the arrogance of thinking you can design limtc's app for him. I have experience with a broadly similar type of app as his. I can tell you you can't always stuff controls to the screen, just because someone somewhere at Google made an arbitrary decision to exclude off-screen controls. Sometimes on-screen controls get in the way, sometimes they break immersion, sometimes there is no good way left to bring them up if you hide them (this probably happens more often than you think) sometimes there are other reasons neither you nor I have ever thought of. There are work-arounds but they are just that - work-arounds. Bringing up UI is a fundamental concept, especially on mobile platforms where screens aren't big enough for keeping UI displayed all the time. It serves nobody if one app has an on-screen button to bring up UI, another does it via a shake and yet another uses an obscure gesture because it uses every other possible option for something else. The Menu button was a uniform way to do something that 90% of apps have or want to do. Now everybody has been left to their own devices. As I haven't ever heard pretty much *any* reason for that, good or bad, I tend to think dumping it was rather a boneheaded idea. > Your solution is unsuitable for production apps. It may not work > reliably today. It will not work reliably in the future. The final call on this hasn't been done for us yet, but I'm telling you - if need be, I'd rather have an app that works (and sells) great for a year on a current Android version and possibly deteriorates afterwards, than something that's clumsy and counterintuitive from the get-go but can keep up its clumsiness unchanged to Android 38.3 or whatever the current version will be in 2035. I'd hate to have this decision pushed onto me but that's what I'd prefer in that case. -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
