Introducing Crowdin translations versioning

Previously, adding new translations to crowdin meant rebuilding the entire app each time, which was time-consuming and impractical.
Now, with the release of TIXNGO back-office led crowdin synchronization feature, we're making things a lot easier.

What does this mean for you?

By introducing the sync and versioning of crowdin translations directly from TIXNGO back-office, you have now access to an easy and convenient way to switch from one translation set to another, without requiring a new build.

Selecting the target version

By accessing the application settings « Target translation version will be applied to ticket app » (key: mobile.app.translations.target-version), you will see the selected target version of crowdin translation.

Getting crowdin latest translation

From the mobile.app.translations.target-version edit screen, click the sync button

TIXNGO will query and checks if a new crowdin project build is available.

• If the version has been already synced, there is nothing left to do.
• If a new crowdin translations build is available, TIXNGO will download it and store its metadata (version, build date, sync date, path) to be reused in the drop-down list and ease target version selection.

Wallet behaviour

We can now load translations dynamically directly from the app, on the fly. In simpler terms, spectators will always see the latest translations without needing to rebuild or update their app.

1. If mobile.app.translations.target-version is null or empty (ie you did not started to use this feature yet), the branded wallet will use the local translation file
2. If mobile.app.translations.target-version is set and not equal to the current version on the mobile app, the branded wallet will
   1. Initiate the download of translations file
   2. Change the current version information on the mobile side, if the download is successful.
3. Otherwise, if mobile.app.translations.target-version equal to the current version, the file won't be downloaded.