/localization-strategy

name: localization-strategy
description: Localization and internationalization strategy for iOS/macOS apps. Covers market prioritization, language tier recommendations, minimum viable localization levels, translation workflows, cultural adaptation, localized ASO, and testing. Use when planning localization, expanding to new markets, deciding which languages to support, or planning translation workflow.
allowed-tools: [Read, Write, Glob, Grep, AskUserQuestion, WebSearch]
last_verified: 2026-07-16
review_by: 2027-06-22
os_version: iOS 27 / macOS 27

Localization Strategy

End-to-end localization planning for Apple platform apps — from market prioritization through translation workflow to localized App Store optimization.

When This Skill Activates

Use this skill when the user:

• Wants to localize their app for new markets
• Asks "which languages should I support?"
• Needs help deciding market expansion priorities
• Wants to plan a translation workflow
• Asks about internationalization (i18n) best practices
• Mentions "localization", "translation", "multi-language", or "global markets"
• Wants to understand localization ROI by language
• Needs cost estimates for translation
• Asks about right-to-left (RTL) layout support
• Wants to localize App Store metadata (title, description, keywords, screenshots)

Process

Phase 1: Market Prioritization Framework

Not all languages are equal. Prioritize by revenue potential, not just speaker count.

Revenue Potential by Language

Based on App Store revenue data and per-user spending patterns:

| Language | Relative Revenue Potential | Why | |----------|---------------------------|-----| | English | Baseline (1.0x) | Largest single market, highest per-user spend | | Japanese | 0.8-1.2x | Extremely high willingness to pay, especially for subscriptions | | Chinese (Simplified) | 0.6-0.9x | Massive volume, growing per-user spend, competitive market | | German | 0.4-0.6x | High per-user spend, values quality and privacy | | French | 0.3-0.5x | Large market across France, Canada, Africa | | Korean | 0.3-0.5x | Tech-savvy users, high app spending per capita | | Spanish | 0.3-0.4x | Huge population, lower per-user spend, growing market | | Portuguese (Brazilian) | 0.2-0.4x | Large market, mobile-first users, growing economy |

**Key insight:** Japanese and German users often pay 2-3x more per user than Spanish or Portuguese users. Volume vs. value is the fundamental tradeoff.

Category-Specific Priorities

App category changes which languages to prioritize first:

| App Category | Prioritize First | Why | |--------------|-----------------|-----| | Productivity / Business | Japanese, German, French | High willingness to pay for tools | | Games | Japanese, Korean, Chinese Simplified | Gaming culture, high IAP spend | | Social / Communication | Spanish, Portuguese, French | Large connected populations | | Health / Fitness | German, Japanese, Korean | Health-conscious, high-spend markets | | Education / Kids | Chinese Simplified, Japanese, Spanish | Education investment culture | | Creative Tools | Japanese, German, French | Creative professional markets | | Finance / Budgeting | German, French, Japanese | Financial discipline culture | | Developer Tools | Japanese, Chinese Simplified, Korean | Large developer populations |

Factors to Evaluate

For each potential language/market, assess:

| Factor | Questions to Ask | |--------|-----------------| | Market size | How many potential users in this language? | | Willingness to pay | Do users in this market pay for apps or expect free? | | Competition level | How many localized competitors exist? Less = more opportunity | | Localization cost | How expensive is professional translation for this language? | | Cultural distance | How much adaptation beyond translation is needed? | | Support burden | Can you handle support inquiries in this language? | | App Store presence | Is the App Store well-established in this market? |

Use AskUserQuestion to gather the user's app category, current markets, and budget constraints before making recommendations.

Phase 2: Language Tier Recommendations

Tier 1 — Highest ROI (Localize First)

| Language | Key Market | Estimated Revenue Lift | |----------|-----------|----------------------| | Japanese (ja) | Japan | +15-30% (high per-user value) | | Chinese Simplified (zh-Hans) | China, Singapore | +10-25% (massive volume) | | German (de) | Germany, Austria, Switzerland | +8-15% (high per-user spend) | | French (fr) | France, Canada, Belgium, Africa | +8-15% (wide geographic reach) | | Korean (ko) | South Korea | +5-12% (tech-savvy, high spend) |

**Recommendation:** Localize into 2-3 Tier 1 languages first. Expected combined revenue lift: 20-50%.

Tier 2 — Good ROI (Localize Second)

| Language | Key Market | Estimated Revenue Lift | |----------|-----------|----------------------| | Spanish (es) | Spain, Latin America, US Hispanic | +5-10% | | Portuguese (pt-BR) | Brazil | +4-8% | | Italian (it) | Italy | +3-6% | | Dutch (nl) | Netherlands, Belgium | +2-4% | | Russian (ru) | Russia, CIS countries | +3-6% |

**Recommendation:** Add Tier 2 after Tier 1 languages prove ROI. Expected per-language lift: 3-8%.

Tier 3 — Volume Play (Localize for Scale)

| Language | Key Market | Notes | |----------|-----------|-------| | Arabic (ar) | Middle East, North Africa | RTL support required — higher dev cost | | Turkish (tr) | Turkey | Growing mobile market | | Hindi (hi) | India | Massive volume, very low per-user spend | | Thai (th) | Thailand | Mobile-first market | | Vietnamese (vi) | Vietnam | Fast-growing app market | | Polish (pl) | Poland | Central European hub |

**Recommendation:** Tier 3 is for apps that already have strong Tier 1 and Tier 2 performance and want maximum global reach.

Phase 3: Minimum Viable Localization Levels

Not every language needs full localization on day one. Start small, measure, then invest.

Level