4 ms·

Here's the Google spec for this: http://www.google.co.uk/design/spec/components/menus.html#menus-usage http://www.google.co.uk/design/spec/components/menus.htm

Here's the Google spec for this: http://www.google.co.uk/design/spec/components/menus.html#menus-usage http://www.google.co.uk/design/spec/components/menus.html#me... If you look at the menu with "All", "Family", "Friends", "Coworkers", initially it shows "All" and the arrow is immediately to the right of the text. I expect that if you select "Coworkers" then the arrow moves.

clay_to_n 12y ago
Yeah, I think standalone it should have the arrow right at the end. When the dropdown is used in a form, it should have an underline, like so from the Material spec: http://material-design.storage.googleapis.com/publish/v_1/quantumexternal/0Bx4BSt6jniD7MHBnQlFGeFRtYTQ/components_menus_usage5.png http://material-design.storage.googleapis.com/publish/v_1/qu...
- calinet6 12y ago
  Yeah, let's not consider every copycat that comes along a valid and complete implementation of good UI guidelines... This one surely is not.
  - xg15 12y ago
    The problem is that many people will use those copycats as the basis for their own app designs. Not everyone is willing to really understand the reasoning behind the design spec down to such minute details as an arrow placement if he can be hip and trendy with something that superficially looks like the same design. If a design is so easily misunderstood with such (comparably) large consequences for the user, that's a flaw in the original spec IMO.
    - calinet6 12y ago
      I don't believe it's easily misunderstood; I think people just don't know how or why to create a quality implementation based on an original. The spec is actually remarkable in the level of depth it goes to teach you not only about the design guidelines themselves, but also the reasoning and psychology behind it. Really, it's probably the best full on UX specification ever produced (and I'm not saying that lightly). It just shows that it's very difficult to get this stuff right. There's still going to be a bell curve, with most implementations and copies ending up in the mediocre middle, but overall, the guidelines might bring the quality of the overall market up. That's all we can hope.

clay_to_n 12y ago

Yeah, I think standalone it should have the arrow right at the end. When the dropdown is used in a form, it should have an underline, like so from the Material spec: http://material-design.storage.googleapis.com/publish/v_1/quantumexternal/0Bx4BSt6jniD7MHBnQlFGeFRtYTQ/components_menus_usage5.png http://material-design.storage.googleapis.com/publish/v_1/qu...

calinet6 12y ago
Yeah, let's not consider every copycat that comes along a valid and complete implementation of good UI guidelines... This one surely is not.
- xg15 12y ago
  The problem is that many people will use those copycats as the basis for their own app designs. Not everyone is willing to really understand the reasoning behind the design spec down to such minute details as an arrow placement if he can be hip and trendy with something that superficially looks like the same design. If a design is so easily misunderstood with such (comparably) large consequences for the user, that's a flaw in the original spec IMO.
  - calinet6 12y ago
    I don't believe it's easily misunderstood; I think people just don't know how or why to create a quality implementation based on an original. The spec is actually remarkable in the level of depth it goes to teach you not only about the design guidelines themselves, but also the reasoning and psychology behind it. Really, it's probably the best full on UX specification ever produced (and I'm not saying that lightly). It just shows that it's very difficult to get this stuff right. There's still going to be a bell curve, with most implementations and copies ending up in the mediocre middle, but overall, the guidelines might bring the quality of the overall market up. That's all we can hope.