Afforadance on Auto-Complete Input boxes
30 Jun 2006 - 2:39pm
2 replies
631 reads
Does anyone have any good affordance/scent on an auto complete input box
(as in google suggest http://www.google.com/webhp?hl=en&complete=1)
--
BLAKe
Comments
On 6/30/06, Blake Scarbrough wrote:
>
> Does anyone have any good affordance/scent on an auto complete input box
> (as in google suggest http://www.google.com/webhp?hl=en&complete=1)
>
>
Blake, I'd love to know the same. In my opinion, the autocomplete input
boxes have a very low discoverability because they're basically just text
fields with added JavaScript.
Google's interface has an added line of text trying to explain and to make
it easier to discover the _hidden_ functionality: "As you type, Google will
offer suggestions. Use the arrow keys to navigate the results. Learn
more<http://labs.google.com//intl/en/suggestfaq.html>
"
Is this enough? Hardly. I would like to see a general consensus around how
to visually indicate autocomplete fields in a way that makes it intuitively
clear what functionality is hidden in the field.
Back in January, I wrote about "live search" in user interfaces, with
examples from Google Suggest, GMail, Apple Spotlight, Windows Vista and
more. But neither of the ones I looked at had any visual indication of the
fields that could indicate that the field was different from an ordinary
text field.
Here are the two articles digging into "live search"/autocomplete:
http://justaddwater.dk/2006/01/26/live-search-explained/
http://justaddwater.dk/2006/01/25/windows-vista-setting-new-standards-for-find-as-you-type-searching/
Please let me know, if you discover anything else in this direction.
/Jesper
--
--
Jesper Rønn-Jensen
Capgemini Danmark A/S
+45 23 73 62 20 (Mobile)
www.capgemini.com (Website)
http://justaddwater.dk/ (weblog)
On 6/30/06, Blake Scarbrough wrote:
>
> Does anyone have any good affordance/scent on an auto complete input box
> (as in google suggest http://www.google.com/webhp?hl=en&complete=1)
>
What is the design problem you're coming up against?
My gut feel on this is that the affordance that announces auto-complete
functionality is the text box to type in. Once a person starts typing in a
text box with auto-complete, the auto-complete suggestions are displayed.
Is there a situation where you'd like your users to be able to differentiate
between text boxes with auto-complete and those without?
-Jose