ASO Case Study: How One Listing Rewrite Took a Habit App from 41 to 78/100

If you've ever wondered whether ASO changes actually move the needle — or whether audit scores are just vanity numbers — this case study is for you.

StrideHabit is a solo-developer iOS habit tracker. When the developer ran an ASOhack audit in late April 2026, the overall score came back at 41 out of 100. Four weeks later, after five targeted changes, it scored 78 out of 100 — and more importantly, the App Store search impression data backed it up.

This is the full breakdown: what the listing looked like before, what the audit found, exactly what changed, and what happened (and did not happen) afterward. If you are new to app store optimization, read our beginner's guide to ASO first, then come back here for the applied version.

What Was Wrong With the Original Listing?

StrideHabit had been live for about seven months. It had collected 47 ratings averaging 3.8 stars — not great, not terrible. The developer had written the listing at launch, updated it once, and largely left it alone.

Here is what the listing contained at the time of the first audit:

Title: StrideHabit

Subtitle: Your daily habit companion

First paragraph of the description:

"Welcome to StrideHabit! We're excited to help you build better habits. StrideHabit is the habit tracker designed to make your daily routine effortless. Whether you're trying to drink more water, exercise more, or read every day, StrideHabit has you covered."

Screenshots: Six screenshots. The first showed the empty home screen with the placeholder text "Add your first habit." The others showed the settings screen, the habit creation flow, and a calendar view — all with sparse data.

Keyword field: 60 characters used out of 100. The string included the app's own name, plural versions of existing title words ("habits", "trackers"), and spaces between every comma.

This is an extremely common pattern for indie apps. The developer had built something genuinely good and then written a listing that described the app from the inside out — features and UI — rather than from the user's perspective.

The core problems were:

• The subtitle used no searchable keywords. "Daily habit companion" is not a phrase anyone types into the App Store.
• The keyword field wasted roughly 35 characters on duplicates and the brand name (which is already indexed separately).
• The hero screenshot communicated nothing about the value of the app — an empty state tells a potential user what the app looks like before they use it, which is the least interesting moment.
• The description opened with a welcome paragraph, burying any persuasive content below the fold.
• Review prompts fired at first launch, when the user had not yet experienced any value.

What Did the ASOhack Audit Find?

Running the listing through ASOhack's ASO audit tool produced a category breakdown that made the priorities concrete:

The two lowest scores — Conversion (28) and ASO metadata (38) — pointed directly at the listing itself. Ads readiness (35) was low partly because the hero screenshot would perform poorly as a Custom Product Page asset. Technical scored highest because the app had no crashes, a reasonable binary size, and supported current iOS versions.

The audit flagged six specific issues in priority order:

1. Subtitle contains zero search-intent keywords
2. Keyword field is 40% wasted capacity with duplicates and the brand name
3. Hero screenshot shows empty/onboarding state rather than peak value moment
4. Description first sentence is a welcome message, not a benefit statement
5. Review prompt timing fires at first open before any value is delivered
6. No keyword overlap with top-three competitors in the "habit tracker" category

That list became the work order.

The 5 Changes We Made (and Why)

The developer made changes in the priority order the audit suggested. Nothing was done simultaneously — each change was isolated so its impact could be attributed correctly.

1. Subtitle: From Generic to Searchable

Before: Your daily habit companion After: ADHD habit tracker + streak

This was the highest-leverage change available. The subtitle is one of the most heavily weighted metadata fields in App Store search ranking. "Your daily habit companion" is a tagline, not a keyword string — it contains no phrase that a user would type when looking for an app like this.

The replacement targets two distinct search intents in 30 characters. "ADHD habit tracker" is a moderately competitive but high-intent phrase — users searching this term are specifically looking for structure-focused tools, which is exactly what StrideHabit's streak mechanics deliver. "Streak" is a core feature term that also appears in competitor reviews and search suggestions.

The developer used ASOhack's keyword density tool to verify neither term was already saturating the title field before committing the change.

2. Keyword Field: Rebuilt From Scratch

