Git Branching Strategy: Trunk-Based vs GitFlow for Teams
Trunk-based development or GitFlow? Compare Git branching strategies for outsourced and offshore teams, with a decision table and rules that keep releases safe.
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.
The two terms are often mixed up, but they describe different jobs:
Do i18n once, properly. Then each new market becomes a localisation exercise rather than a development project.
| 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 |
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.
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.
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.
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.
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.
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.
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.
/de/ paths), with correct hreflang tags so search engines show the right version to the right audience.Translation is a workflow, not a one-off file handover. A workable setup includes:
Localisation bugs are easy to miss because developers rarely read the target language. Build checks into your QA process:
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.
Trunk-based development or GitFlow? Compare Git branching strategies for outsourced and offshore teams, with a decision table and rules that keep releases safe.
Monorepo or polyrepo? Compare code repository strategies for web, mobile and backend products, with a decision table and tips for outsourced teams.
How to version and retire APIs without breaking clients: versioning options, breaking-change rules, sunset policies and a checklist for outsourced teams.
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.