#Mobile App Localization

AI-translated localization files routinely pass CI while containing broken placeholders, missing plural categories, and inconsistent terminology. These five validation gates — placeholder integrity, file structure, plural coverage, glossary consistency, and human spot-check routing — are the enforcement layer between LLM output and your release branch. Each can be wired into a standard GitHub Actions pipeline with minimal setup.

AI translation tools like ChatGPT have no memory of what they translated three strings ago, producing different words for the same concept across your app. This post covers the five most common terminology drift patterns, shows a concrete before/after in Android strings.xml, and explains why the fix has to happen at the pipeline level — not the prompt level.

Pasting strings into ChatGPT before each release works until it doesn't — and the failure is cumulative, not sudden. This post details six structural breakdowns that compound across releases when you treat AI translation as a one-time task rather than a continuous workflow, and provides a practical framework for deciding when to make the switch.

AI-generated translations are syntactically valid, which means they pass standard CI checks and look fine in code review—until a native speaker opens the app. This post documents seven structural failure modes that survive every standard quality gate, with the exact pre-release checks that catch each one before they reach production.

AI translation tools process strings as isolated key-value pairs, with no knowledge of screen context, UI element type, glossary constraints, or prior translation decisions. This produces fluent, grammatically correct output that is semantically wrong in ways no automated checker catches — wrong part of speech, broken gender agreement, formality drift, terminology inconsistency, and silently truncated strings.

Most localization CI pipelines verify that translation files exist — not that they're correct. This post covers eight build-time checks that catch placeholder mismatches, incomplete plural forms, invisible encoding corruption, and the class of silent failures that AI-assisted translation introduces before they reach production.

With per-app language settings now standard on iOS 16+ and Android 13+, runtime locale switching is a first-class user expectation — not an edge case. This post covers the six distinct failure modes that occur when users change language mid-session, with platform-specific diagnosis and fixes for iOS, Android, and React Native. A correctly formatted string is useless if the locale state driving it is stale.

Number, date, and currency formatting is the localization category most teams treat as solved until it breaks in production. This guide covers correct formatter usage on iOS, Android, and React Native, documents the edge cases that consistently cause bugs — Arabic-Indic numerals, zero-decimal currencies, de-CH vs. de-DE — and provides a concrete testing checklist for every new locale you ship.

Most RTL launch failures aren't caused by engineers who didn't know better — they're caused by assumptions about who was handling which part of the review. This 27-item checklist covers layout mirroring, text rendering, number formatting, string quality, input behavior, and App Store distribution across iOS, Android, and React Native. Use it as a PR gate, a release sign-off template, or a handoff document to a localization QA vendor.

RTL failures cluster in predictable patterns that most test suites never exercise. This post covers six specific failure modes — from mirroring gaps in custom views to bidi rendering breaks in formatted strings — with reproduction steps and concrete fixes for Android, iOS, and React Native. Arabic and Hebrew together represent 400M+ potential users; these bugs are preventable with systematic testing.