The foundation
Localization is more than translation.
Translation, internationalization, and localization solve related parts of the same product challenge. ReRune connects translation work to the localized resources and delivery flow used by the product.
Translation
Translation expresses source content in another language while preserving its intended meaning.
Internationalization
Internationalization prepares code, resources, layouts, and formatting logic so the product can support multiple locales cleanly.
Localization
Localization adapts the complete product experience for one locale, including language, formats, visuals, cultural expectations, and delivery.
What ReRune manages
The language layer stays connected from translation key to app update.
ReRune keeps the translation workspace, developer sync, and supported runtime delivery in one product flow.
Keys and translated values
Create or import stable keys, edit values by language, and keep app copy in a shared project.
Languages and coverage
Define project languages, track translation completion, and spot missing values before release.
Context and metadata
Keep descriptions, comments, tags, placeholders, and project context close to the text they guide.
Dictionaries and AI assistance
Guide DeepL and OpenRouter translation actions with project context, preferred style, and reusable product terminology.
CLI, API, import, and export
Move translations between ReRune, platform files, repositories, local scripts, and CI/CD pipelines.
Publishing and OTA delivery
Publish approved text through ReRune SDKs for supported apps while bundled translations remain the fallback.
ReRune workflow
How ReRune moves app copy from workspace to shipped experience.
The workflow keeps translation management, developer sync, and supported runtime delivery connected.
- 01
Create the project and languages
Create a ReRune project, define the source and target languages, and import the platform translation files already used by the app.
- 02
Bring in keys and context
Manage source text, translated values, descriptions, comments, tags, placeholders, dictionaries, and project context in one workspace.
- 03
Translate with governed assistance
Use DeepL or OpenRouter translation actions with project context, preferred style, and dictionaries guiding the output.
- 04
Review values and structure
Inspect language coverage, missing values, metadata, and placeholder checks before translations move into the app workflow.
- 05
Sync with development
Use platform import and export, the ReRune CLI, or API access to move translation updates through local scripts and CI/CD.
- 06
Publish to supported apps
Generate OTA publish IDs and deliver approved text through ReRune SDKs while bundled app translations remain the fallback.
ReRune integrations
ReRune fits the localization model already used by each app.
Each integration preserves its platform resource model while ReRune adds translation management, sync, and supported OTA delivery.
Web and React
i18next JSON resources
The ReRune React SDK adds browser caching and preload support while react-i18next keeps rendering bundled and OTA values.
React Native
i18next JSON resources
The ReRune React Native SDK uses AsyncStorage persistence while the app keeps its existing react-i18next rendering path.
Flutter
ARB and generated AppLocalizations
ReRune layers published values over generated Flutter localizations while widgets keep using their existing getters.
Android
strings.xml
ReRune supports native string lookups in Views and Compose while bundled Android resources remain the fallback.
iOS
.strings, .stringsdict, and .xcstrings
ReRune applies OTA values through native Bundle lookups while Apple localization assets remain the bundled fallback.
ReRune quality controls
Context, structure, and delivery stay close to every translation.
ReRune keeps the information and controls used by app teams inside the same workflow as the translated values.
Context stays with the project
Project context, descriptions, comments, and tags give translation actions more information than an isolated string.
Placeholder checks protect structure
Defined placeholders remain visible and ReRune checks their structure before changed values are saved.
Dictionaries guide terminology
Project dictionaries keep product names, legal wording, and recurring terminology available across languages.
Coverage remains visible
Language completion, missing keys, active integrations, and project readiness stay visible before release.
Developer sync prevents drift
Import, export, CLI, and API workflows keep translation changes connected to repositories and delivery pipelines.
Release delay
Supported ReRune SDKs deliver approved text at runtime so eligible copy changes do not require another full app release.
Localization economics
ReRune addresses the workflow around translation.
Measure direct spend together with coordination, quality rework, and release delay. ReRune brings the app copy workflow into one product and developer flow.
Independent research
Governed AI changes the cost model.
An April 2026 Nucleus Research analysis reports that organizations adopting AI native translation platforms reduced translation spend by 80 to 90 percent. It also describes fragmented enterprise workflows taking two to four weeks from briefing to delivery, with much of the delay caused by coordination.
These findings describe the organizations studied. Build your own case from vendor spend, software cost, internal coordination time, quality rework, and release delay.
Read the Nucleus Research analysisTool and vendor overlap
ReRune combines a translation workspace, AI integrations, developer sync, and runtime delivery so teams can reassess separate tools and handoffs.
Coordination time
A shared project view for keys, languages, metadata, dictionaries, and progress reduces briefing, file exchange, and status chasing.
Quality rework
Project context, dictionaries, metadata, and placeholder checks keep quality controls close to the translated values.
Market access
Reusable keys, terminology, developer sync, and supported OTA delivery make additional app languages easier to operate.
ReRune platform
One localization workflow from translation keys to runtime delivery.
ReRune connects the language workspace to developer tooling and the supported SDK integrations used by web, mobile, and cross platform apps.
What ReRune connects today
- Projects, languages, translation keys, values, and completion visibility.
- Descriptions, comments, tags, placeholders, and project context.
- Dictionaries and preferred style for DeepL and OpenRouter translation actions.
- Platform imports, exports, a dedicated CLI, API access, and CI/CD sync.
- Shared workspaces for product, localization, and engineering contributors.
- Publishing workflows with OTA publish IDs for supported applications.
- React, React Native, Flutter, Android, and iOS SDK integrations with bundled fallback.
ReRune workflow
From workspace to shipped app.
ReRune connects translation keys, values, languages, metadata, placeholders, dictionaries, AI assistance, platform import and export, CLI, API, and publishing in one workspace.
The ReRune SDK ecosystem extends the workflow to React, React Native, Flutter, Android, and iOS with OTA delivery and bundled app translations as fallback.
Common questions
Questions about software localization with ReRune.
See how the broader localization discipline connects to the capabilities available in ReRune.
What is software localization?
Software localization adapts product content for specific languages and regions. ReRune supports the language workflow through translation keys, values, languages, metadata, dictionaries, AI assistance, developer sync, and supported OTA delivery.
What is the difference between translation and localization?
Translation changes content from one language to another. Localization connects that translated content to the product. ReRune manages the translation workspace and the supported delivery paths that move app copy into web and mobile products.
What is the difference between i18n and l10n?
Internationalization, often shortened to i18n, prepares the app to support multiple locales. Localization, often shortened to l10n, supplies the language content for a locale. The app keeps its framework localization model while ReRune manages translation resources and delivery.
When should software localization begin?
Start by creating a ReRune project, defining languages, and importing existing translation resources. Add project context and dictionaries, then connect the CLI, API, or relevant SDK workflow used by the app.
Which files are used for software localization?
ReRune works with JSON based i18next resources for React and React Native, generated Flutter localizations, Android string resources, and Apple localization assets. Each integration preserves the platform resource model while ReRune adds sync and supported OTA delivery.
Can localized app text change without another app release?
Yes. ReRune SDKs can fetch approved text at runtime while the app keeps bundled translations as fallback. Changes to code, new product behavior, and unsupported resource changes continue through the normal release process.
Sources and further reading
Built on platform guidance, ReRune SDK resources, and current research.
These references support the definitions, ReRune integration details, platform resource conventions, and economic context used in this guide.
Across guide to software localization
An overview of software content, context, localization tools, and file based workflows.
Nucleus Research on localization ROI
April 2026 research on governed AI translation, coordination cost, quality, and market access.
Android localization guidance
Official Android guidance for default resources, localized resource directories, fallback, and locale selection.
Apple String Catalog guidance
Official guidance for localizable text, languages, plural variants, and String Catalog workflows in Xcode.
Flutter internationalization guidance
Official Flutter guidance for ARB resources, generated localization classes, placeholders, plurals, and locale resolution.
React i18next documentation
Documentation for loading JSON resources and exposing localized values through React components and hooks.
ReRune Flutter package
The public Flutter package for adding ReRune OTA delivery to generated localization flows.
ReRune Android SDK
The native Android SDK resources for Compose and Views localization updates.
ReRune iOS SDK
The Swift Package Index entry for native iOS localization delivery through Bundle lookups.
ReRune React package
The public React package for i18next integration, browser caching, preload support, and OTA delivery.
ReRune React Native package
The public React Native package for i18next integration, AsyncStorage persistence, and OTA delivery.
Continue exploring
Turn the fundamentals into a working localization system.
Explore the ReRune product workflow, compare platforms, understand OTA delivery, or see the customer experience behind the platform.
Software localization platform
See how ReRune connects translation management with product delivery.
Compare localization platforms
Compare ReRune, Lokalise, Phrase, Crowdin, and Transifex for app teams.
OTA localization updates
See how approved text reaches supported apps with bundled fallback.
R.O.E GmbH customer story
Read how one product team replaced spreadsheet handoffs with a shared workflow.