Common challenge
Bundled .strings and .xcstrings remain the safe baseline, but app teams need a controlled path for approved text changes after release.
Platform localization
iOS localization SDK for OTA .xcstrings updates.
ReRune iOS SDK 1.0.0 delivers approved OTA values through native Bundle.main lookup paths while bundled .strings, .stringsdict, and .xcstrings remain the fallback.
Best fit
iOS teams that want ReRune 1.0.0 through Swift Package Manager, native localization behavior, dashboard review, 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.
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.
ReRune for iOS
Ship OTA localization updates in native iOS apps while keeping UIKit and SwiftUI on Apple's native localization APIs.
- 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()
iOSSwift.xcstringsUIKitSwiftUI
Quick StartView on Swift Package Index
UI stack
SwiftUI quick start
// Swift Package Manager
// https://swiftpackageindex.com/BasalBit/rerune-ios
// Version: 1.0.0
import ReRune
import SwiftUI
@main
struct ExampleApp: App {
init() {
reRuneSetup(otaPublishId: "replace-with-ota-publish-id")
}
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(...).
Questions
Questions teams ask before choosing a localization platform.
Does ReRune support .xcstrings?
Yes. ReRune 1.0.0 applies OTA values through native Bundle.main lookups, supports plain and cardinal plural content, and keeps bundled .xcstrings as fallback.
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.
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 moreAndroid localization SDK for native app text updates.
Use ReRune Android Compose or Views SDK 1.0.1 for OTA app strings with native resource fallback, translation management, and developer sync.
Read moreFlutter localization with OTA updates on top of your existing flow.
Use ReRune Flutter SDK 1.0.0 for OTA localization updates while keeping generated delegates, bundled resources, CLI sync, and AI assistance.
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.