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.
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.
When you'd do this
Opening in a new shopping centre entirely, adding a language inside a country you already serve, or going back to fix a branch that was only ever translated once and never revisited since.
What you need before starting
- An actual business reason, and a rough sense of what to expect
- Someone who genuinely uses shops in that language day to day, not only someone who can translate words
- Which languages that particular country's branch actually supports
- Your current shopfront, exported, from your home country
- What rivals' branches in that country actually look like
- Agreement on which tier this country gets: full attention, or simply correct and unembarrassing
What to actually do
First, decide whether you need a whole new branch, or just another language inside one you already have. Every country's branch supports a default language plus a handful of others, and this varies a lot: some support many extra languages, some barely any. Check whether the cheapest win is simply adding a language inside a country you already operate in, rather than opening somewhere entirely new. Often it is.
Then find out what shoppers in that country see today, before you touch anything. Where no language matches, the centre falls back to the country's own default, or to your home language. Find out which one that actually is for this market. It's frequently your home-language shopfront showing up untouched, and that's your real starting point.
Then research your filing words in the local language, entirely from scratch. Not "translate the list and see how it reads". Start from rivals' branches in that country, what local shoppers actually write in reviews, the directory's own suggestions with the country properly set, and your own complaints from shoppers in that market.
For a language written in a very different script, count what your filing-word field actually holds before you plan around any assumed limit. Don't assume it behaves the same as it does in your home language.
Then write the shopfront separately for each centre. On Apple's side: your sign, the line beneath it, filing words, leaflet, all set per country, and all locked to a refit. On Google's side: your sign, pitch line and leaflet, all indexed, all visible, and written differently from Apple's side entirely, this isn't a straight copy across centres either.
Then translate at least your first few window photos, as a minimum. The captions do most of the actual work. Swapping the caption text over your existing pictures captures most of the value without a full reshoot. For a market read right to left, the whole order of the sequence reverses too.
Then, if the country justifies it, check uncertain words with a paid billboard first. A billboard running in that country tells you which words real local people actually type, and which of them convert, before you spend your limited filing-word space finding out the hard way.
Then open, and write down the date. Apple's side ships with your refit; Google's side goes through its own inspection, plan for around a week.
Then set yourself a date to come back and check. A few weeks out. A new country's first shopfront is a guess, not a finished piece of work.
What "done" looks like
- The country's supported languages are actually known, and the choice was made on purpose
- Filing words researched in the local language, not translated
- Both centres written up separately, from one shared brief
- At least the first few window photos translated
- A starting point exported and dated
- The filing-word field's actual local-script capacity checked and written down
- A follow-up date sitting in the calendar
- The country's tier written down somewhere
What tends to go wrong
Translating the filing-word field instead of researching it fresh. Produces perfectly correct words that nobody actually types.
Treating one language as one market. The same language spoken in three different countries is three different vocabularies.
Translating the words and leaving the window photos in your home language. The most visible, most obviously half-finished version of this job.
Opening in countries you won't actually keep maintaining. A stale, abandoned branch is worse than no branch at all.
Assuming a non-Latin filing-word field holds exactly as much as the Latin one does. It's genuinely unresolved, go and check it yourself.
Leaving your home-language shopfront wrong. It's the fallback for the entire world, not just for home shoppers.