While you get most comfort out of using our CDN your environment might demand you to bundle the translations with your product (eg. offline usage in areas with restricted internet access or with offline fallback).
Using our CDN has three big advantages:
You can deploy updates to translations without the need to redeploy/rollout a new version of your application.
During development, testing you can set your versions to auto publishing. Doing so your translation changes are reflected immediately in your application and results in a lot easier development process.
You can easily set a version to publish in private mode, which means you will need an API key to download your translations. This enables you for example to use locize as before but without leaking any information to the public.
If your product demands to download the translations, because you need or prefer to host or bundle them yourself you can do so. Using our CDN is completely options and get only billed if you’re using it.
Options to download the translations:
Using our web applications
We highly encourage you to at least use the CDN during development as it makes your work on translating your product a lot more efficient. Just bundle or change the i18next backend implementation during production. Or do both on production: Define a primary backend for the normal locize CDN and a second fallback CDN with local/bundled fallback translations. Here you can find an example usage with backend fallback.