Automating Localization
summary
An app distributed to 156 countries in 40 languages uses a third‑party TMS, Github Actions, and an automated Google Translate pass to upload strings, order quick machine translations (minutes, cents) and generate OTA bundles for QA and staged releases; human orders carry a ~$400 minimum and run in parallel so by release users see improved human text while developers stop blocking on translations; remaining issues include mismatched locale ISO codes, unwanted draft screens being uploaded, and coordinating iOS and Android orders.
AI-written summary · about
chapters (11)
- 0:00Localization challenges
- 1:35Naive approach flaws
- 4:12Manual efforts and delays
- 5:52Localization platforms
- 6:56Automated workflow
- 9:27Benefits of new system
- 10:09Technical and procedural downsides
- 11:33Future improvements
- 14:23Optimized process and savings
- 15:05Tailoring solutions
- 16:08Q&A
related talks
48mContinuous Localization in Enterprise Web Projects
23mDriving Seamless Localization
26mContinuous Localization in Enterprise Web Projects
30mInfluence your customer outreach with best practices for internationalization
04mGlobalization Pipeline: Translations at cloud speeds
09mRemote Localizable Strings
17mStreamlining Mobile Releases
01h 11mSpeak My Language %app%
