少即是多 - 自动邮政编码？
您有一个国际网站，其中有一个表格，人们可以在其中填写他们的地址。
如果人们需要少填写一个字段不是很好吗？示例：
- 每天有 100 名访问者使用该表单
- 他们在邮政编码字段上花费 5 秒
因此 5 * 100 * 365 = 182500 秒或每年 50 小时。这只是一个网站上的一种表格。将其乘以所有询问此类信息的网站，您就可以看到我们通过重新设计可以节省的时间。
您可以通过地理位置 + 地理编码获取某人的邮政编码。但由于一个人当前的位置很容易与一个人居住的城市不同，所以这实际上并不有用。
解决方案是根据地理定位（但可变）国家/地区、输入城市和输入街道获取邮政编码。
我们可以使用的 API：http://code.google.com/ intl/nl/apis/maps/documentation/geocoding/ 或 http://developer.yahoo .com/geo/placefinder/。
现在真正的问题是，会出现哪些问题（国际化、本地化、准确性等）？
You have an international website with a form where people fill in their address.
Wouldn't it be great if people need to fill out one field less? Example:
- 100 visitors use the form each day
- They spend 5 seconds on the ZIP code field
So 5 * 100 * 365 = 182500 seconds or 50 hours a year. And that's just for one form on one website. Multiply that by all websites that ask such information and you can see the time we can save by redesigning this.
You can get someone's ZIP code via geolocation + geocoding. But since a person's current position can easily differ from the city a person lives in, this isn't really usable.
A solution would be to get the ZIP code based on a geolocated (but changeable) country, input city and input street.
The API we could use: http://code.google.com/intl/nl/apis/maps/documentation/geocoding/ or http://developer.yahoo.com/geo/placefinder/.
Now the real question is, which problems would arise (internationalization, localization, accuracy, etc.)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
没有人回答这个问题，所以我来试试。
不，如果网站根据其他信息填写邮政编码字段，那就不太好了。它可能对某些人有用。对于足够多的人来说，这肯定会失败，您必须提供邮政编码字段作为覆盖。现在，您的网站比具有传统邮政编码字段的网站具有更高的复杂性和开发成本，因为您必须同时测试自动邮政编码猜测器和传统字段。
由于人们对这两种选择感到困惑并且不知道该选择哪一个，因此您的可用性会受到影响。
您将付出机会成本，因为将设计和开发资源花费在邮政编码猜测器上，而不是花费在其他一些可产生更大可用性优势的功能上。
以下是我预见会出现的一些问题：
在采用这样的功能之前，我会采取两个步骤：
对现有数据进行测试。无论您考虑使用哪种方法来猜测邮政编码，请在现有客户数据上进行尝试，看看是否可以准确地重现客户输入的邮政编码。这将使您了解错误率。您能接受这样的错误率吗？
如果您真正的问题是，有人可以证实我的感觉，即这是一个迷人的功能，那么我可能还没有给您您想要的答案。但你问：“会出现什么问题？”
No-one else has answered this, so I'll have a go.
No, it wouldn't be great if the website filled in the zip code field based on other information. It might work for some people. It would certainly fail for enough people that you'd have to offer a zip code field as an override. Now you have a site with a higher complexity and development cost than one with a conventional zip code field, because you have to test both the automatic zip code guesser and the conventional field.
You'll have a usability hit which comes from people being confused by the two alternatives and not knowing which to choose.
You'll pay an opportunity cost, by spending design and development resources on the zip code guesser, instead of on some other feature which yields a larger usability benefit.
Here are some problems I foresee arising:
Before taking on a feature like this, I'd take two steps:
User research. Can you identify users for whom the time taken to enter a zip code is a pain point? What about the one of the top three pain points? I'll bet this issue isn't even on your users radar.
Test on existing data. For whatever method you are thinking about using to guess zip code, try it on existing customer data, and see if you can accurately reproduce the zip code the customer entered. This will give you an idea of your error rate. Can you live with this error rate?
If your real question is, could someone please validate my feeling that this is a charming feature, then I probably haven't given you the answer you seek. But you asked, "what problems would arise?"