ASO Case Study: How One Indie Health App Rebuilt Its Listing, Step by Step
An ASO case study from one indie health app: the research, the listing rebuild, the localisation, and the rank checks, with clear limits on what a single case can prove.
An **ASO case study** is useful when it shows a sequence of decisions and the evidence behind each one. This case follows one indie health app, BloodSnap, from a rough listing to a set of scored, validated, and localised store pages, with rank checks along the way.
Treat it as a worked example of method. A single app in a single category cannot tell you what will happen to your listing, and this article does not claim that it can.
Key takeaways
- A case study is one data point. It shows the method and the trail, not a promise.
- The most useful changes were the ones that were tied to a scored keyword and a named market.
- Localisation and rank checks were measured separately, so each result had its own evidence.
- The team kept the decisions and the rejected options, which made later changes easier to judge.
- Use the case to choose what to test, then run your own cycle with your own data.
The starting listing
The first listing for BloodSnap was written from the product's own description. It explained the features well but did not match how people search for a tracker in the category. There was no shortlist of phrases and no record of which competitors used which language.
That is a common starting point for indie apps. The product is clear to its builder, and the store listing is written for the builder rather than the searcher.
The research pass
The team mined 35 competitors, expanded roots with store autocomplete, and built a research set of about 1,200 keywords. The scoring pass produced 268 scored keywords with confidence labels. The distribution across recommendations was 20 Focus, 140 Primary, 33 Secondary, 27 Maybe, and 48 Skip for that run.
The Skip group mattered as much as the Focus group. Dropping weak phrases prevented the listing from filling up with terms that looked busy but did not match the product.
The listing change
The new title and subtitle each carried one Focus phrase and one benefit. The description was rewritten around the product's actual workflow, and the keyword field was filled from Primary and Secondary terms. Each field was checked against its limit before it was saved.
| Field | Before | After |
|---|---|---|
| Title | Brand-first, generic | Brand plus a Focus phrase |
| Subtitle | Feature list | One benefit and one Primary phrase |
| Description | Marketing summary | Workflow and proof, written for the searcher |
| Keyword field | Unplanned | Primary and Secondary terms, no repeats |
Localisation and market checks
The Play listing was adapted into 10 locales, with each locale keeping its own title, short description, and description budget. Right-to-left Arabic and Urdu previews were checked in the store layout. A native speaker still reviewed the tone before release.
Live Rank checked keywords on demand across markets. For this app, the checks found live ranks in 13 countries. A title that moved in one market did not necessarily move in another, which is why the checks were kept separate.
The icon review
App Icon Studio compared the BloodSnap icon with eight competitor icons. The icon ranked 3 of 9 with a score of 76, and the review gave written notes on what worked and what did not. Those notes shaped the next round of icon work, but the team tested new art before it went live.
What the case cannot prove
- It cannot predict the rank of a different app in a different category.
- It cannot separate every factor, because several things changed over the same period.
- It cannot guarantee downloads, reviews, or revenue.
- It cannot replace your own competitor set and scoring run.
What to take into your own project
- Mine your own competitors before you change a field.
- Score the list and drop the Skip group from every field.
- Change one layer per cycle and save the baseline.
- Localise only after the core listing is stable.
- Keep the record so the next decision is easier to judge.
Where NewASO fits
NewASO kept this project's research, listings, locales, and rank checks in one local workspace. That is the part of the case that is easy to repeat. The results depend on the app and the market, and the workspace does not decide them. For the process in order, read how to do ASO. For the example walkthrough, read app store optimization examples.
Frequently asked questions
Can I copy this listing for my app?
No. Copy the method, not the words. Your product, category, and competitor set are different, and the phrases that fit BloodSnap may not fit your app.
How long did the case run?
The case follows the sequence of research, writing, localisation, and checks. The exact timing matters less than the record of when each change was made and what was measured.
Should I localise before or after I fix the main listing?
After. A stable base listing is easier to translate and easier to judge. Localising a weak listing copies its weaknesses into every market.