Before: 60 characters — StrideHabit,habits,trackers,daily,routine,goals,planner,reminder

After: 98 characters — habit,routine,streak,adhd,productivity,goal,daily,check,morning,mindful,focus,consistency,build

Three problems were fixed simultaneously. First, the brand name was removed — App Store algorithms index the app name separately, so repeating it in the keyword field is a documented waste of character space. Second, plural forms were collapsed to singular ("habits" → "habit"), because the algorithm handles stemming. Third, spaces after commas were removed — the App Store treats the space as a character, reducing effective keyword capacity.

The rebuilt field adds nine net-new keyword concepts in the same 100-character limit. Terms like "mindful," "focus," and "consistency" target adjacent search intents that habit tracker apps rank for but are less contested than the head term "habit tracker" itself.

3. Hero Screenshot: Empty State Replaced With Peak Moment

Before: Screenshot 1 showed the empty home screen with placeholder text and a large "+" button.

After: Screenshot 1 shows a 21-day streak completion screen with a full-screen celebration animation, the streak counter prominent in the center, and a caption overlay reading "Your streak. Your proof."

This is the single change with the most direct impact on conversion rate. A user browsing App Store search results sees the first screenshot before they tap through to the full listing. An empty state communicates nothing about why the app is worth downloading. A 21-day streak celebration communicates the emotional payoff of using the app for three weeks — which is precisely the outcome the user wants.

The developer used ASOhack's Screenshot Lab to test two caption variants before shipping. The "Your streak. Your proof." version outperformed "Never miss a day." in the preview test by a meaningful margin.

4. Description Opening: Welcome Paragraph Replaced With Benefit Lead

Before:

"Welcome to StrideHabit! We're excited to help you build better habits."

After:

"Build any habit in 21 days — StrideHabit uses streak science and smart reminders to make consistency automatic. Designed for ADHD brains and busy schedules. No subscriptions. No fluff."

The rewrite front-loads three things: a concrete outcome (build any habit in 21 days), the mechanism (streak science + reminders), and two credibility markers that address purchase objections (ADHD-friendly, no subscription). The target keyword phrase "habit tracker" appears naturally in the second paragraph. The old welcome paragraph was moved to the end of the long description where it does no ranking harm.

Using a benefit-led opening is one of the most consistent findings across App Store conversion research. Users read an average of the first two sentences of a description before deciding whether to tap "read more" — those two sentences need to do the heaviest persuasion work.

5. Review Prompt: Moved to Streak Milestone

Before: SKStoreReviewController.requestReview() called at app launch after three opens.

After: Review prompt fires when a user completes a 7-day streak for the first time.

Users prompted at first launch have no basis for a positive review. They have used the app for minutes. Moving the prompt to the 7-day streak milestone means only users who have experienced the app's core value — the streak mechanic — are ever asked for a review. This improves both the response rate and the average star rating over time, because the population being asked skews toward satisfied, engaged users.

Results After 4 Weeks

The developer re-ran the ASOhack audit exactly four weeks after the final change shipped. Here is the updated category breakdown:

Beyond the audit score, the App Store Connect data over the same four-week window showed:

• Search impressions: up 34% week-over-week by week four, compared to the four weeks prior
• Product page conversion rate: improved from 2.1% to 3.8% (impressions to download)
• Average rating: unchanged at 3.8 — the review milestone change takes months to move this metric
• New ratings received: 11 new ratings in four weeks, versus 3 in the prior four-week period

What Did Not Change

It is important to be honest here, because ASO case studies often cherry-pick the wins.

Organic download volume did not dramatically transform. The app went from roughly 4-5 organic downloads per day to 7-9. That is meaningful growth on a percentage basis, but it is not the kind of step-change that replaces a marketing budget. The keyword improvements create more entry points, but StrideHabit is competing in a crowded category — Streaks, Habitica, and Done all have years of ratings velocity and significantly more backlinks.

Apple Search Ads still matter. The improved listing means ASA spend now converts better (a lower cost-per-install), but the developer still needs paid traffic to build the reviews and download history that compounds organic ranking over time. A great listing amplifies paid spend — it does not replace it.

