Source repositories remain authoritative
Import Android XML, Apple .strings or supported Flutter ARB messages as part of development. Keep format-specific build tooling in your app pipeline.
Check resource correctness
Protect placeholders and preview changes. Test resource export in the relevant build system, particularly for plural categories, escapes and platform-specific string resources.
Keep humans in control
Assign locales to translators, let them propose changes to existing translations, and ask a reviewer to approve the final version before a release.
Common questions
Are mobile apps updated instantly?
No, mobile releases require their own integrated delivery and update mechanisms.
Do imports preserve all Apple/Android metadata?
Advanced metadata fidelity needs testing on each format.
Before relying on this in production
Confirm support for your resource syntax and test exported translations in your application. Documentation describes supported workflows, not a guarantee of lossless conversion for every specialized format.