Tag Info

Hot answers tagged

35

As a Stack Overflow / Stack Exchange employee, my guess is that this was a Google Forms doc put together for the specific purpose of gathering addresses this one time. We do this internally a lot to gather information. Using a product like Google Forms allows anyone to get something done without having to involve developers or designers. I imagine the ...


18

Though I don't have an answer behind why all the fields were named the same, I think the idea was to ensure that all potential international addresses could fit into the form design without designing custom forms for every international address. Here are some examples of international addresses Amazon also a generic international format as mentioned in ...


15

TL;DR: Use a single text field, store as a single string, show an address label preview. Separate fields have served limited purpose, such as safely identifying the country, town or zip code area someone lives in. They also allowed to enforce some constraints, such as providing a fixed list of countries. They also - in theory - allowed to "reduce the ...


14

6-line addresses (or rather 7-line, including the name of the addressee) do occur. Consider for example a typical UK residential address: Miss S Pollard name 1 Chapel Hill building number and street name Heswall locality BOURNEMOUTH town with a post office BH1 1AA postcode UNITED KINGDOM ...


9

The two fields are part of the same address. (I've never heard your colleague's interpretation before.) Usually the second line is optional. As noted by dnbrv and TJH, in some locations the second line is necessary or helpful. In addition, providing the extra line allows for formatting an address to optimize postal delivery, which is largely driven by ...


7

Ultimately, it's a trade-off: Method A has the advantage of being concise, but Method B has the advantage of being consistent. (I'm the UX guy at SmartyStreets where we deal with addresses a lot.) I like Method B better, and here's why: The address is displayed in a familiar format that the user can quickly scan for correctness. The user does not have to ...


7

This is an interesting question. Thanks for asking. I had the exact same idea last year, and after some research and even an A/B test, I chose to stick with the field-set approach. This is based on my own experience with an online shop that actually ships fashion items. So this is about shipping address; not the billing address. Users who place online ...


6

You mention that other fields are validated but not the region field, that your primary motivation is for mailing addresses. If this helps you at all, only one of those countries you mention in your list of examples (USA) uses the region name in the mailing address. I took an entirely unscientific examination of a random set of industrialised or ...


6

The fact that Option B forces the user to review the address is a feature, not a bug. Getting the address wrong is usually quite costly to both the user and the website owner--something is going to get shipped the wrong place, mail will not get received, or at least a credit card will be denied. Hence it is important that the user checks that the address ...


6

Just use a standard text field. Entering a postcode is not as hard as it may seem. You can use regex for whitespace separation and auto numeric and character switching. i.e. force the mobile keypad to switch between numbers and characters when postcode is typed since you know what pattern it could be. Auto-suggestion would be the best option here. Canadian ...


5

I would argue that a good number of people think of the two-letter abbreviation when they think of their state(s). A form that accounts for both short and long-form manual input and a traditional drop-down list would be ideal in my mind. I'm imagining something like a standard text field that validates on either the abbreviation or the full name, and if ...


4

The last option, using a single field for type and street is likely the best. That said, let's go through the three options and see where the strengths/weaknesses of each are: The "street" field starts focused; if the user selects something in the drop down then the "street number" is focused ("type" is autofilled); if he tries to move to the next ...


4

In the U.S., a few years ago when social media was starting to boom, advertisers would often display a logo and state something like "Find us on Facebook" in TV and print media. However they started to realize that fan pages and other non-official profiles made that confusing, so then they started displaying full URL's (i.e., www.facebook.com/CoolCompany) ...


4

(I work at SmartyStreets, where we research and experiment with address-related UX.) Country should go first. Then you can customize the appearance of the form, if you wish, for certain countries, so that users will feel more comfortable entering their address. However, going entirely backward from the broadest region type to most narrow isn't the best ...


4

Try to re-design your form. Form description is too verbose and non-prominent. Header Shipping address is clear and easy for perception. Shipping Address and Mailing address is a bit confusing. Use Address label and placeholder in the field. Narrow address field is perceived as small info container, like email. The real postal addresses are more wider. ...


4

