Localizing React Native apps from start to end
summary
A small demo app compares fbt and i18next showing pluralization, parameter insertion and styled fragments; fbt extracts whole sentences, requires a description prop, uses Babel, yields smaller bundles but a smaller community, while i18next uses handwritten IDs, double-curly placeholders, larger bundles and many plugins. Workflow advice includes using CAT platforms like Crowdin, Phrase and Locaas, leveraging translation memory, machine translation plus human post-editing, term bases and QA checks, and uploading screenshots or Figma context so translations actually fit the UI.
AI-written summary · about
chapters (10)
- 0:00Introduction to localization
- 1:50Common localization failures
- 3:56Library comparison and demo
- 6:37Working with fbt
- 10:18Working with react-i18next
- 12:32Comparing fbt and i18next
- 14:33Modern translation tools
- 15:26How translators work
- 19:30Translation best practices
- 25:54Native platform specifics
related talks
31mRewriting a Large Hybrid App with React Native
27mBuilding high quality mobile apps with React Native
08mReact Native and Badoo story of a massive experiment
01h 01mReact Native: A Better Way to Do Mobile
01h 13mMigrating to React Native: A long-term retrospective
25mReact developers in a wild world of native apps
44mReact Native: how to succeed with your mobile app
35mBridging the Gap: How to use React Native in existing large native code bases