Keys and platforms

Updated 2 months ago ​by Nick Ustinov

Assigning platforms

One of the unique features of Lokalise is the ability to use similar keys across different platforms, thus reducing the translation work amount to be done by translators. Once you import or add keys, they need to be assigned to one or several platforms (e.g. iOS, Android). 

Assigning key to a platform actually means including the key in the export routine for the file formats, that are suitable for this platform. Example – if the key is assigned to both iOS and Android platforms, it would get exported to Apple .strings and Android .xml, however would not go to Web .json export (while keys with Web platform would only go to .json export). You can think of platforms as global tags for the keys. In case you want all the keys to get exported despite the platform (i.e you need to export all to Excel), just turn on Include all platforms switch at the project download web panel.

Different keys for different platforms

Coding for different platforms usually involves different naming schemas, for example iOS coders prefer "LoginButton", while Android coders are keen for "login_button". Lokalise has the solution for the never-ending battle. Enable "Per-platform key names" in project settings, then once you add a new key (or edit the imported one) there is an option to set unique key name per platform. 

Hidden and archived keys

If you are not done editing your original translation, mark the key as "Hidden from contributors" so contributors can't see it and don't start the translation. Note, that other project owners will see this key and it's translations.

Optionally, you may want to archive keys so they are not visible in statistics, export, search and similar. Archived keys can be found by choosing "Archived" in Filter. In order to archive or unarchive keys, select the desired keys in editor view (by ticking a checkbox on the left of the key) and choose appropriate action from the floating box.


How did we do