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.

Can I preview draft translations in a running app before publishing?

Yes. Enable OTA staging for the project and opt a development or QA client into staging mode. The client receives saved, enabled draft snapshots on its next sync from a cache kept separate from published content. Production clients stay on the published path by default.

ReRune

iOS localization SDK for native app text updates.

ReRune iOS SDK 1.2.0 delivers the selected variant through native Bundle.main lookup paths, with per-key Main and bundled-resource fallback.

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

Bundled .strings and .xcstrings remain the safe baseline, but app teams need a controlled path for approved text changes after release.

Best fit

iOS teams that want ReRune 1.2.0 through Swift Package Manager, runtime variants, native localization behavior, and OTA update delivery.

How ReRune helps

ReRune keeps iOS OTA delivery tied to project context, dictionaries, language progress, and the same translation workspace used by other product surfaces.

iOS specifics

Native Foundation lookup remains the center of the iOS integration.

ReRune installs through Swift Package Manager and applies published values through targeted Bundle.main localization behavior, while bundled .strings, .stringsdict, and .xcstrings content remains available.

Use native lookup calls

UIKit and SwiftUI code should resolve OTA-aware text through NSLocalizedString(...) or Bundle.main.localizedString(...). The current phase targets the default Localizable table in Bundle.main.

Rebind UIKit or observe SwiftUI revisions

UIKit can subscribe to reRuneRevisionPublisher and rebind visible strings. SwiftUI can attach .reRuneObserveRevision() to views that read NSLocalizedString(...).

Expose cached dashboard languages

reRuneAvailableLocaleDetails combines compiled and successfully applied dashboard locales. Apps can call reRuneSetLocale(...) for an in-app picker and persist that choice themselves.

Respect the current SwiftUI and platform boundary

SwiftUI Text("key"), LocalizedStringKey, and LocalizedStringResource are not intercepted in the current phase. New keys, native system text, Settings language lists, and App Store metadata still require an app release.

SDK technical reference

ReRune for iOS

Ship OTA localization updates and runtime variants in native iOS apps while keeping UIKit and SwiftUI on Apple's localization APIs.

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.0
Requirements: iOS 15+, Swift tools 5.9+, Swift Package Manager

Install command

.package(url: "https://github.com/BasalBit/rerune-ios.git", from: "1.2.0")

View on Swift Package Index Setup guide Runtime behavior Platform notes

README at a glance

Runtime contract

Install with Swift Package Manager and import ReRune in UIKit or SwiftUI
Keep using NSLocalizedString(...) or Bundle.main.localizedString(...) for OTA-aware text
Works with bundled .strings, .stringsdict, and .xcstrings localization assets
Refresh visible UI with reRuneRevisionPublisher or .reRuneObserveRevision()
Select Main or a named translation variant at setup or runtime
Preview enabled drafts in an isolated staging mode before publishing

iOSSwift.xcstringsUIKitSwiftUI

Quick Start

UI stack

SwiftUI quick start

// Swift Package Manager
// https://swiftpackageindex.com/BasalBit/rerune-ios
// Version: 1.2.0

import ReRune

import SwiftUI

@main
struct ExampleApp: App {
  init() {
    reRuneSetup(
      otaPublishId: "replace-with-ota-publish-id",
      variant: ReRuneVariant("customer_acme")
    )
  }

  var body: some Scene {
    WindowGroup {
      ContentView()
    }
  }
}

struct ContentView: View {
  var body: some View {
    VStack {
      Text(NSLocalizedString("title", comment: ""))
      Text(Bundle.main.localizedString(forKey: "subtitle", value: nil, table: nil))
    }
    .reRuneObserveRevision()
  }
}

Native lookup path

Resolve SwiftUI text with NSLocalizedString(...) first, then attach .reRuneObserveRevision() on the visible screen so OTA revisions trigger a redraw.

Current SwiftUI scope

SwiftUI Text("key"), LocalizedStringKey, and LocalizedStringResource are not part of the OTA interception path yet, so resolve the string first and then pass it into Text(...).

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.

Contact the ReRune team

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

Can an iOS app keep using .xcstrings with ReRune?

Yes. ReRune 1.2.0 applies the selected variant through native Bundle.main lookups while bundled .xcstrings remain available as fallback. It does not deliver .xcstrings files as the OTA transport.

Does ReRune replace UIKit or SwiftUI localization APIs?

No. ReRune is designed to work alongside native localization behavior, with bundled resources remaining the fallback when runtime updates are unavailable.

How should SwiftUI read ReRune OTA strings?

Use NSLocalizedString(...) inside the SwiftUI view and attach .reRuneObserveRevision(). Direct Text("key"), LocalizedStringKey, and LocalizedStringResource interception is not supported in the current phase.

Can ReRune add an iOS language that is not compiled in the app bundle?

Yes. After a successful fetch, dashboard-only languages can appear through reRuneAvailableLocaleDetails and can be selected with reRuneSetLocale(...). iOS Settings and App Store language metadata are unchanged.

Which iOS localization resources remain the fallback?

Bundled .strings, .stringsdict, and .xcstrings values remain available through Foundation lookup. The current OTA scope targets Bundle.main and the default Localizable table.

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