Skip to content
← All articlesEngineering

Software Localisation and Internationalisation Guide

A practical guide to software localisation and internationalisation (i18n) for web and mobile apps: what to build first, common pitfalls and how to plan.

Selling to customers in the US, UK, Europe, the Middle East or Australia usually means more than translating a few screens. Dates, currencies, addresses, text direction and even the length of a button label all change from market to market. Teams that treat this as a late-stage “translation task” often discover that their codebase has to be reworked first.

This guide explains the difference between internationalisation and localisation, what to get right early, and how to run the work with an outsourced team.

Internationalisation vs localisation

The two terms are often mixed up, but they describe different jobs:

  • Internationalisation (i18n) is an engineering task. You design the product so that it can support any language or region without code changes.
  • Localisation (l10n) is the content and configuration task. You adapt the product for a specific market: translated text, local formats, legal wording, imagery and payment methods.

Do i18n once, properly. Then each new market becomes a localisation exercise rather than a development project.

What changes between markets

Area What to plan for
Text Translation, plurals, gender, and strings that grow or shrink
Dates and times Formats, time zones, first day of the week, calendar systems
Numbers and currency Decimal and thousands separators, currency symbols and placement
Addresses and names Different field order, postcode formats, single-name users
Text direction Right-to-left layouts for Arabic and Hebrew
Legal and privacy Consent wording, terms, tax display, data residency
Payments Local methods and expectations by country

Engineering foundations to get right early

1. Never hard-code user-facing text

Every visible string should come from a resource file or translation catalogue, not from the source code. Use message keys and keep them stable. This applies to error messages, emails, push notifications and validation text as well as page copy.

2. Do not build sentences by concatenation

Joining fragments such as “You have” + count + “items” only works in English word order. Use full message templates with named placeholders, and use a proper plural-rules library. Languages differ in how many plural forms they have, so a simple “singular or plural” check is not enough.

3. Use the platform’s formatting tools

Modern browsers provide the Intl APIs for dates, numbers, currencies and relative time. iOS and Android have equivalent locale-aware formatters. Use them rather than writing your own format strings.

4. Store dates in UTC, display in local time

Keep timestamps in UTC in the database and convert at the edge, using the user’s time zone. Store the time zone explicitly where it matters, for example for appointments or deadlines.

5. Support Unicode end to end

Make sure your database, APIs, fonts and exports handle UTF-8 everywhere. Test with names and text from several scripts, not just accented Latin characters.

6. Design for text expansion and right-to-left

Translated text is often noticeably longer than English, so fixed-width buttons and tight layouts break. Use flexible layouts and logical CSS properties (such as margin-inline-start) instead of left and right. If you may support Arabic or Hebrew, build mirroring in from the start; retrofitting it is expensive.

Choosing a locale strategy

Decide how a user’s language and region are determined, and keep these separate. A person in Germany may want the interface in English but dates and currency in German formats.

  • Language comes from user choice first, then browser or device settings.
  • Region drives formats, currency and legal content.
  • URLs for web apps should reflect the language (for example /de/ paths), with correct hreflang tags so search engines show the right version to the right audience.

Managing translations

Translation is a workflow, not a one-off file handover. A workable setup includes:

  • A translation management tool or a clear process for exporting and importing strings.
  • Context for translators, such as short descriptions and screenshots, since a single word like “Order” can be a noun or a verb.
  • A glossary for brand and product terms that must stay consistent.
  • A review step by a native speaker who knows your domain.
  • Machine translation only as a first draft for low-risk content, never as the final text for legal, medical or financial wording.

Testing localised products

Localisation bugs are easy to miss because developers rarely read the target language. Build checks into your QA process:

  • Pseudo-localisation: replace strings with accented, lengthened text to find hard-coded text and layout breakage before real translations arrive.
  • Layout checks in every supported language and in right-to-left mode.
  • Format checks for dates, numbers and currency with real regional settings.
  • Functional tests for sorting, search and input in each locale.
  • Release checks that no translation keys or placeholders appear on screen.

A short readiness checklist

  • No hard-coded user-facing strings in code
  • Plural and placeholder handling uses a proper library
  • Dates stored in UTC and formatted per user locale
  • Layouts tested with long text and, if needed, right-to-left
  • Translation workflow and glossary agreed
  • Legal, privacy and payment content reviewed per market
  • Pseudo-localisation included in automated or manual testing

Working with an outsourced team

Be explicit in your requirements about the markets and languages you need now and those you expect later. A good partner will build the i18n foundations into the first sprint, include localisation in the definition of done and test each language before release. Agree who owns translations, who reviews them and how new strings are handled in each release. For related practices, see our guides on onboarding an offshore development team and website accessibility and WCAG.

If you are planning a multilingual web or mobile product, our web development team can help you design it for global use from day one. Contact us to discuss your target markets.

Let’s build what’s next.

Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.