Continuous delivery

OTA localization updates without making every copy fix a release.

ReRune connects approved runtime text delivery across Flutter, Android, iOS, React, and React Native while keeping dashboard review, CLI/API sync, and bundled fallback in the same flow.

ReRune dashboard showing localization workspace activity and project status
ReRune projects list showing real localization projects in a workspace
ReRune project keys view for managing software translation keys
ReRune OTA demo mobile app landing screen with live localization status
ReRune OTA demo mobile app story screen showing runtime translation content

Common challenge

App-store release cycles are too slow for every copy fix, translation refinement, or newly supported language.

Best fit

Flutter, Android, iOS, React, and React Native products that need reviewed text delivered safely at runtime.

How ReRune helps

ReRune treats OTA as one delivery option inside the localization platform, not a detached runtime patching tool.

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
rerune

Connect the project

Create the project config and connect the repository to its ReRune workspace.

rerune --pull

Pull approved updates

Bring current dashboard translations into the app or its build workflow.

rerune --push

Push local changes

Send local translation updates back to ReRune for the team to manage and publish.

ReRune for Flutter

Add OTA localization updates on top of your generated Flutter localizations without changing how widgets read translated strings.

  • Layers server-published translations over AppLocalizations
  • Works across mobile, web, and desktop from one setup
  • Generate config with dart run rerune and keep your existing API
  • Check for updates on start or trigger refresh manually at runtime
AndroidiOSWebmacOSLinuxWindows
Quick StartView on pub.dev

setup

dependencies:
  rerune: ^1.0.0

flutter gen-l10n
dart run rerune

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();

  await ReRune.setup(
    otaPublishId: 'your-ota-publish-id',
    localizations: reRuneAppLocalizationsConfig,
  );

  runApp(const MyApp());
}

MaterialApp(
  localizationsDelegates: ReRune.localizationsDelegates,
  supportedLocales: ReRune.supportedLocales,
);

Why it feels lightweight

ReRune plugs into the standard Flutter localization flow, so your UI can keep using the same generated getters while published texts update in the background.

Main runtime APIs

Use ReRune.checkForUpdates(), listen to ReRune.onFetchedTextsApplied, or wrap screens with ReRuneBuilder when you want update-aware UI.

Questions

Questions teams ask before choosing a localization platform.

Which ReRune platforms support OTA localization updates?

ReRune supports OTA workflows for Flutter, Android, iOS, React, and React Native through their public SDK integrations.

Are OTA updates a replacement for normal localization files?

No. OTA updates add a runtime delivery layer for approved text. Bundled files and native or framework localization remain important for fallback and baseline behavior.

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.

One 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.