Prompt
How do I set up a translation workflow for web and mobile releases
Latest observation
A good translation workflow for web and mobile releases usually has 5 parts:
- Choose a source-of-truth for strings
- Extract/localize strings from code
- Send strings to translators
- Review and QA translations
- Ship and update translations continuously
Here’s a practical setup that works well for both web and mobile.
1) Standardize your translation files
Use one consistent format across platforms if possible.
Common choices:
- JSON for web and some mobile apps
- YAML or PO if your tooling prefers it
- Platform-specific formats:
- iOS:
Localizable.strings,String Catalogs - Android:
strings.xml
- iOS:
If you can, keep a centralized translation source and generate platform-specific files from it.
Recommended structure
Use keys that are:
- stable
- descriptive
- not tied to exact English wording
Example:
{
"auth.login.button": "Log in",
"auth.login.error.invalid_password": "Incorrect password",
"home.welcome": "Welcome, {name}!"
}
Avoid using English phrases as keys like:
{
"Log in": "Log in"
}
2) Build a localization process into development
During development
- Developers add new keys when UI text changes.
- Use placeholder text in source language.
- Avoid hardcoding strings directly in components.
Example
Instead of:
<button>Log in</button>
Use:
<button>{t("auth.login.button")}</button>
For mobile:
- iOS: use localization APIs / string catalogs
- Android: use
@string/...resources
3) Decide how translations get updated
You usually have two options:
Option A: Manual file-based workflow
Good for smaller teams.
Process:
- Developer adds new keys
- Export source strings
- Send file to translator
- Import translated files back into repo
- Ship with app release
Pros:
- simple
- cheap
- easy to control
Cons:
- more manual work
- slower
- error-prone at scale
Option B: Translation management system (TMS)
Best for teams with frequent releases.
Popular tools:
- Lokalise
- Crowdin
- Phrase
- Transifex
- Weblate
Typical flow:
- Push source strings to TMS
- Translators work in the TMS
- Pull translations back into repo or via CI
- Build/release with updated locale files
Pros:
- automation
- translator-friendly
- supports context, screenshots, comments
- better for web + mobile together
Cons:
- cost
- setup time
4) Add context for translators
Translations are much better when translators know:
- where the string appears
- character limits
- tone of voice
- if it’s a button, title, error, or label
Add metadata when possible:
- developer comments
- screenshots
- UI context
- placeholders explanation
Example:
{
"checkout.submit": "Place order"
}
Context note:
- “Button on checkout page. Confirms purchase.”
Also support placeholders carefully:
"home.welcome": "Welcome, {name}!"
Make sure translators know:
{name}must stay in place- whether pluralization is required
5) Handle pluralization, gender, and interpolation properly
Don’t hardcode plural logic in English only.
Example:
{
"cart.items": "{count, plural, one {# item} other {# items}}"
}
Use a localization system that supports:
- plural rules
- interpolation
- gender/context if needed
This is especially important for mobile and international releases.
6) Wire localization into CI/CD
Make releases safer by automating checks.
Useful CI checks
- missing translation keys
- unused keys
- invalid JSON/XML syntax
- placeholder mismatches
- missing locales for release branches
Release flow example
- Merge code with new strings
- CI extracts strings and validates them
- Strings sync to TMS
- Translations are completed
- CI pulls translations
- Build is created for web/mobile release
- QA validates on target devices/browsers
7) Plan for web vs mobile differences
Web
- translations can often be updated faster
- you may be able to ship locale updates without full app deployment if using runtime-loaded translation files
- consider code splitting and lazy loading locale bundles
Mobile
- app store releases may delay translation rollout
- embed translation files in the app or fetch them remotely if your product allows it
- be careful with offline support if strings are remote
A common approach:
- web: load locale files from CDN or app bundle
- mobile: bundle translations with the app, optionally supplement with remote config for noncritical text
8) Create a release checklist
Before release:
- all new strings added to source locale
- translations complete for target markets
- screenshots/context updated for changed UI
- QA checked:
- long text overflow
- truncation
- RTL layouts if applicable
- date/time/number formats
- fallback behavior for missing translations
After release:
- monitor untranslated strings
- track user-visible fallback language usage
- collect translator feedback
- fix key naming or context issues
9) Support localization best practices
Important details:
- use locale-aware formatting for dates, numbers, and currency
- support RTL languages if needed
- avoid concatenating translated fragments
- keep strings short and flexible for expansion
- test with pseudo-localization
Pseudo-localization
Useful for catching UI issues before real translation:
- expand strings
- add accent marks
- simulate RTL
Example:
Save→[Šávèè]
10) A simple recommended setup
If you want a practical starting point:
Small team setup
- Source strings in JSON
- i18n library:
- Web: i18next, FormatJS, Lingui, react-intl
- Mobile: platform localization APIs or shared library if cross-platform
- Use Git for version control
- Use a TMS if you have more than a few locales
- Add CI validation for missing keys and placeholder mismatches
Larger team setup
- Central TMS
- Automated sync with GitHub/GitLab CI
- Locale QA in staging
- Screenshot/context capture from design or app builds
- Release gate if critical locales are incomplete
Example workflow
- Product adds UI copy in English
- Developer adds translation keys
- Build system extracts strings
- Strings sync to TMS
- Translators translate with context and screenshots
- QA reviews in staging build
- Translations merge back to repo
- Web deploys immediately
- Mobile release includes updated locale files in the app build
Best tools by need
If you want simplest setup
- i18next / react-intl
- JSON files
- Git-based workflow
If you want scalable workflow
- Lokalise / Crowdin / Phrase
- CI sync
- context + screenshots
- automated validation
If you want, I can also give you:
- a recommended tooling stack for React + iOS + Android, or
- a step-by-step translation pipeline you can implement in GitHub Actions.