On Jan 31, 8:44 pm, Michael Pujos <[email protected]> wrote: > On 31/01/2012 21:28, Brian Conrad wrote: > > > From my experience I wish I had just used valuable screen real estate > > to begin with and put Menu, Settings, Help on the screen. Almost the > > number one support question I get is about settings because users > > don't know that the Menu button can also be used for apps not just > > phone settings. So what do you think of this blog article about the > > Menu button going away? > >http://android-developers.blogspot.com/2012/01/say-goodbye-to-menu-bu... > > As much as I understand the purpose of the article, my feeling is anger > for constantly changing core UI paradigms. > What is cool today will suck and will be deprecated tomorrow. Some day, > overflown menu will suck too.
My thoughts reading the article were a mishmash of - Why is this article happening now? Couldn't/shouldn't it have happened a year ago - What is wrong with calling it a menu. Sure there is overflow but that happened with the old menu system too - Why do I feel so confused by the article? Shouldn't this be easy peasy. - I should really get around to removing long click from my app. However many people have trouble with the concept of the menu button I'm sure more do with long click. - Do Honeycomb/ICS apps like Gmail and Maps update via the Market now or only via OS updates? -- 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.