It's common in Europe (I'm in UK) too, but usually as an optional field. To give an example of a UK address which requires 2 lines: Apartment 10, Derp House (line 1) 20 Derpstreet (line 2) Derpville (Town) Derptown (City/County) D3 3RP (Postcode) I don't know enough about US addressed but my Canadian address also needed the extra line as I lived in a ...


4

For the address itself, there should be 4 lines as explained on the clear addressing guidelines on the official Royal Mail website (I say for the address itself because there is 4 + 1 line for the addressee's name). EDIT : Some people have pointed out to me that you sometimes need to indicate the house name before the street name, so 5 lines instead of 4 ...


4

It should not. The user counts on you that you do not change his input behind his back. As the user continue to the next field, his focus is now on that only field. Though the fields may be visually close to each other, he might not pay attention that you've changed his previous input. Not to mention that you got it right saying it might annoy him even if ...


4

From a UX standpoint, the most important question is whether the user's presaved "auto-fill" will fill in your form. You really need to check whether your single text area will work with such features. If it won't, you've potentially lost a user/customer/petition-signer/whatever. Especially with the prevalence of phone/tablet based users, entering an address ...


4

Keep it for business addresses In business contexts it is often used for 'Attn:' lines or department names. In large metro areas, it is also commonly used for building ID, eg 'West Tower'. You could mask it until business address is checked. Unfortunately, people don't always catch that requirement. In the end, you have to ask yourself what's more likely ...


4

Two address lines are necessary. A common use for the second line is to bring attention to a specific location or sub-address within a large business park or manufacturing facility. It is also commonly used when shipping internationally and the address is very lengthy. Example #1 (Attention to location inside shipyard): Block X, Office Number 0-12, 2nd ...


4

IP is, though, a good start. Using HTML5's location abilities is a good idea. What you are considering is something many sites have already figured out. I'd start by seeing what the other's already do. Look at large retailers with web sites that offer in-store pickup. Home Depot, Target, Walmart, etc. Ideally, you let people search everything and only ...


4

Could this confuse the user ? Will he start looking for other places on this map ? Expect him to look for other places, but he will also likely be expecting not to find them. Usually this means he'll zoom out/drag a bit and then having done so, either get out of the map or stop looking altogether. Try provide an easy way to 'get back to where the ...


3

Use a text box, then validate the input. I'm a developer at SmartyStreets, where we deal with this issue a lot. Dropdowns are notorious for slowing down users because they're hard to navigate with the keyboard. For example, some state dropdowns use "NV - Nevada", others just "Nevada", and some just "NV" -- in any case, it's hard for users to predict what to ...


3

It depends on whether or not you need to verify the address. When validation matters If you need to verify the input you need a database of validation rules. But even then, it will be hard to keep track of all possible valid formats and keep in mind that these things are not set in stone and may change at any time. You could think about offering an option ...


3

(I’m a non-native English speaker.) When I read your question title, I thought: Huh, what’s the difference between "email address" and "mailing address"? For me, "mail address" is a synonym for "email address". And "mailing address" is not that far away from "mail address". I think one of these labels would work better: postal address shipping address ...


3

While the order you have mentioned is typical for a specific group of countries, it may be totally different in other ones. In other words, whenever you refer to some specific order, it comes from a popular convention in a specific country (or group of countries). Going against standards (which are parallel to these popular conventions and thus also to user ...


3

The <address> tag is intended to be used for contact information for the author of the nearest <article> or <body> ancestor. Using it to indicate contact information for multiple entities or even a single entity that is not the author of the page is confusing the semantics of the element. This is why we have the microformat hCard. See ...


3

I found quite a detailed reference of mailing address formats from around the world but I'm not sure how up to date it is, so I found also a tool to look up address format by country. Skimming through both, you can notice that the overwhelming majority of countries do need only one line for street address. However, if the destination is a post office (PO) ...


3

I'd imagine address separation boils down to the following: Backend storage, useful for a variety of reasons like reporting Validation of individual elements of the address to ensure correctness (without, imagine the parsing you would have to do) Label printing The last thing you want is someone's credit card information on file, processed, with no way ...



Only top voted, non community-wiki answers of a minimum length are eligible