OTA bundles & delivery

Over-the-air (OTA) translations let you ship updated copy to installed apps without waiting for app store review. StringJet builds JSON bundles per platform, serves them over HTTPS, and lets you separate production and prerelease channels so testers see changes before customers do.

Start with the OTA overview and platform guides on https://developer.stringjet.com. Edit strings in the editor first, then publish bundles from the app.

Production vs prerelease

For each of iOS, Android, Flutter, and web, you choose which built bundle is active for production and which is active for prerelease. That supports staged rollouts and QA builds that opt into prerelease channels in your SDK integration.

Build and publish flow

From the Bundles tab, build a new OTA bundle for the selected platform, review bundle rows (including display names for your team), assign Prod and Prerelease with the radio controls, then save active bundles. Only project owners and developers can publish or clear selections, matching how you gate production changes.

How apps authenticate

Apps use the SDK with credentials from Project info — never embed raw secrets in marketing pages. The runtime fetches the correct JSON for the platform and channel your app requests. OAuth for humans is separate from SDK tokens; see Add the SDK.

OTA storage & delivery limits

Published bundles consume OTA storage; serving bundles to devices consumes OTA delivery against your plan. Usage appears in Plan & billing and in project info. Compare tiers on pricing.

Reliability & backups

Pair OTA with automated backups so you can restore translation state if something goes wrong during a large change.