Overview
Over-the-air (OTA) updates let your app download translations at runtime instead of shipping them frozen in the build. Fixing a typo, retranslating a sentence or adding a language becomes a publication in SimpleLocalize, not a new App Store or Play Store release.
OTA updates are built on Translation Hosting:
- Translate in the Translation Editor as usual.
- Publish the translations to Translation Hosting. See publishing translations.
- Your app downloads the published translations from the CDN, caches them and shows them instead of the strings bundled in the build.
Translations you have not published keep using the strings bundled in the app, so the UI never breaks when a key is missing.
Mobile apps
The OTA SDKs work on top of the localization you already have. They override bundled strings key by key, cache downloaded translations on disk so the app works offline, and never remove what was already downloaded when a refresh fails.
| Platform | Requirements | Package |
|---|---|---|
| iOS & macOS | iOS 13+, macOS 11+, tvOS 13+, watchOS 6+ | Swift Package, no dependencies |
| Android | minSdk 21 | Gradle library, no runtime dependencies |
Both SDKs read the same published files, so one publication updates your iOS and Android apps at the same time.
Web apps
Web apps can load translations straight from the CDN, for example with an HTTP backend of your i18n library. See fetching translations for the URLs and the available files per language, namespace and customer.
Environments and rollbacks
- Point development builds at the
_latestenvironment and release builds at_production, so you can check translations before your users see them. See environments. _productionis served withCache-Control: max-age=3600, so a publication reaches users within about an hour.- If a publication goes wrong, roll back to a previous one. Apps pick up the restored translations on their next refresh.