Form Internationalization Techniques | Marvel Blog
📹 New! Remote User Testing - Get video + voice feedback on designs and prototypes
Request Demo

Form Internationalization Techniques

Posted 3 years ago by Andrew Coyle

Approaches to collect addresses in a globalized world

Internationalization and localization are broad topics, which have large implications on the web. This article examines techniques to internationalize address fields.

Structured vs. Generic Input Field

The example on the left shows two methods for collecting a phone number. As I wrote about in Design Better Input Fields, the structure and length of the field communicates what is needed. Whenever possible, format the input to the desired entry.

However, formatting the input in this way causes issues for international addresses and phone numbers. If the country is not known, it is usually better to present an unstructured generic input to account for the country variations in form fields.

There are 3 common approaches to internationalize address fields as Luke Wroblewski points out: specific, changing, and generic formats.

Specific Format

The specific format works when the system can interpret the user’s country and present the appropriate address structure. This technique is problematic if the system doesn’t have access to a user’s geo-location data, or if the user intends to enter an address for a location outside their country. For example, geo-location data is of no use if the user is entering a list of global distribution centers into a network database. The changing format is a better approach for this use case.

Changing Format

Changing formats present the appropriate address fields based on the specified country. The country selector is presented before or after the address fields. When a user selects a country the field labels change and the structure reformats. The changing format can also be achieved by asking for a user’s country in a step before presenting the address fields.

Generic Format

The generic format is the most flexible way to capture an address. Each input is unstructured, which makes it hard to check for errors. This approach can cause data integrity issues because the user can enter an address in various ways. State/Province/Region and ZIP/Postal Code should be optional because not every address will have them.

A Fourth Way

There is another way to approach internationalization. The fourth way incorporates an auto-complete address field input. A user is presented with a list of suggested addresses as they type. The user then chooses the correct address and the form changes structure based on the country and populates the selected data in the fields below. The user can then edit and add any missing data.

What are other methods to collect addresses in a globalized world?

Find me on Twitter, and Dribbble.

Get started with Marvel Enterprise

Get started with Marvel Enterprise

From CEOs to marketing, get your entire organisation collaborating in one place.

Get started with Enterprise

Designing the future of global trade @Flexport. Follow me on Twitter.

Related Posts

Successful products from the Soviet Union that were created in isolation to the rest of the world.

How to choose the right UI component for the type of message you want to deliver to your users.

Making good component design decisions in react when it’s hard to see how an existing component can still be reused