Flutter localization with OTA updates on top of your existing flow.

Name: Localize your Flutter app with a coding agent.
Uploaded: 2026-09-07T06:15:14-07:00
Duration: 1 min 6 s
Description: Watch a coding agent move Flutter strings into ARB files, integrate ReRune, and deliver a live text update to the running app.

ReRune Flutter SDK 1.2.1 adds approved OTA text and runtime variants while widgets keep using familiar delegates, supported locales, and getters.

Start localizing See workflow

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

Generated delegates and ARB files cover the app runtime, but teams still need translation coordination, QA, release timing, and runtime update control.

Best fit

Flutter teams that want faster translation cycles, lower localization costs, clear ownership and review of app copy, and approved OTA text updates after the initial SDK integration without waiting for another developer release or App Store and Google Play review.

How ReRune helps

ReRune adds dashboard context, CLI/API sync, AI assistance, and OTA publish IDs around the Flutter localization workflow instead of replacing Flutter conventions.

Flutter specifics

How ReRune layers onto generated Flutter localization.

The Flutter package generates a ReRune configuration from Flutter's localization output, then overlays published messages while widgets keep using the generated AppLocalizations API.

Generate the typed integration

Run flutter gen-l10n, then dart run rerune to create the *.rerune.g.dart config. SDK 1.2.1 also provides prepare-arb for exported ARBs with offset:0. That optional path reads lib/l10n and writes lib/l10n/flutter, which must be the configured arb-dir.

Add runtime languages to the locale list

Fetched or cached dashboard languages join the compiled locales in ReRune.supportedLocales. Rebuild the root localization configuration when a newly fetched language must appear during the current session.

Resolve each message through a fallback chain

Lookup checks the requested OTA locale variants, the published main language, and then the bundled Flutter value. Placeholders and cardinal plurals keep the generated method signatures and use the locale that supplied the OTA value.

Ship structural localization changes normally

Changed text and supported dashboard languages can arrive at runtime. New keys, changed placeholder signatures, platform language metadata, and new application behavior still require code generation and an app release.

Flutter walkthrough1 min

Localize your Flutter app with a coding agent.

Watch a coding agent move Flutter strings into ARB files, integrate ReRune, and deliver a live text update to the running app.

SDK technical reference

ReRune for Flutter

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

Version-pinned guidance from the published package README. Follow the linked README for the complete API and current release notes.

Package: rerune
Current release: 1.2.1
Requirements: Flutter 3.22+, Dart 3.4+

Install command

flutter pub add rerune:^1.2.1

View on pub.dev Setup guide Platform notes Runtime behavior Troubleshooting

README at a glance

Runtime contract

Layers server-published translations over AppLocalizations
Works across mobile, web, and desktop from one setup
Generate the ReRune config; prepare API-exported ARBs when needed
Check for updates on start or trigger refresh manually at runtime
Select Main or a named translation variant at setup or runtime

AndroidiOSWebmacOSLinuxWindows

Quick Start

setup

dependencies:
  rerune: ^1.2.1

flutter gen-l10n
dart run rerune

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

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

  runApp(const MyApp());
}

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

Why it feels lightweight

Keep your generated Flutter localization APIs. If exported ARBs contain offset:0, SDK 1.2.1 can prepare compatible copies before generation. Keep source ARBs in lib/l10n, set arb-dir to lib/l10n/flutter, and run dart run rerune prepare-arb before flutter gen-l10n and dart run rerune.

Main runtime APIs

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

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.

Install the SDK

Connect the supported app runtime to a ReRune publish ID while keeping native or framework localization behavior in place.

Publish approved text

Approve translation changes in the workspace, then publish runtime updates without turning every text fix into a full store release.

Refresh visible copy

Let supported SDK hooks check for updates and refresh text when new approved localization payloads are available.

Keep fallbacks intact

When runtime updates are unavailable, the app keeps reading bundled resources so localization failures do not break the product.

Agent-assisted setup

Run one command. Your coding agent integrates ReRune.

Run the onboarding command from the root of your Git repository. The wizard detects the app and compatible coding agents already installed, then launches the agent you choose to move static UI text into localization, connect ReRune when cloud setup is selected, and validate the result.

Run inside your Git repository

$ curl -fsSL https://rerune.io/onboard.sh | sh

View current script View v1.2.6 Changelog

The script runs locally. ReRune does not receive your source code or list of installed agents.

Run the onboarding command
Start it from the repository root. It stays in the terminal and detects the app, existing localization, and supported coding agents already installed.
Confirm the detected setup
Review the source locale, Git branch, and whether to connect ReRune cloud and add supported OTA delivery. Nothing changes until you confirm.
The agent completes the integration
The selected agent migrates user-facing strings into the app's localization system, connects ReRune when cloud setup is selected, adds supported OTA setup when requested, and runs the relevant validation.

Coding agent integrations

11 integrations: 4 available now, 7 planned.

Claude CodeReady
CodexReady
OpenCodeReady
PiReady
GitHub Copilot CLIPlanned
GoosePlanned
Qwen CodePlanned
Cursor AgentPlanned
Kiro CLIPlanned
Cline CLIPlanned
Factory DroidPlanned

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.

Web apps and browser-based products React web apps with the public OTA SDK Angular apps with ngx-translate or Transloco React Native apps with the public OTA SDK

Flutter apps with the public OTA SDK

Native Android apps with the public OTA SDK Native iOS apps with the public OTA SDK

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.

Questions

Questions teams ask before choosing a localization platform.

Does ReRune work with Flutter localization delegates?

Yes. With rerune 1.2.1, apps select Main or a named variant before runApp(...) and keep using generated delegates, supported locales, and getters.

Can Flutter teams use ReRune without OTA?

Yes. Flutter teams can still use ReRune for project management, translation keys, AI assistance, import/export, and CLI/API sync even when OTA delivery is not part of the release plan.

Does ReRune support Flutter ARB workflows?

Yes. Run flutter gen-l10n, then dart run rerune to generate the ReRune configuration. For exported ARBs containing offset:0, first use dart run rerune prepare-arb with source files in lib/l10n and l10n.yaml pointing at lib/l10n/flutter. Widgets keep using generated AppLocalizations getters and methods.

How are missing Flutter OTA translations handled?

Lookup checks the requested OTA locale variants, the manifest's main language, and then the bundled Flutter value for that message. Missing remote content does not remove the compiled fallback.

Which Flutter localization changes still need an app release?

New keys, changed placeholder signatures, new code paths, and platform or store language metadata still require code generation and an app release. Published values and supported dashboard languages can be delivered within the installed SDK's runtime scope.

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.

Contact the ReRune team

Share an idea, report a problem, or ask for help with ReRune.

Explore next

Keep exploring the localization workflow.

Go deeper into the developer, platform, and delivery workflows connected to this page.

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.

Start localizing Pricing