▲ | dfxm12 3 days ago | |||||||||||||||||||||||||||||||||||||
I have a pet peeve for having to enter my zip code after I've already had to type in the city and state. What else would you expect? Typing my zip is way easier than going through a list of zipcodes in a dropdown, many of which will be off by one digit in different spots. (ETA: I reread your comment and see what you are expecting) I like the experience of autocomplete while I'm typing out my street address. | ||||||||||||||||||||||||||||||||||||||
▲ | boilerupnc 3 days ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||
I think the sentiment for the pet peeve is commentary on the perceived inefficient sequence of the data input and a hope for reducing the number of fields entered from 3 to 1. >I have a pet peeve for having to enter my zip code AFTER I've already had to type in the city and state. The city and state can be derived from the zipcode - so why not simply ask for the zipcode to be typed and then auto-populate the associated city and state. | ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||
▲ | pseudosavant 3 days ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||
I like the autocomplete too. Probably the best pattern, but it does usually do that by leveraging paid Google Maps APIs I believe. I was frustrated that this seemingly open data wasn't openly available. Anything that asks for city+state+zipcode can ask for zip code first, auto populate the rest. For the edge cases where the city is wrong, the person can still type in the city like they would have needed to anyway. It is worth noting that a package would never get delivered to the wrong place because the city wasn't correct but the ZIP code was. The USPS routes based on ZIP codes, not city/state. |