Why almost everything is done twice

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

The multiplication that makes ASO an operational problem rather than a writing problem, and how to keep it tractable.

Verified 2026-09-18 · 39 days ago both foundations process operating-model

ASO is not hard because any single decision is hard. It is hard because every decision multiplies.

The multiplication

Two platforms. Different fields, different release binding, different evidence base (00-05).

Times localizations. A Every App Store text field is set per localization, and Apple’s reference lists 50 languages and locales. (App Store localizations, verified 2026-09-18) Play listings localize too.

Times surfaces. Search results, product page, charts, editorial, in-app events, custom pages. Each reads different parts of what you wrote (00-02, 00-03).

Times cadence. A iOS indexed text moves only with a release; Play’s largely does not (10-09, 20-07).

Ten markets on two platforms is not twenty pieces of work. It is twenty field sets, on two schedules, measured in two consoles whose numbers do not agree (80-03).

What this does to a team

Three failures follow from the multiplication, and they are the ones worth designing against.

Partial updates. The primary locale gets revised, the others do not. Then the aggregate result gets read as if it were one change, and someone draws a conclusion about the algorithm. This is the most common way ASO measurement goes wrong.

Drift. Nobody can hold twenty field sets in their head. Without an export, the current state of your own metadata becomes unknown, and the next refresh starts by rediscovering it.

Everything at once. Metadata, creative and a release ship together, and nothing can be attributed to anything. You get a number and no learning.

How to keep it tractable

Keep a current export. Every field, every locale, both platforms, dated. Without it you have no baseline, and without a baseline you can measure nothing (runbooks/quarterly-keyword-refresh). At four or five markets this stops being optional. See 98-08.

Separate the two schedules deliberately. iOS indexed text batches to the release train; Play does not have to wait. Running them on one artificial cadence wastes the flexibility Play gives you.

Tier your markets. A handful get real research and localized creative; the rest get correct, unembarrassing metadata. Attempting fifty markets at equal depth produces fifty mediocre ones. Which tier a market sits in is a business decision, record it, and record why.

Change one class of thing at a time. Metadata this release, creative next, or accept that the quarter produces no clean learning. This is the hardest discipline to hold and the one that most determines whether you learn anything (50-03).

Write down decisions, not just changes. Six months on, the useful record is not what the subtitle said. It is why that term was chosen and what was expected to happen.

What goes wrong

Treating ASO as a writing task. The writing is the small part. The operational load is per-locale state, two release cadences, and attribution.

Scaling by adding markets. Each new locale adds permanent maintenance. An unmaintained localization is worse than none, because it is stale text that users still see.

One process for both stores. Guarantees either an iOS release window is missed or Play changes are held for no reason.

No baseline. Then every result is an anecdote, and every explanation is a story.

In short

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

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 App name, subtitle, keyword field, description and What's New cannot be changed on a live app without submitting a new version. A live app is in status Ready for Distribution, which Apple's status reference marks as not editable.
IOS-VER-001 · verified 2026-09-19
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.