The 3.8-star rating is still a ceiling. Users browsing search results see the star rating in the thumbnail. At 3.8, StrideHabit is below the psychological threshold of 4.0 that many users use as a filter. The review prompt change will improve this over the next two to three months, but the listing rewrite cannot fix a rating problem on its own.

What We'd Do Differently

Start the screenshot test earlier. The Screenshot Lab test ran for only five days before the developer picked a variant. A longer test window on a small-volume app produces more statistically reliable data. Two weeks minimum is worth the delay.

Rebuild screenshots 2 through 5 at the same time as screenshot 1. The conversion rate improvement was real, but screenshots 2 through 5 still show low-data UI states. The delta from changing the remaining screenshots is likely another 0.5 to 1 percentage point of conversion — leaving measurable installs on the table.

Run a competitive keyword gap analysis before finalizing the keyword field. The rebuilt keyword field was an improvement, but several high-volume terms that direct competitors rank for — "habit journal," "streak counter," "daily goals tracker" — were missed in the initial pass. A structured gap analysis against the top five competitors would have caught these.

Track custom product page variants from day one. Apple allows up to 35 Custom Product Pages per app. Starting the experiment infrastructure early means you accumulate data faster and can run paid traffic to the best-performing variant.

---

Key Learnings

1. The subtitle is the highest-leverage metadata field most indie developers underuse. Every character should be a keyword a real user types.

2. The keyword field has a hard 100-character limit — wasting any of it on brand names, plurals, or spaces is a documented ranking penalty.

3. Screenshots sell outcomes, not features. Show the user at their best moment, not the app's empty state.

4. Description first impressions are critical. The first two sentences are the only ones most users read before deciding.

5. Review timing is a conversion problem, not just a sentiment problem. Asking at the wrong moment suppresses both volume and quality of reviews.

6. ASO improvements compound over time. The full effect of keyword field changes typically takes 6-8 weeks to fully register in App Store search rankings — four weeks in, the impression lift was still climbing.

---

FAQ

How long does it take for App Store keyword changes to show results?

Apple typically indexes keyword field and subtitle changes within 24-72 hours of a new version being approved. However, ranking position changes — how high you appear in search results for new terms — take longer to stabilize, usually 4-8 weeks, because ranking depends on download velocity and engagement in addition to metadata.

Does changing the subtitle hurt your existing keyword rankings?

Yes, potentially. If your subtitle currently contains terms you rank for, changing it removes those ranking signals. Always check what you currently rank for before rewriting — the keyword density tool at /tools/keyword-density will show you your current term coverage. Only remove terms that have zero or negligible ranking contribution.

Is "ADHD" actually a good keyword to target in a habit tracker app?

For the right app, yes. "ADHD habit tracker" is a specific, high-intent search phrase with meaningful monthly volume and lower competition than head terms like "habit tracker." The key question is whether your app's features genuinely serve that user — StrideHabit's streak mechanics, reminders, and minimal UI do. Targeting a keyword your app cannot deliver on will produce downloads that churn quickly, which damages your ranking signal over time.

What score on the ASOhack audit is "good enough"?

A score above 70 generally means the major metadata and conversion errors have been addressed. Scores above 85 reflect apps that have also done competitive keyword work, localization, and systematic screenshot testing. The score is a diagnostic tool, not a goal in itself — what matters is whether the underlying metrics (impressions, conversion rate, rating) are improving. Start with a free audit at ASOhack to see your current baseline.

How often should you rerun an ASO audit?

After any major metadata update, run the audit again within two weeks. Beyond that, a quarterly audit cadence is sufficient for most indie apps. The competitive landscape shifts as new apps enter the category, so terms that were low-competition six months ago may be saturated today — and new opportunities open up regularly.

---

Ready to see where your own listing stands? Run a free audit at ASOhack and get a scored breakdown across the same six categories. The beginner's guide to ASO covers the foundational concepts if you want to understand the methodology before diving into your own numbers.