Most ASO work fails because it starts in the wrong place.
Agencies and in-house teams open the keyword tool first. They re-shoot the screenshots. They A/B test the subtitle. They do all of it before answering the only question that matters: when someone taps into the listing, do they understand what this app actually does within four seconds?
If the answer is no, no amount of ranking buys you installs. Worse, both the App Store and Google Play punish listings with high impressions and low taps-to-install. Better keywords on a confusing listing is how you lose rankings on purpose.
Our stance when a founder asks us about ASO: before you buy keywords, fix the one-sentence promise. Then test the first screenshot. Everything else is seventh on the list.
ASO is a conversion problem, not a ranking problem
Ranking matters. But ranking is the second half of the equation. The first half is the listing's conversion rate — the percentage of people who see the icon, read the subtitle, and tap through to install.
Both stores run that math constantly. In App Store Connect it appears as product page views to downloads. In the Google Play Console it appears as store listing conversion rate. Both drive discovery. A listing with a 25% conversion rate from a cold tap gets more search surface than a listing with a 6% conversion rate on the same keyword.
So the usual ASO workflow — rank first, convert later — is backward. You cannot rank your way out of a confusing listing. You can convert your way into better rankings.
The thing nobody fixes first: the one-sentence promise
Open your app's current App Store or Play Store listing. Read the subtitle. Then read your app's name. Then read the first screenshot caption.
If the three answers together don't tell someone who has never heard of your product (a) what it does, (b) who it's for, and (c) why they'd open it this week — the keyword list is not the problem.
This is where most ASO engagements go sideways. The founder knows the product inside out. The agency specializes in keyword research. Nobody is responsible for the sentence a stranger reads at 11pm on a train while deciding whether to install.
Fix that sentence. Not the keyword list. The sentence.
Then test it in the subtitle (30 characters on the App Store) or the short description (80 characters on Google Play), on the first screenshot caption, and in the first line of the description. Measure the install-to-impression ratio in your console before and after. If it moves, you had a positioning problem. If it doesn't, now you can spend money on keywords and know they will pay off.
The strongest counter-argument — and why I still hold the position
The strongest version of the ASO-first argument: "Ranking is the funnel entry. If I don't rank, I don't get impressions, and conversion rate on zero impressions is irrelevant."
This is true at launch and only at launch. The first wave of impressions comes from category browse, your paid ads, your newsletter, your TestFlight list, your social links. That first wave sets your conversion baseline, and that baseline sets how aggressively the algorithm serves your listing in search.
Rank into a bad listing and you waste the first wave. Rank into a tight listing and the second wave is cheaper to buy, and the third wave starts arriving organically. This is why apps with narrow positioning and small ASO budgets routinely out-rank well-optimized apps with vague positioning — the algorithm rewards the conversion, not the keyword density.
I still hold the position after hearing the counter-argument. If anything, the counter-argument makes the case stronger: your first ASO dollar should go to the sentence, because every subsequent dollar depends on it.
You cannot rank your way out of a confusing listing. You can convert your way into better rankings.
What actually moves installs, in order
Here is the only ranked list this post contains, because it is the one list that matters:
- The subtitle or short description — the 30- or 80-character line a stranger reads first.
- The first screenshot and its caption — read before anyone taps "more".
- The app icon — the single biggest conversion lever on both stores.
- The first screenshot's secondary caption and the first paragraph of the description.
- The next two screenshots.
- Keyword fields (App Store) and short description keywords (Play Store).
- The long description, promo text, and seasonal updates.
- Localized store listings for the top two non-English markets you have traction in.
Items 1 to 5 are positioning. Items 6 onward are traditional ASO. The order reflects how both stores actually weight listing elements for conversion today, not how most agencies prefer to invoice.
Why both stores punish bad ASO work
Both the App Store and Google Play run on an impression-to-install ratio that is harder to see than ranking but more consequential. A listing that gets 10,000 search impressions and 150 installs is treated differently from a listing that gets 2,000 impressions and 150 installs. The second gets served more aggressively, because its ratio is better.
Pouring keyword budget into a weak listing is how you train the algorithm to show your app less. Impressions without installs are an algorithmic penalty, not just wasted spend. This is also why we treat App Store review discipline and the listing itself as the same workstream — both are about what the store sees before it decides how much to serve you.
Over-optimizing for broad keywords usually hurts the same way. "Fitness app" has a hundred times the search volume of "cardio recovery for runners over 40," but the narrower keyword will outperform the broad one on your conversion rate — and over three months that compounds into better ranking on the broad term too.
Where App Store and Play Store ASO actually differ
Short version — the strategic logic is the same, the tactical levers are not:
- App Store Connect uses a dedicated 100-character keyword field hidden from users. Google Play Console has no keyword field; keywords are inferred from the short description, long description and title.
- Google Play weights the long description more than Apple does. Spend time there if you're Play-first.
- Apple weights the subtitle more than Google weights the short description.
- Both stores now re-rank on-device for the specific user. Your real competition for a given install is not the top-ranked app, it's the app the algorithm thinks that specific user prefers — which brings us back to conversion.
The platform differences are tactical. The positioning problem is identical on both.
Our honest recommendation
If you're pre-launch, write the sentence before you book an ASO engagement. If an agency is willing to work on the subtitle, first screenshot and app icon before touching keywords, hire them. If they want to start with the keyword matrix, you've already learned something about their process — same way you learn something from how an agency answers the first AI question.
If you're post-launch with flat installs, open App Store Connect and Play Console. Look at impressions-to-installs over the last 90 days. If that ratio is under 10%, no keyword work will save you. Fix the first screenshot and subtitle. Measure again. Then spend the ASO budget.
If you're hiring a studio to do ASO as part of a mobile build, make sure the brief references the product's one-sentence promise. We treat it the same way we treat the decisions that live in a serious mobile scoping conversation — the positioning answer upstream decides whether the downstream work pays off.
FAQ
What is App Store Optimization (ASO) and does my app actually need it?
ASO is the practice of improving how your app ranks and converts in the App Store and Google Play Store. Every published app needs some ASO because both stores weight listing conversion rate — the share of impressions that become installs — into their discovery algorithms. The question is which part of ASO to spend on first.
Why do most ASO campaigns fail to grow installs?
Because they start with keywords instead of positioning. If your app's subtitle, first screenshot and app icon don't tell a stranger what the app does in four seconds, better keywords buy you worse rankings — both stores demote listings that attract impressions without installs. The first ASO fix is the one-sentence promise, not the keyword matrix.
Should I invest in ASO before launch or after?
Both — but in different forms. Pre-launch, invest in the subtitle, the app icon, and the first screenshot. These set your conversion baseline from the first wave of impressions and shape how aggressively the store serves your listing later. Post-launch keyword optimization only pays off on top of a listing that already converts.
Is ASO different on the App Store vs the Google Play Store?
The strategic logic is identical; the tactical levers differ. The App Store has a dedicated 100-character keyword field, weights the subtitle, and relies less on the long description. Google Play has no keyword field; it infers keywords from the title, short description and long description, and weights the long description most heavily. The positioning problem is the same on both.
Can an agency do ASO for me, or does it have to be in-house?
An agency can run ASO, but only if the brief leads with positioning rather than keyword research. If the agency's first deliverable is a keyword matrix, they will not fix the subtitle, the first screenshot, or the icon. If their first deliverable is a draft of the one-sentence promise, they understand the order the stores actually reward.
Rewriting your App Store listing before you spend on keywords? Book a free 30-min call →
