Hi all, Designing a search component for a travel site that requires you to search. Can search by city/state, address, point of interest, airport . . . the usual stuff.
Some travel sites default to a searchbox defaulted to the fields for city. If the user wants to search by airport or by point of interest they have to select another mode or tab on the searchbox to get those fields. My contention is that people get a lot of error messages because they put in say a point of interest without seeing the mode tab (we know they get a lot of error messages at this step). T Some travel sites like hotels.com,Mobissimo have gone to a single searchbox that allows people to enter whatever they want supporting more 'google' like search query behavior. My contention is its better to allow people to enter whatever makes sense to them as long as the system can interpret it and return reasonable results. Anyone have any research or wisdom to support either case? Thanks! ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
