Launching or optimising a new market

Expert: with sources and numbers. Plain: the same, without them, for beginners.

Entering a storefront properly, or fixing one that was entered badly.

Verified 2026-09-18 · 39 days ago both localisation keywords process

When you’d do it

Entering a new storefront; adding a localization inside a storefront you already serve; or fixing a market that was “localized” by translation and never revisited.

What you need before starting

  • A business reason and a rough expectation for the market
  • Someone who uses apps in that language. Not only a translator
  • Apple’s storefront-to-language mapping for the target market, start from 10-11, then confirm against Apple
  • Current metadata exported for your base locale
  • Competitor listings in that storefront
  • Agreement on which tier this market is: full treatment, or correct-and-unembarrassing (00-06)

The steps

1. Decide storefront or localization

A Apple’s localizations reference lists 50 languages and locales, and each storefront has a default language plus additional supported languages: the US supports eight additional, Germany one, India ten. (App Store localizations, verified 2026-09-18)

Check whether the cheapest win is a language inside a storefront you already have, rather than a new country. Often it is. The storefront-to-language lookup is 10-11.

2. Confirm the fallback today

A Where no localization matches, the store falls back to the storefront default or your primary language. Same source. Find out what users in that market currently see. It is frequently your base-language listing, and that is your baseline.

3. Research keywords in the target language, from scratch

Not “translate the list and check it”. Start from competitor listings in that storefront, reviews written in that language, store autocomplete with the storefront set correctly, and your own support tickets from that market (30-05).

For CJK, Cyrillic, Greek, Hebrew or Arabic: count what App Store Connect actually accepts in the keyword field before planning around a number (30-06, CONFLICT-004).

4. Write the metadata, per platform

iOS: name, subtitle, keyword field, description. A All set per localization. Version-bound, so it ships with a release (10-09).

Play: A title 30, short description 80, full description 4,000 (Create and set up your app, verified 2026-09-18). Indexed, visible, and written differently (20-08).

5. Localize the first three screenshots at minimum

The captions do most of the work. Swapping caption text over existing artwork captures most of the value (40-07). For RTL markets, the reading order of the sequence reverses.

6. Validate uncertain terms with paid, if the market justifies it

An Apple Ads campaign in that storefront tells you which terms real people type and which convert, before they take metadata space (30-09).

7. Ship, and record the date

iOS with the release; Play through its own review, planning for up to 7 days (20-07).

8. Set a review date

Four to six weeks out. A new market’s first metadata is a hypothesis.

What “done” looks like

  • The storefront’s supported languages are known and the choice is deliberate
  • Keywords researched in-language, not translated
  • Both platforms written separately from one brief
  • First three screenshots localized, at minimum
  • Baseline exported and dated
  • Non-Latin keyword field byte count checked and recorded
  • A review date in the calendar
  • The market’s tier written down

Common mistakes

Translating the keyword field. Produces correct words nobody types.

Treating a language as a market. Spanish in Mexico, Spain and the US are three vocabularies.

Localizing text and leaving screenshots in the base language. The most visible half-done job.

Entering markets you will not maintain. A stale localization is worse than none.

Assuming the non-Latin keyword field holds 100 characters. Unresolved; check it.

Leaving the primary language wrong. It is the global fallback.

In short

Every fact on this page in one line, with its evidence tier, source and verification date, 5 A. Generated from the claim register, so it cannot drift from the page above.

A Apple's App Store localizations reference lists 50 languages and locales for app metadata, including Croatian.
IOS-LOC-001 · verified 2026-09-18
A Each storefront has a default language plus additional supported languages. For example the US storefront defaults to English (US) and additionally supports Arabic, Chinese (Simplified and Traditional), French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico) and Vietnamese.
IOS-LOC-002 · verified 2026-09-18
A The localization a user sees is determined by the App Store language setting for their location, their device language settings, the localizations added to the app, and the app's primary language; where nothing matches, the store falls back to the storefront default or the primary language.
IOS-LOC-003 · verified 2026-09-18
A App name, subtitle, keyword field, promotional text, description and What's New are all set per localization.
IOS-LOC-004 · verified 2026-09-18
A Google Play app name is limited to 30 characters; short description to 80; full description to 4000.
PLAY-MD-001 · verified 2026-09-18

Think your app deserves better?

Send the App Store link.
The audit comes back within two working days, whether you hire us or not.

Free, and we mean it. No card, no call required.