Publishing and OTA delivery

The translation editor holds the current draft. A key can be unpublished, published, or modified since its last publication. Saving a change updates the draft; publishing makes a snapshot available for delivery.

This separation lets you prepare new wording while users continue to receive the existing publication. A CLI push or an import changes drafts. Publish to release them to normal SDK clients, or use OTA staging to preview saved drafts in a test app before publication.

1. Open the project and review the keys, languages, placeholders, plurals, and variants you intend to release.
2. Select the keys and choose the publish action. Your account needs publishing access.
3. Use a publication tag that identifies the change or release so it can be found in history.
4. Confirm publication, then check the result in an app using that project OTA Publish ID.

Check the selected key set before confirming. Publishing should represent a deliberate release of the reviewed content, especially when the project serves multiple apps or audiences.

• Draft sync and publication are separate jobs

1. The SDK identifies the project with a read-only OTA Publish ID.
2. An update check requests the current publication information and relevant locale content.
3. The SDK applies supported messages and caches successfully fetched data according to its platform implementation.
4. The application renders the new values through its native translation engine and any required revision observer.

An online app receives a change on its next successful update check. Publication is not a push notification to every installed device. A disconnected app continues using its available cached or bundled text.

Monthly OTA usage is measured in successful SDK response-body data served by the origin. Check the account plan and current usage when investigating delivery limits.

• Plans and OTA quota

Open publication history, inspect the earlier snapshot, and restore the version you want to deliver. Restoration changes live delivery while keeping the current editor draft separate. Verify the restored text through a successful SDK update check.

Unpublishing removes a key from current published delivery. It does not erase text already cached on disconnected devices. Confirm fallback behavior in your app before using unpublish as part of a release change.