Comments on: Hidden Functionality — Hints And Affordance http://justaddwater.dk/2007/05/03/hidden-functionality-hints-and-affordance/ Instant Usability & Web Standards Sat, 28 Jan 2012 13:44:35 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jesper Rønn-Jensen http://justaddwater.dk/2007/05/03/hidden-functionality-hints-and-affordance/comment-page-1/#comment-139946 Jesper Rønn-Jensen Thu, 03 May 2007 18:01:13 +0000 http://justaddwater.dk/2007/05/03/hidden-functionality-hints-and-affordance/#comment-139946 Great comment Michael. Good that you put focus on "true" affordance as opposed to "just" adding simple text. However, I think that "true" affordance has some challenges with respect to the most advanced Web2.0 widgets. A good example is autocomplete text fields that I describe tomorrow. The challenge: It is a text field, it looks like a text field, but it works much differently because of the added functionality (that you cannot see or does not show). So, in my point of view, "true" affordance for new web widgets will probably take some time and probably also require some explanatory texts before everybody learn :) Great comment Michael. Good that you put focus on “true” affordance as opposed to “just” adding simple text.

However, I think that “true” affordance has some challenges with respect to the most advanced Web2.0 widgets.

A good example is autocomplete text fields that I describe tomorrow. The challenge: It is a text field, it looks like a text field, but it works much differently because of the added functionality (that you cannot see or does not show).

So, in my point of view, “true” affordance for new web widgets will probably take some time and probably also require some explanatory texts before everybody learn :)

]]> By: Michael Zuschlag http://justaddwater.dk/2007/05/03/hidden-functionality-hints-and-affordance/comment-page-1/#comment-139859 Michael Zuschlag Thu, 03 May 2007 14:08:45 +0000 http://justaddwater.dk/2007/05/03/hidden-functionality-hints-and-affordance/#comment-139859 As your links indicate, the term “affordance” usually means communicating the function of the object by it’s physical or sensory design, not by tacking some explanatory text beside it. A label on a door saying “Push” is not an affordance. A horizontal bar to press on is. There is a place for brief explanatory text in sites and apps, but such text counteracts the main purpose of hiding functionality –to reduce clutter. True affordances avoid this problem. That said, it’s hard to make compelling affordances in the virtual world of software UI. How do you show the title bars are draggable? One way is to use a “grippy” texture like seen in Java Swing. How do you indicate that the drop down arrow list more menu items? It might help if there were two or three visible menu items, rather than just “Reply.” Seeing “Reply” “Forward” and then the drop down arrow at an equivalent visual level may suggest “more of same here” (assuming users know what the downward pointing triangle usually means). As your links indicate, the term “affordance” usually means communicating the function of the object by it’s physical or sensory design, not by tacking some explanatory text beside it. A label on a door saying “Push” is not an affordance. A horizontal bar to press on is. There is a place for brief explanatory text in sites and apps, but such text counteracts the main purpose of hiding functionality –to reduce clutter. True affordances avoid this problem. That said, it’s hard to make compelling affordances in the virtual world of software UI. How do you show the title bars are draggable? One way is to use a “grippy” texture like seen in Java Swing. How do you indicate that the drop down arrow list more menu items? It might help if there were two or three visible menu items, rather than just “Reply.” Seeing “Reply” “Forward” and then the drop down arrow at an equivalent visual level may suggest “more of same here” (assuming users know what the downward pointing triangle usually means).

]]>