Your first translation

Sign in to ReRune and select your organisation. Create a project for the application you want to localize. Choose a main language that your team can use as the source, then add a target language with its language code and display name.

Add a description of the product and its audience. Include translation guidelines for tone, terminology, and formatting. These details help collaborators and AI-assisted translation interpret short messages.

• Open the dashboard
• Projects and languages

If your app already has locale files, open the project translations and import a file with the matching platform format and language. Otherwise, create a key such as checkout_continue and enter its main-language value. Use the same identifier in your app.

Fill in the target-language value. Preserve named arguments, quantity variables, and message structure. Add notes when the meaning depends on where the text appears.

• Import and export
• Keys, placeholders, and plurals

Install the CLI, create an API key in your account, and run rerune in your application directory. The interactive setup selects the project, platform, and translation folder and writes rerune.json. Keep the API key in your local environment or an untracked .env file.

rerune

Commit or back up your current locale files before the first sync. Run pull, inspect the changes, then run your app and check the message in both languages. Run any code generation your localization framework requires.

rerune pull

• Install the CLI
• Understand pull and push

For OTA delivery, generate an OTA Publish ID in the project settings and follow your SDK chapter. Keep native fallback resources in the app. Publish the reviewed key in the dashboard, then trigger an SDK update check and verify the visible value.

Test once with a network connection and once offline. A fresh offline install needs bundled text; a later offline launch can use retained SDK cache. Editing a draft alone does not change the published text.