Translation management, from six quite different jobs
A mobile release cannot be hot-fixed, a website's copy is also its SEO, and a white-label customer needs eighteen strings changed and four thousand left alone. Start from the one that sounds like yours.
By what you ship
Pull translations at build time and ship them with the bundle. JSON or YAML, straight into the repo.
Mobile appsNative formats and a release you cannot take back. Gate the build on the locales you promised.
WebsitesMarketing copy where the wording is the positioning, and a bad translation is a bounce.
By the job in front of you
One default set of strings, a variant per customer, and inheritance so a shared fix reaches all of them.
Continuous localizationPush on merge, pull the finished files back, gate the release on progress.
AI-first translationMachine drafts with your glossary and context, arriving flagged for review rather than silently published.
Working with outside translatorsScope an agency to one app and a freelancer to one language of one variant.
Market-specific wordingA regulated market that needs its own phrasing, as a variant rather than a fork.
Design filesPlannedPulling strings out of Figma before the screen is built is on the roadmap, not in the product today.
By who you are
The same workspace, seen from four desks.
Three HTTP endpoints, scoped keys, native file formats and an MCP server.
Product managersThe whole string set on one screen, with history and a review state you can trust.
DesignersWording decided and reviewed before it is built, with context attached to the key.
Localization ownersGlossary, registers, per-locale progress and an activity trail for the workspace.
Start with whichever one is on fire
A workspace takes a minute and the first import takes one drag.