Earlier quoted context omitted.
Well, this list shows 293 ZIPs that cross state lines [0], this FAQ says there are ~43,000 ZIPs in use [1] so that puts it closer to 99.3%. But think about it, if you're taking an address to ship something, getting the ZIP right is what matters. If your package has 45201 on it, it doesn't matter if it says Cincinnati, OH or Cincinnati, KY. [0] http://web.archive.org/web/20110112211559/http://maps.huge.i... [1] http:/…
But if you're collecting a billing address (probably more common, since many places bill but don't ship, e.g., for digital goods, but not that many ship without billing), and are trying to expedite filling out the form by guessing the city and state from the zip, I doubt the payment processing would succeed if you got the city or state wrong. All depends on the situation, I guess.
Website mistakes that are easily fixed
31–40 of 70 posts
Re: Website mistakes that are easily fixed
#32I'm glad I'm not the only one who's anal about redirecting to the canonical host name. Now, let the bike-shedding begin: should the canonical host name be www.foo.com or foo.com?
Re: Website mistakes that are easily fixed
#33Re: Website mistakes that are easily fixed
#34> There can be a whole list of languages in the Accept-Language header, in the order the user prefers them! Use that data, it's there for you to use. Yet it takes only jumping a plane for a few hours to get Google to think I can and want to read Georgian. Google's i18n for anonymous users (I'm not logged in on my phone's browser) is the most ridiculous I've experienced, every border I cross I get a different language…
Re: Website mistakes that are easily fixed
#35godamn credit card forms! those get me the most because we're at the moment where i'm trying to give you money, and they pull some passive-aggressive bullshit like limiting the field length to 16 characters. i can almost type in my whole card number, but then i can go no further and i have to manually go back and remove all the spaces and then go to the end of the number and enter the last digit. class act.
Or worse: requiring the spaces. Or maybe they want dashes.
Re: Website mistakes that are easily fixed
#36I'm glad I'm not the only one who's anal about redirecting to the canonical host name. Now, let the bike-shedding begin: should the canonical host name be www.foo.com or foo.com?
www allows for the use of CNAMEs (which, as I understand it, is why the www convention was established in the first place).
Whether it was an A record or a CNAME record was generally at the adminstrators preference. CNAMEs had their own hiccups and weirdness to deal with, and still do to a lesser degree.
Re: Website mistakes that are easily fixed
#37Here's one he missed: your "country" dropdown has a list of every country in existence, alphabetically. So for the US you have to scroll down to near the end of the list past hundreds of other countries. Instead, put your audience up top (Canada, US, GB maybe) and then alphabetically list the rest.
Re: Website mistakes that are easily fixed
#38Slightly pedantic, but it's even easier than that if you don't have any elements separating them - you don't even need the id:
> Banana
This adds convenience on desktop, but it's really annoying not to have it on smaller mobile screens.
Re: Website mistakes that are easily fixed
#39Asking for city, state and zip code is my favorite on the list. Plus the country should be asked for first then if US only get the street and zip code. There was a link on HN sometime ago that showed that people trusted the form/page more when complete address information was requested (I believe the conclusion was that people were used to doing it that way) so maybe there is a downside to the shorter version.
Funny. This is the one to which I had the most negative response. Zipcodes are terrible for inferring anything geographically interesting. A single zipcode is just a collection of USPS postal routes; nothing more, nothing less. They don't have to be contained within a single city, or even a single state, nor do they have to be contiguous, and they can overlap with one another. New ones are also added all the time, an…
The form would look it up in a background ajax call. It wouldn't tell you this or block your actions. If it found a match in our DB, it would populate the city, country fields, not make a mess, and leave you free to edit the form if it was wrong. Your flow would be the same either way.
I think not interrupting the users flow was a big part of it.. it didn't make people go "What? How do I change that? What happened? That's not right".. you just kept filling it out like normal... with some fields pre-filled if you were lucky.
Re: Website mistakes that are easily fixed
#40https://github.com/gioele/rack-i18n_best_langs
It picks up clues from various HTTP pieces (headers, URI) and generates a list of locales in order of possible user preference. It is then up to the web application to make good use of this list of preferences.
It is alpha quality but I would love some criticism about it from HN readers.