Mobile applications have the added dependency of an extra approval step to the store of choice (Android or iOS) when a change is introduced. Transifex Native will deliver independently translation phrase changes bypassing this approval step leveraging over the air delivery and a version control system to make sure older application versions are not affected when you don’t need them too.
A workflow example of Transifex Native over mobile application will work like:
- Release/deploy new code containing Transifex Native marked source strings in your app binary , ideally we would like for Transifex Native to offer the option to deploy source keys/ids only so that you will be able to change the source language as well but some more research is needed on our side for that. An additional option to bundle a default set of translation along with the code release will be available to make sure that translations are always available, even if on an offline first run of the installed mobile application.
- Along with the release you can also dictate the app version so that Transifex Native knows which version of the translations to serve. This way you can secure that older installations do not miss any removed or updated strings reflecting newer functionality not available in the older versions.
- Update/add translations in Transifex. These translations will be available whenever the mobile app has access to internet, by requesting newest translations for the specific version. These translations are stored in a local cache to be available in case mobile is offline.