Re:Best Practices for Form Design (2008) [pdf]
by dihydro on Monday August 15, 2022 @11:29AM
(#32470948)
One thing that should be standard by now is for addresses in the USA or other countries that have ZIP or Postal codes per municipality or area, the zip/postal should be entered first and auto fill the city if it is unique. There should be very few times where "USA, 20755" doesn't give the correct location.
[ Parent
| on HN ]
Re:Best Practices for Form Design (2008) [pdf]
by leejoramo on Monday August 15, 2022 @02:28PM
(#32473445)
This has always bothered me with web forms.
Back in 1992, I developed networked databases applications for macOS using Panorama. It included looking up city and state from ZIP codes. The only times I recall it getting the wrong info was in cases of recent city boundary changes.
Panorama still exists, it was so much better than Access or FileMaker.
Re:Best Practices for Form Design (2008) [pdf]
by jimmygrapes on Monday August 15, 2022 @02:54PM
(#32473724)
I just implemented the USPS APIs and they all require a street address in order to succeed, due to the need for disambiguation. What I really wanted was something like you describe, because I don't always have a street address so much as a general region. All the other API offerings are way too pricey for my purposes, or look scammy. I ended up scraping Wikipedia and making a generic spreadsheet instead.