Common challenge
Cross-platform teams need one localization workflow without giving up control over native release behavior.
Platform localization
React Native localization for cross-platform app teams.
ReRune centralizes React Native app text, translation context, AI assistance, CLI/API sync, and OTA delivery through the public @rerune/react-native package.
Best fit
React Native teams that want shared project context and runtime delivery through the public @rerune/react-native@1.0.0 SDK.
How ReRune helps
ReRune connects the public React Native SDK to the broader app localization strategy: one workspace for web, native, and cross-platform text with approved OTA delivery.
Workflow
From app copy to release-ready localization.
ReRune connects translation management to the delivery path developers already use: dashboard work, AI assistance, CLI/API sync, and OTA updates where a supported SDK is installed.
1
Install the SDK
Connect the supported app runtime to a ReRune publish ID while keeping native or framework localization behavior in place.
2
Publish approved text
Approve translation changes in the workspace, then publish runtime updates without turning every text fix into a full store release.
3
Refresh visible copy
Let supported SDK hooks check for updates and refresh text when new approved localization payloads are available.
4
Keep fallbacks intact
When runtime updates are unavailable, the app keeps reading bundled resources so localization failures do not break the product.
Coverage
App-first does not mean mobile-only.
Start where localization creates release friction, then keep web, mobile, and cross-platform products in one shared workspace as your surface area grows.
Developer delivery
Sync through the CLI. Publish through OTA SDKs.
Use the ReRune CLI locally or in CI/CD to manage project translations, then deliver approved runtime updates through the SDK built for your app.
Companion CLI
Install the ReRune CLI
Use the ReRune CLI to sync, validate, and manage translations right from your terminal. Run syncs in CI/CD or locally whenever you need to push a new language.
Homebrew (macOS/Linux):
brew install BasalBit/tap/rerune- Downloadable builds for macOS, Linux, and Windows
- Uses the API keys you generate in the dashboard
- Fits scripted CI/CD workflows through CLI and API access
reruneConnect the project
Create the project config and connect the repository to its ReRune workspace.
rerune --pullPull approved updates
Bring current dashboard translations into the app or its build workflow.
rerune --pushPush local changes
Send local translation updates back to ReRune for the team to manage and publish.
React Native
@rerune/react-native uses AsyncStorage persistence for iOS and Android while keeping the same i18next rendering path.
React Nativei18nextOTA
Quick Start
@rerune/react-native@1.0.0
npm install @rerune/react-native@1.0.0 i18next react-i18next
import {
createReRuneAsyncStorageCacheStore,
ReRune,
} from '@rerune/react-native'
const cacheStore = createReRuneAsyncStorageCacheStore()One integration flow
Choose the platform package and cache adapter once. The rest of your localization setup and component usage stays aligned across web and native.
- 1
i18next
Keep your existing resources, namespaces, language switching, and fallback rules.
- 2
ReRune.setup(...)
Bind ReRune once with a publishable, read-only OTA ID and the platform cache.
- 3
useTranslation()
Render with normal react-i18next calls; remote values override only the keys they provide.
Shared i18next and ReRune setup
import i18next from 'i18next'
import { initReactI18next, useTranslation } from 'react-i18next'
const resources = {
en: { translation: { headline: 'Bundled headline' } },
de: { translation: { headline: 'Gebündelte Überschrift' } },
}
await i18next.use(initReactI18next).init({
lng: 'en',
fallbackLng: 'en',
defaultNS: 'translation',
resources,
interpolation: { escapeValue: false },
})
export const reRuneClient = ReRune.setup({
i18n: i18next,
otaPublishId: '<READ_ONLY_OTA_PUBLISH_ID>',
defaultLocale: 'en',
bundledResources: resources,
cacheStore,
})
export function Headline() {
const { t } = useTranslation()
return t('headline')
}Questions
Questions teams ask before choosing a localization platform.
Is ReRune React Native OTA support available now?
Yes. React Native OTA integration is publicly available as @rerune/react-native@1.0.0.
Does React Native use the same integration model as React?
Yes. Both bind ReRune.setup(...) to the app's existing i18next instance and keep normal react-i18next rendering. React Native uses its package's AsyncStorage cache instead of the browser cache and usually does not need SSR preload.
What happens if an OTA localization update is unavailable?
Supported SDK flows keep bundled resources as the fallback. Runtime updates add approved text delivery on top of the app's existing localization path instead of replacing the safe baseline.
Explore next
Keep exploring the localization workflow.
Go deeper into the developer, platform, and delivery workflows connected to this page.
OTA localization updates without making every copy fix a release.
Publish approved OTA localization updates through ReRune SDKs for Flutter, Android, iOS, React, and React Native with bundled fallbacks.
Read moreReact localization that stays connected to product delivery.
Add ReRune OTA translations to React with @rerune/react while keeping i18next, react-i18next, bundled fallbacks, language switching, and SSR support.
Read moreApp localization platform that starts with releases, not files.
ReRune is an app localization platform for web, mobile, and cross-platform product teams that need translation management, AI assistance, CLI/API sync, and OTA updates.
Read moreOne workspace
Start with one product workflow and expand from there.
Create projects, manage keys, use AI assistance with context, sync through CLI/API, and publish approved runtime updates when your app uses a supported ReRune SDK.