Live data from Hacker News

Redesigning the country selector

baymard.com

41–50 of 136 posts

Re: Redesigning the country selector

#45
post #6

On a similar note, I've always found it kind of amusing/frustrating that forms in the US make you fill out city, state, and zip code, when in fact the zip code indicates a specific city and state. I realize that's a huge database of geolocation data to keep as part of the program, but I wonder if there could be some kind of lookup that goes on behind the scenes and fills in the city and state if the response is quick…

The Apple Online Store does this - you put in your street address and zip code, and it calculates the city and state.

Re: Redesigning the country selector

#46

this is hardly something brand new, this looks bettter and works just as well : http://harvesthq.github.com/chosen/ I'm sorry but progressive enhancement of a select tag into an autocomplete element isn't quite news worthy.

Does chosen have an equivalent to what this selector does with data-alternative-spellings?

Re: Redesigning the country selector

#47
post #25

Could you retrieve the country from the IP address to set the default?

Ta-da-m! This is the first question any usability/UI/whatever designer should ask: "Can software do this for users automatically?". Only then the designer should think of the visual appearence and interaction.

Re: Redesigning the country selector

#48

My main complaint about old country pickers and this one is non-prioritization of countries in the list. Yes, I understand that this may be a sensitive issue, but how much likely your customer is going to be from Canada than from Cameroon. Or if I start typing 'CA' in this selector, I get American Samoa and Antarctica before Canada! Let alone my old acquaintances Cambodia and Cameroon. Same for Russia - you get Aruba…

Population/GDP would be a good starting point, then it'd be nice to adjust weighting automatically over time based on where the site's visitors are coming from (geolocation and previous choices).

Re: Redesigning the country selector

#50
post #29

I have to ask. Is it common for anyone to type their country starting with characters inside of the word? I.e. instead of typing "can" for canada, would you type "ada" or something similarly fuzzy? I personally type "can", and if Canada is not the first result I consider it's usability inferior to a standard drop-down.

It may not be common, but I don't think it is an unreasonable thing to expect. Think of a country such as the Democratic Republic of Congo -- I'm not entirely certain, but I'd imagine it is common for someone to simply start typing "Congo" while still expecting the result to be available. This example may not be ideal since this country selection has both "Congo" and "Congo, Democratic Republic of" in its data set, b…

I think the parent was more interested in whether someone would use a string of letters within a word in the name, as opposed to just starting a word somewhere in the name.

That is to say in your example, the parent wasn't questioning whether the code should support 'Congo', but whether it should support 'ong', for example.

Post reply on HN