If an iOS app has low downloads, “do more ASO” is too vague to be useful.
The first split is simple:
- Visibility problem: not enough qualified people are seeing the product page.
- Conversion problem: people are seeing it, but the page does not convince enough of them to install.
Those two problems need different fixes. Rewriting keywords will not rescue a vague first screenshot. Redesigning screenshots will not help much if the app is barely appearing for realistic searches.
Start with the funnel
Look at App Store Connect before changing metadata.
If impressions and product page views are low, inspect:
- title and subtitle keyword coverage
- whether subtitle repeats title words
- whether the 100-character keyword field uses realistic long-tail terms
- whether the app is trying to win broad head terms like “fitness,” “notes,” or “timer” too early
If product page views are reasonable but installs are weak, inspect:
- first screenshot promise
- subtitle clarity
- ratings and review recency
- description opening lines
- pricing/trust objections
What visibility problems usually look like
A visibility issue often starts in metadata. The title may be mostly a brand name, the subtitle may repeat the same words, or the keyword field may be filled with broad terms that established apps already dominate.
A better pattern is to make the title/subtitle carry the clearest category and outcome, then use the keyword field as extra building blocks. For example, a focus app might use metadata to support combinations around focus sessions, pomodoro, deep work, and distraction blocking instead of chasing “productivity” alone.
What conversion problems usually look like
A conversion issue often appears in the first five seconds of the product page.
The app may have a clean UI, but the first screenshot only says “Dashboard.” The description may list features but not explain the outcome. The subtitle may be technically accurate but too generic to help a user choose.
A stronger screenshot sequence tells a story:
- outcome users want
- how the app creates it
- trust/privacy/proof
- useful secondary benefit
- best product moment
Real report pattern from ASO Playbook
In one generated ASO Playbook report for a focus timer app, the score moved from 71 → 86 and the report included 56 keyword rows. The useful part was not a magic ranking promise. It was the diagnosis: tighter title/subtitle intent, a keyword field built around realistic combinations, and screenshot copy that made the first-frame promise clearer.
That is the loop indie founders need: identify the weakest link, rewrite that part, then measure again.
Quick checklist
Before you rewrite everything, ask:
- Are impressions low, or are installs low after views?
- Does the title include a category or intent word a user would actually search?
- Does the subtitle add new meaning, or repeat the title?
- Is the keyword field using all 100 characters without wasting repeats?
- Does screenshot #1 explain the outcome at thumbnail size?
- Does the description answer the buyer’s real objection in the first few lines?
If you want a concrete teardown, paste your App Store URL into ASO Playbook or view the focus timer report here: https://asoplaybook.ai/report/6404e5e9-5390-4b71-bb42-c642c173b711
Top comments (0)