Internationalization Examples - Inspiration & Best Practices

Internationalization (i18n) prepares your application for use across multiple languages, regions, and cultures. This goes beyond text translation: date formats, currency, text direction, pluralisation, and culturally relevant imagery all need to be considered. A well-designed i18n architecture makes adding new languages straightforward without code changes. Below we show how various platforms implement internationalization.

E-commerce platform with 12 languages and regional pricing

An international e-commerce platform serves customers in 12 languages and 8 currencies. Product descriptions are translated by professional translators and stored in a headless CMS with per-locale content. Prices are dynamically calculated based on the visitor's region, including local tax rules. The URL structure uses locale prefixes (/en/, /de/, /fr/) for SEO-optimal indexing per language version.

• Headless CMS with per-locale content management
• Dynamic currency conversion with local tax calculation
• SEO-optimised URL structure with locale prefixes
• Hreflang tags for correct language version indexing by search engines

SaaS dashboard with runtime language switching

A SaaS platform implemented runtime language switching where users can instantly switch languages without reloading the page. Translations are lazy-loaded: only the active language is loaded, and additional languages are fetched on demand. A namespace system divides translations by feature module so large applications remain manageable. Fallback logic displays the English text when a translation is missing.

• Runtime language switching without page reload
• Lazy-loading of translations per namespace and language
• Fallback chain: requested language → English → translation key
• Context-dependent translations for plurals and gender

Legal platform with RTL support

A legal platform serves clients in Arabic and Hebrew alongside Western languages. The entire UI mirrors for RTL languages: navigation, tables, icons, and text alignment are automatically flipped. CSS logical properties (inline-start/end instead of left/right) enable this without separate stylesheets per text direction. Bidirectional text in documents is correctly handled with Unicode directional control.

• CSS logical properties for automatic RTL mirroring
• Bidirectional text handling with Unicode BIDI control
• RTL-aware icons that automatically mirror when needed
• Separate typography settings per script system

Mobile app with locale-aware formatting

A financial app formats numbers, dates, currency, and phone numbers according to the user's locale. The system uses the Intl API for consistent formatting: 1,234.56 for the US versus 1.234,56 for the Netherlands. Dates are displayed in the local format and relative timestamps ("3 hours ago") adapt to the language. A/B testing shows that locale-correct formatting increases user trust by 23%.

• Intl API for locale-consistent number and date formatting
• Relative time formatting (timeago) in the local language
• Phone number validation and formatting per country
• Locale-aware sorting rules for lists and tables

Marketing website with translation workflow

A marketing website manages translations through a structured workflow. Content is created in the source language (English), automatically exported to a Translation Management System (TMS), translated by professionals, and imported back via a webhook. A preview environment shows translations in context before publication. Untranslated content is flagged in the CMS with a completeness indicator per language.

• Automated export/import pipeline with TMS integration
• Preview environment for translations in context before publication
• Completeness tracking per language with visual progress indicator
• Glossary management for consistent terminology across translations

Key takeaways

• Design your i18n architecture from the start: retrofitting is many times more expensive.
• Use namespaces and lazy-loading to keep translations manageable and performant.
• RTL support requires CSS logical properties and intentional UI design, not just mirrored layouts.
• Locale-aware formatting of numbers, dates, and currency increases user trust.
• An automated translation workflow with preview capability accelerates time-to-market for new languages.

How MG Software can help

MG Software implements scalable internationalization solutions that prepare your application for a global audience. From i18n architecture and translation workflows to RTL support and locale-aware formatting — we ensure your product delivers a native experience in every language and region.