ReRune documentation
Manage your translations, connect your codebase, and deliver published text to your apps. Start with the workflow, then follow the guide for your stack.
On this page
Start here
Your first translation
Take a message from your repository to ReRune and back into your app. This walkthrough covers workspace setup, a first sync, and optional runtime delivery.
Install the CLI
Install ReRune on macOS, Linux, or Windows and connect an application directory to your project.
React
Add OTA delivery to an i18next app while keeping native resources, translation hooks, and language switching.
Publishing and OTA delivery
Release reviewed translation snapshots and understand when installed applications receive them.
OTA staging and live preview
Preview saved draft translations in a test app before publishing. Enable project staging, opt in your SDK, and understand refresh and cache behavior.
Set up ReRune in CI/CD
Pull published translations in GitHub Actions, validate application requirements, build once, and deploy the tested artifact using the runnable ReRune CI demo.
How ReRune works
ReRune stores the text your application displays as translation keys. Each key has values in your project languages. Your team edits those values in the dashboard, uses context and dictionaries to guide translation, and publishes the text that is ready for users.
- Author in a project. Create or import keys, choose a main language, and add the languages your app needs.
- Review the draft. Check wording, placeholders, plurals, and any audience-specific variants before publishing.
- Deliver to the application. Sync locale files through the CLI or export, or let a supported SDK fetch published text at runtime.
The core concepts
| Concept | What it means |
|---|---|
| Organisation | A team workspace with members, permissions, and projects. |
| Project | A collection of translation keys, languages, context, variants, and OTA Publish IDs for an app or product. |
| Translation key | The stable identifier your code uses to look up a message. |
| Draft and publication | The editor holds your current draft. Publishing creates the content available for runtime delivery. |
| Variant | An audience-specific override of Main text, such as wording for a brand, plan, or experiment. |
| API key and OTA Publish ID | API keys authenticate management and sync. Read-only OTA Publish IDs connect an SDK to a project. |
Choose your SDK
React
Add OTA delivery to an i18next app while keeping native resources, translation hooks, and language switching.
React Native
Connect native i18next rendering to published translations, persistent cache, and runtime variants.
Angular
Use the ngx-translate or Transloco adapter with your existing loader, native configuration, and reactive translation pipes.
Flutter
Keep generated AppLocalizations calls and add published translation values, runtime languages, and revision-driven rebuilds.
Android
Use ReRune with native Android resources in Compose or Views, including explicit refresh when published text changes.
iOS
Deliver text through native Foundation localization with SwiftUI revision observation or UIKit rebinding.