If you have a mobile app available on both iOS and Android platforms and you want to localize the strings in the same POEditor project, you can do that using iOS .strings and Android .xml files and by following the tips below.

1. Use the same keys for both iOS and Android

Keys (string IDs) are imported as terms in POEditor, and a term is unique by its term and context pair. Use identical keys on both platforms if you want each source string to be imported once and translated once.

2. Use the Tagging System

Import the iOS .strings file and the Android .xml file one after the other, and tag the strings with the platform name on each import. Tags keep the strings grouped by platform in the same project, so you can filter them during translation and export only the right strings for each app.

This is especially useful when some strings exist only on iOS or only on Android.

3. Use different keys for source strings that should be translated differently

If a source string needs a different translation on iOS and on Android, add it twice, with different keys. A term can only have one translation per language in a project.

4. Use placeholders that work on both platforms

Use placeholders common to both iOS and Android, because it is not possible to convert their format on export.

If you can't use the same keys for both iOS and Android

Create a separate project for each platform. After you translate one of them, translation memory (available from the Start plan) suggests the existing translations in the other project, so you don't translate the same text twice.

For platform-specific setup, see How to translate an iOS app and How to localize Android apps.