Researchers at the University of Michigan once sat 25 American and 27 Chinese participants in front of the same photographs and tracked where their eyes went. The Americans found the main object about 118 milliseconds faster and stared at it longer. The Chinese participants kept moving between the object and everything around it, spending far more time on the background. In a companion study, Japanese participants described 60% more background detail than Americans looking at identical scenes.
When other researchers ran something similar on web pages, the pattern held. Chinese and Korean users swept the page in a rough circle, taking it all in. Americans started in the middle and worked outward, hunting for the focal point.
That’s a slightly unsettling thing to learn if you design for international markets. Before anyone translates a word or argues about a colour, your users are already reading the screen in a different order. Localized design is how you account for that, and it’s usually why a layout that tested well at home feels vaguely off somewhere else around the globe.
Here are 6 things worth getting right.
1. Text Expansion and Contraction
Translate a word, and it rarely stays the same length. The scale of the change catches teams out.
IBM’s guidelines, published by the W3C, show a short English word of 5 or 6 letters can come back 2 to 3 times longer. Longer sentences grow far less, usually by about a third. So the shortest text swells the most, and short text sits in your buttons, menus, and tabs.
Take “views,” for example. In German it becomes “-mal angesehen,” in Italian “visualizzazioni,” both roughly 3 times as wide, both needing to fit a button you sized for five letters.
Across a whole interface, most European languages run 15% to 30% longer than English, with German and Dutch often past 35%. Chinese, Japanese, and Korean use fewer characters, but need more space between lines to stay readable, so you gain less room than the character count suggests.
Preventing all of this comes down to three habits:
- Don’t lock the width of buttons and boxes
- Leave space around labels so there’s room to grow
- Before translating, swap your English text for overlong dummy words.
2. Cultural Adaptation of Visual Elements
Images carry meaning just as reliably as words do.
White means purity across much of the West and mourning across much of East Asia. Red reads as danger in some places and prosperity in others. A palette you chose for a specific emotional effect at home may produce a different one abroad.
Icons are riskier, mostly because they feel universal when they aren’t. Hand gestures, for example, can carry offensive meanings in particular regions. Mailboxes, currency symbols, and light switches all look different from country to country, so the object you drew from life is somebody else’s abstraction.
3. Local Rules, Formatting, and Compliance
Every locale arrives with formatting conventions you either accommodate or fight.
Dates run month-day-year in the US, day-month-year across most of Europe, and year-month-day through much of Asia. Numbers are split on commas in English and periods in German, so “1,000” is a thousand in London and one in Berlin. Currency symbols sit before or after the figure depending on where you are.
Right-to-left languages like Arabic and Hebrew are a lot harder to navigate. Moreover, navigation, icons, progress bars, and reading order all mirror. All of these issues seem small individually, but pile up quicker than you’re able to realize.
4. User Experience (UX) and Cultural Nuances
Interfaces that do well across parts of East Asia often pack far more onto a screen than Western users find comfortable, and that’s a functional feature. If people are scanning holistically and reading context alongside content, a dense layout is legible to them in a way it isn’t to someone hunting a single focal point.
Trust works pretty much the same way. How much reassurance someone wants before entering payment details, how prominent your guarantees need to be, which payment methods people trust, all of it shifts by region.
The ironic part is that none of this turns up in a translation file. You only find it when real users from the market work through the real interface, which is why in-market testing belongs inside your localization plan.
5. Brand Consistency Across Markets
Adapting to local markets while still looking like yourself is the central tension here, and you solve it by deciding upfront what’s fixed and what can move.
Logos, core palettes, and brand marks usually stay put, because they’re working on recognition. Typography, imagery, layout density, and tone can shift while still expressing the same personality.
It’s also worth discussing fonts early on in the process. A typeface chosen for how it looks in English, for example, may not include the characters for Russian, Arabic, Japanese, or Chinese at all. When that happens mid-launch, someone swaps in whatever font does cover the script, and suddenly your brand looks like a different company, definitely not the look you were going for!
The practical safeguard is a brand guideline that’s localization-aware, one that says plainly which elements are fixed, which are adaptable, and who signs off on regional variations.
6. Preparing Design Files for Translation Workflows
Good files save money in every language. Bad ones multiply manual work by the number of markets you’re in.
Keep your text live and editable, because copy flattened into an image can’t be translated without rebuilding the asset. Make sure to use consistent paragraph and character styles, so adjusting size for a longer language is one global change instead of a hunt through individual text boxes. Lastly, build flexible containers rather than pixel-locked frames and always name your layers!
Most importantly, give translators context. Screenshots, string descriptions, and character limits all allow someone to make a choice that actually fits the space, which is more than a spreadsheet of disconnected phrases allows.
Bring In Eyes That Aren’t Yours
Ironically, your own team is the worst possible judge of whether a design works abroad. Everyone reviewing the mockup shares roughly the same reading habits and instinct for what looks clean.
That’s why the six things above are process problems more than design problems. Flexible containers, script coverage, live text, and in-market testing – none of it requires unusual talent. It simply asks you to decide early, while decisions are still cheap.
When you get it right, none of the work shows. Users in each market just find something that feels like it was built for them.
At EC Innovations, our localization services support global teams across the whole design workflow, from adapting layouts and page assets through to review by native speakers in the markets you’re targeting.
Contact us to talk it through, whether you’re preparing a first international release or fixing a design system that stopped scaling.



