Build Assets
Checklist

Internationalisation Readiness

Layouts and strings are ready for translation without breaking.

Platform: bothTags: i18n, l10n, translation, localisation, international

Check

All UI strings use a translation function or key lookup (not hardcoded English). Layouts accommodate 30% text expansion (German, Finnish expand significantly). Date, time, number, and currency formats use locale-aware formatting. Text containers don't clip at fixed widths. RTL languages don't break layout.

Why This Matters

Postel's Law: be liberal in what you accept. UI that assumes English text length will break when translated. Retrofitting i18n after launch is 3–5× more expensive than building it in from the start.

Category

Launch Readiness

Priority

important

How to Verify

Pseudo-localise: replace all strings with 30% longer equivalents. Check every layout for overflow or clipping. Test a right-to-left locale if RTL is a target market.

Source Topic

ux psychology

Postel's Law

Be liberal in what you accept