Live data from Hacker News

Redesigning the country selector

baymard.com

51–60 of 136 posts

Re: Redesigning the country selector

#51
Throwing an autocomplete at something is NOT always an upgrade. I've spent quite a bit of time thinking about country selectors, and I'll present my solution for two separate use cases here.

In the first case, a country selector allows a user to select a country as a component of their shipping address, a user profile, etc. The input method described in the aforementioned article suits that case decently; however, it's not immediately intuitive that a user can access some of its touted conveniences (such as the selection of a country by its short name), and in most cases, a user will not frequently return to the same country input field (i.e. they'll set up a saved shipping address ONCE, or set their home country on a social profile ONCE) which removes the possible avenue of training the user to expect the pattern.

In this case, the best possible user experience can be given by leveraging geo-location (either by using the JS API, or any of the myriad IP-based solutions) and making intelligent suggestions to the user. For example: If I'm a user, and I am required to enter my shipping information (including country) on a checkout page, the page's best GUESS as to where I am should be displayed first, and the user should be allowed to change that assumption quickly. For example, you might show the user a drop-down box with the page's best guess selected by the default, surrounded by nearby countries (depending upon geo-location accuracy). Secondly, flag icons actually have quite a bit of value -- many people think visually, first, and will be looking for their flag's colors. Even if the icons are minuscule, they're still incredibly helpful.

The second use case which I want to present is that in which a company (such as Range Rover) presents a page allowing you to select which localized version of their site you wish to visit. In Range Rover's case, this is a massive list of countries, with their respective flags. Let's be honest: part of the reason this page exists for most companies is because they wish to demonstrate how significant their global reach is, or the expenditure required to translate the site. On Range Rover's site, the US (my homeland) is buried deep on the bottom left-hand side -- to make this more usable, they could leverage the same geo-location technique discussed above, and simply provide visual differentiation between my home country, and the other countries! Everyone's goals are achieved here; usability is increased, the "global" feeling is imparted, and the business douches who insisted upon a massive list of countries in the first place are sated!

The guys who wrote this article don't understand what's possible with current technology, and therefore cannot successfully design for it.

Re: Redesigning the country selector

#52
post #23

While this has a nice UI, it suffers from a ranking system that fails to weight prefixes correctly. For those of us in Canada, typing "ca" should probably rank countries that start with the "ca" prefix first, followed by countries that have a word that starts with "ca", finally followed by countries that just happen to contain "ca". I don't see much use in showing "United States" as the first match for a user who has…

indeed, still doesn't beat typing 'c' 3 times.

I actually laughed at this. It's a total Canandian "in joke"

Re: Redesigning the country selector

#55
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 agree. Let me put it a little differently. I think that the order of the letters and how soon they appear in the list of potentials should impact the ranking of the results.

Basically it should work like Command-T in Textmate (or the vim plugin based off of it). So if there's a Congo and a Republic of Congo in your potentials, then typing "con" should list Congo first as being a more likely result (even though in this case it may not be).

In this demo, when I type "ca" the first three results are "United States, American Samoa, and Antartica". I would argue that this is less intuitive to the user than a simple alphabetical dropdown.

Re: Redesigning the country selector

#56
you have to keep user experience in mind...everyone is used to scrolling down to find the country...if you throw this in, half your users will get frustrated not knowing what to do.

on the technical side, it should just match the starting letters, instead of all letters in the name

Re: Redesigning the country selector

#57
post #30

While this has a nice UI, it suffers from a ranking system that fails to weight prefixes correctly. For those of us in Canada, typing "ca" should probably rank countries that start with the "ca" prefix first, followed by countries that have a word that starts with "ca", finally followed by countries that just happen to contain "ca". I don't see much use in showing "United States" as the first match for a user who has…

Perhaps adding a geo-ip look up to help weight the results would make this better? None the less this is a huge improvement then a drop-down with every known country.

I've always wondered why more sites don't do this. Even without the fancy auto-complete, just set the default country using a geo-ip lookup.

Re: Redesigning the country selector

#58

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.

Exactly my thought. Chosen has the advantage of working moo tools, jquery or prototype. There's also a drupal plugin. It doesn't have alternate spellings support, but that should be really simple to add.

Re: Redesigning the country selector

#59
post #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?

no, but again, that wouldn't be that hard to add.
Post reply on HN