# App store localization Human Guide

## What This Is For
When the user wants to localize their App Store listing for international markets. It gives the agent a clearer input/output frame for app store localization: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the App store localization agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for app store localization.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the App store localization guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Check for `app-marketing-context.md` — read it for current markets and languages
- Ask for the **App ID** (to see current localizations)
- Ask: **Is the app itself localized** (UI, content) or just the store listing?
- Ask: **Which markets** are they considering?
- Ask: **Budget** — professional translation or AI-assisted?
- [ ] **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

## Decision Points And Nuance
The original skill emphasizes: Initial Assessment, Market Prioritization, Tier 1 Markets (highest ROI for most apps), Tier 2 Markets (good potential), How to Choose, Localization Checklist, Metadata Localization, Critical: Keywords Are NOT Translations, Cultural Adaptation, Localization Workflow.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Provide context: "This is an App Store title, must include [keyword]"

## Copy-And-Paste Prompt
```text
Use the App store localization human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the eronred/aso-skills skill entry for `localization`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# 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 |
|---------|--------------|