Point your app at the CDN so it loads translations at runtime instead of baking them into your build.
Who this is for
A developer with access to the app's source. Minting the key needs admin.
Before you start
You need a CDN key for the project, and at least one published locale. Both come from the project's Deploy screen.
Steps
Open the project's Deploy and mint a CDN key under Tokens, keys, webhooks & CDN. Copy it; it is shown once.
Install the runtime package for your framework.
Configure it with your project, your CDN key, and the locale to load.
Deploy your app.
What happens next
Your app fetches the published bundle for the requested locale on load, and uses it for the rest of the session. Publishing a new version in transglot reaches your users without a new build.
Because the bundle is fetched rather than bundled, cache behaviour matters: the latest address revalidates frequently, so expect a new publish to appear within about a minute rather than instantly.
If it doesn't work
If nothing loads, check the locale has actually been published. An unpublished locale has no bundle to serve, however complete it looks in the editor.
If requests are refused, check the key is the project's CDN key and not a deploy token; they are different credentials with different powers.
A request for a format the version was not published in will not find anything. Ask for the published format.
Related
The CDN
Publish a locale
The runtime SDKs