Localization
Expand an indie mobile app to international App Store markets with prioritized locales and listing localization strategy.
Overview
Localization is an agent skill for the Launch phase that plans App Store international expansion, market prioritization, and listing localization for mobile apps.
Install
npx skills add https://github.com/eronred/aso-skills --skill localizationWhat is this skill?
- Initial assessment: App ID, UI vs listing-only localization, target markets, and translation budget
- Tier 1 market prioritization table with App Store locale codes (en-US, de-DE, ja, ko, and others)
- Explicit handoffs to keyword-research and metadata-optimization for market-specific keywords and copy
- Reads app-marketing-context.md when present for current languages and markets
- Strategy distinguishes full app localization from store-listing-only expansion
- Tier 1 prioritization table covers 7 major App Store markets with locale codes
Adoption & trust: 1.7k installs on skills.sh; 1.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want more countries on the App Store but lack a prioritized market list and a clear plan for listing vs in-app localization within your budget.
Who is it for?
Indie iOS or Android developers with a live or near-live listing who are choosing the next 2–5 countries to localize.
Skip if: Web-only products with no app store listing, or teams that only need in-app string files without any store metadata work.
When should I use this skill?
User mentions localization, translate my app, international markets, expand to new countries, localize metadata, or which countries to target.
What do I get? / Deliverables
You get a structured localization assessment and Tier 1–oriented market priorities, with clear next steps toward keyword research and metadata optimization per locale.
- Market prioritization recommendations
- Localization strategy aligned to budget and UI coverage
Recommended Skills
Journey fit
Canonical shelf is Launch because the skill targets App Store metadata and market expansion, not in-app engineering or post-launch analytics. ASO subphase fits international listing localization, locale codes, and store presence—not general web SEO or paid distribution.
How it compares
Use as an ASO expansion playbook alongside keyword-research and metadata-optimization, not as a replacement for professional translators or full product i18n engineering.
Common Questions / FAQ
Who is localization for?
Solo and indie mobile app builders who sell through Apple’s App Store and need a practical international rollout plan for listings and markets.
When should I use localization?
During Launch when you plan ASO for new locales—after validating the app, before or while translating metadata for Germany, Japan, Korea, or other Tier 1 markets, and whenever you ask which countries to target next.
Is localization safe to install?
Treat it like any third-party agent skill: review the Security Audits panel on this Prism page and confirm the package source before running it in a repo with secrets or production keys.
SKILL.md
READMESKILL.md - Localization
# App Store Localization You are an expert in App Store internationalization and localization strategy. Your goal is to help the user expand to new markets by localizing their App Store presence effectively. ## Initial Assessment 1. Check for `app-marketing-context.md` — read it for current markets and languages 2. Ask for the **App ID** (to see current localizations) 3. Ask: **Is the app itself localized** (UI, content) or just the store listing? 4. Ask: **Which markets** are they considering? 5. Ask: **Budget** — professional translation or AI-assisted? ## Market Prioritization ### Tier 1 Markets (highest ROI for most apps) | Market | Language | App Store Code | Notes | |--------|----------|---------------|-------| | United States | English | en-US | Largest market | | United Kingdom | English | en-GB | Easy win if US is done | | Germany | German | de-DE | Largest EU market | | Japan | Japanese | ja | High ARPU, competitive | | France | French | fr-FR | Large EU market | | South Korea | Korean | ko | High smartphone penetration | | China | Simplified Chinese | zh-Hans | Massive but complex (needs ICP) | | Brazil | Portuguese | pt-BR | Largest LATAM market | | Canada | English/French | en-CA/fr-CA | Easy win | | Australia | English | en-AU | Easy win | ### Tier 2 Markets (good potential) Spain (es-ES), Italy (it), Netherlands (nl), Sweden (sv), Russia (ru), Mexico (es-MX), India (en-IN/hi), Indonesia (id), Turkey (tr), Saudi Arabia (ar-SA) ### How to Choose Evaluate each market on: | Factor | Weight | How to assess | |--------|--------|--------------| | Market size | 30% | iPhone user base in country | | Competition | 25% | How many localized competitors? | | Effort | 20% | Translation complexity, cultural distance | | Revenue potential | 15% | ARPU in the market | | Strategic fit | 10% | Does your app solve a local need? | ## Localization Checklist ### Metadata Localization For each target market: - [ ] **Title** (30 chars) — Localized with market-specific keywords - [ ] **Subtitle** (30 chars) — Localized with local keywords - [ ] **Keyword field** (100 chars) — Completely new research per market - [ ] **Description** (4000 chars) — Translated and culturally adapted - [ ] **Promotional text** (170 chars) — Localized for local events/seasons - [ ] **What's New** — Translated for each update - [ ] **Screenshots** — Text overlays translated, culturally appropriate imagery - [ ] **App Preview Video** — Subtitles or localized version ### Critical: Keywords Are NOT Translations **The biggest localization mistake:** Translating English keywords directly. Instead: 1. Run `keyword-research` for each target market separately 2. Understand how locals search (different terms, different intent) 3. Use local autocomplete suggestions 4. Check what local competitors use in their metadata **Example:** - English keyword: "budget tracker" - German: "Haushaltsbuch" (household book) — NOT "Budget Tracker" - Japanese: "家計簿" (household ledger) — completely different concept - Spanish: "control de gastos" (expense control) — different framing ### Cultural Adaptation | Element | What to check | |---------|--------------| | Screenshots | Currency symbols, date formats, number formats | | Colors | Cultural color associations (red = luck in China, danger in West) | | Imagery | Diverse representation, culturally appropriate | | Tone | Formal vs informal varies by culture | | Features | Highlight features relevant to local needs | | Social proof | Use local press, local user counts if possible | |