?Huh? You're saying my menu option should be BLANK except for the checkbox if not locked???
I'm sure I'm misreading you. I do get your point about "present the state on the screen and the actions in the context". That's a nice statement of the argument for presenting the menu as a verb. And I'm inclined to agree. It just feels like going against the platform, and I'd like to understand why and when it's appropriate. I do value consistency in UI. On Feb 26, 2:16 pm, "Nick Owens" <[email protected]> wrote: > Bob: > > The text next to the option should say "Locked" if locked and nothing if > otherwise. A long-click should bring up the appropriate option for "Lock" > or "Unlock", depending on the current state. Only one options needs to be > presented. Present the state on the screen and the actions in the context - > in my experience, that has the most consistency across all software. > > I think you're too deep into the analysis on this one and need to take a > step back - sometimes that happens when we stare at something too long. > > Thanks, > Nick Owens > VP, ThreeClix > Office: (904) 429-7039 > Mobile: (847) 565-9392 > After Hours: (904) 540-5830 > > > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of Bob Kerns > Sent: Friday, February 26, 2010 5:11 PM > To: Android Developers > Subject: [android-developers] Usability: State vs Verb > > My business partner and I have a small disagreement, and I'm trying to > figure out the best way to resolve it. > > First, I should say I started out his way, and switched after > reviewing a lot of applications. > > The background is this -- we have an app, with some controls which can > be locked. A lock/unlock icon is put next to the lockable controls. > You can long-click the icon, and it brings up a context menu with > several items, including the item for the lock state. > > Currently, it brings up a "Locked [X]" or "Locked [ ]" item -- that > is, a menu item with a checkbox that can be checked or unchecked, and > the lock state is changed accordingly. > > He would like me to change it to reflect the action being taken. I.e. > the menu item would say "Lock" if it is currently unlocked, and > "Unlock" if it is currently locked. > > It would be acting as a toggle in either case; the only difference is > how it is presented to the user. > > I see arguments both ways: > > * Consistency with platform standards suggests the checkbox. > * This feels more active than the usual "change the state of a > preference flag". > > Locking has implications beyond this application -- and is a major > motivation for the application, in fact. > > Note that both he and I independently thought at first glance it > should be 'Lock/Unlock'. I need to weigh this apparent intuition > against platform-wide practice and user expectations. > > Does anyone have any thoughts or opinions? Or alternatives I perhaps > haven't considered? > > Thanks. > > -- > 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 > athttp://groups.google.com/group/android-developers?hl=en -- 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
