Keep one translation key
Product code continues to refer to the same key while ReRune stores the Main text and its audience-specific alternatives together.
ReRune product guide
One app. Different text for every test, brand, and plan.
Run A/B tests on app copy, adapt wording for white-label brands, and give Free and Pro users the right message. Keep shared translations in Main and change only the text each group needs.
Published August 27, 2026. Updated September 8, 2026 by the ReRune team.
One key, three outputs
signup.cta- MainFallback
- Get started
- Group A
experiment_a - Start free trial
- Group B
experiment_b - Try it free
Your software selects the test group, brand, or plan. ReRune supplies its text and uses Main for missing overrides.
What is a variant?
One translation key, different messages.
A variant is an alternative value for an existing translation key and language. The project keeps one Main value, then adds named overrides only where an audience needs different wording.
Override only what changes
An A/B test, white-label brand, or Free/Pro plan can reuse the Main catalog and provide custom text only for the keys that differ.
Preserve a reliable fallback
If the active variant has no value for a key or language, ReRune uses Main content instead of leaving the interface without text.
Variants demo30 sec
One key. Different messages.
See how the same app shows different messages for different audiences.
Seven practical uses
Use variants wherever audience changes the wording.
Keep one app and one set of translation keys. Change the wording for the test group, brand, or plan.
A/B testing
Try “Start free trial” for group A and “Try it free” for group B under the same translation key. Use your experiment assignment to select the variant and your analytics to compare results.
White-label apps
Welcome Northstar and Lumen users with their brand’s wording. Keep shared translations in one project and override only brand-specific text.
Free and Pro plans
Show “Upgrade to Pro” to Free users and “Open your workspace” to Pro users. Your app selects the variant from the user’s plan and continues to control feature access.
Customer-specific copy
Show “Contact your account manager” to one customer instead of the shared “Contact support.”
Roles and permissions
Give administrators setup instructions and show members a shorter confirmation for the same action.
Regional requirements
Use region-specific legal or checkout wording within the same language when the requirement is not a locale change.
Partners and resellers
Show a reseller’s support name and contact instructions while the underlying product workflow stays shared.
How it works
Start with Main, then branch only where needed.
The model stays small because every variant inherits the complete Main catalog before its own overrides are considered.
Define project variants
Create variants in project settings with stable names such as experiment_b, white_label_northstar, or plan_pro.
Write Main content
Main remains the required source of truth and the fallback for every supported language.
Add focused overrides
Select a variant in the translation editor and add plain or plural content only for the keys and languages that differ.
Publish together
Published delivery includes Main and its alternatives so the supported runtime integration can select the active value.
Your app selects a variant using its experiment assignment, brand, or subscription plan. ReRune supplies the matching published text and uses Main wherever the variant has no override.
Platform imports update Main translations only. Exports can use Main or one selected variation, with per-language fallback to Main. Published SDK and raw CLI delivery include the stored alternatives.
Choose the right mechanism
Variants solve an audience problem, not a grammar problem.
Keeping these concepts separate makes the translation model easier to author, test, and explain.
Language or locale
Use a language or locale when wording changes because the reader uses English, German, Italian, or a regional language convention.
Plural form
Use plural content when grammar changes with quantity, such as “1 item” and “3 items.”
App context
Your app selects the active variant using its experiment assignment, white-label brand, or subscription plan. ReRune provides the matching text and uses Main when no custom value exists.
Translation variant
Use a variant when the language stays the same but an A/B test group, white-label brand, or subscription plan needs different wording.
Questions
Translation variants, answered.
Contact the ReRune team
Share an idea, report a problem, or ask for help with ReRune.
What is a translation variant?
A translation variant is an alternative value for an existing translation key and language. It is selected by a named project option and falls back to Main when no override exists.
Can ReRune variants support A/B testing?
Yes. Store alternative messages under the same translation key and select a variant using your app’s experiment assignment. Your experiment system handles group assignment and your analytics measure results. ReRune delivers the matching text.
Can I show different text to Free and Pro users?
Yes. Select a variant from the user’s subscription plan to show different upgrade prompts, onboarding text, or support messages. Your app continues to control feature access and billing. ReRune supplies the matching wording.
Do white-label apps need separate translation projects?
Not when the apps share most of their product text. A single project can keep shared wording in Main and store brand-specific overrides only for the keys that differ.
What happens when a variant value is missing?
ReRune uses the Main value for that key and language. This lets variants remain sparse instead of duplicating the complete catalog.
Can a variant contain plural content?
Yes. A variant can contain plain text or supported plural content, provided the language already has Main fallback content for the key.
Are variants included in platform imports and exports?
Platform imports update Main translations only. Exports can use Main or one selected variation and fall back to Main for languages without a valid alternative. Published SDK and raw CLI delivery include stored alternatives.
Continue exploring
Connect variants to the rest of the localization workflow.
App localization platform
Keep shared app text and platform-specific delivery paths in one localization system.
Read the guideDeveloper localization platform
Connect translation management to repositories, automation, and release workflows.
Read the guideOTA localization updates
Publish approved app text through supported runtime delivery paths with bundled fallback.
Read the guidePut variants to work in your app.
Start with an A/B copy test, a white-label brand, or different messages for Free and Pro users. Keep the shared text in Main.
Start free