Most ASO guides are written for teams with a growth manager, a paid tool subscription and a design department. If you are a solo developer or a two-person studio, you need something different: a short list of changes you can make between lunch and dinner, ship with your next build (or without a build at all), and measure inside App Store Connect and Google Play Console.
This guide collects the app store optimization tips for indie developers that actually move downloads when nobody is spending money on ads. Every item below is free, every item can be done alone, and most of them only touch metadata, which means no review queue and no release risk.
Why indie ASO is a different game
Big apps win on brand searches and paid user acquisition. You are not competing there. Your traffic comes from three places:
- Search: someone types “habit tracker” or “split bill” and scrolls past the top three paid slots.
- Browse: the store surfaces you in a category list, a “you might also like” row, or an editorial collection.
- Referral: someone sends your link from Reddit, Product Hunt, a newsletter or a friend.
Search is where metadata wins. Referral and browse are where the icon, first screenshot and rating win. The eleven actions below cover both sides, and they are ordered by effort to impact ratio, not by how impressive they sound.
The afternoon checklist at a glance
| Change | Time | Needs a build? | Typical impact |
|---|---|---|---|
| Rewrite title with a keyword | 20 min | No | High on impressions |
| Rewrite subtitle / short description | 20 min | No | High on impressions and taps |
| Clean the iOS keyword field | 30 min | No | High on long tail |
| First three screenshots | 60 min | No | High on conversion |
| Icon A/B test | 90 min + wait | Icon variants in build (iOS) | Medium to high |
| Smart review prompt | 45 min | Yes | High on rating and ranking |
| Metadata-only localization | 2 h per batch | No | High on new markets |

1. Put your main keyword in the title, not your brand poetry
The title is the single heaviest ranking field on both stores. Apple gives you 30 characters, Google Play gives you 30 characters. A brand name alone wastes two thirds of that.
Pick one head keyword that describes the job your app does, and attach it to your brand with a colon or a dash.
Before and after
| Field | Before | After |
|---|---|---|
| App Store title | Lumen | Lumen: Habit Tracker |
| Play title | Lumen – Be Your Best Self | Lumen Habit Tracker & Goals |
Rules worth following:
- Brand first if anyone already searches your name, keyword first if nobody does.
- No “best”, “free”, “#1”, “top”. Apple and Google strip or reject promotional words and they rank for nothing.
- Check what the title looks like truncated on a phone. Roughly the first 12 to 14 characters survive in search results, so do not bury the keyword at the end.
- Do not stuff. “Habit Tracker Routine Goal Streak” reads like spam and hurts tap-through.
2. Treat the subtitle and short description as a second title
On iOS the subtitle is 30 characters and it is indexed. On Google Play the short description is 80 characters and it is indexed too. Both are visible to the user, so they have to do double duty: rank and convince.
Before and after
| Field | Before | After |
|---|---|---|
| iOS subtitle | The best way to improve | Daily routine & streak planner |
| Play short description | Lumen helps you become the person you always wanted to be. | Build habits with a simple daily checklist, streaks, reminders and weekly progress. |
Never repeat a word that is already in the title. The store indexes title and subtitle together, so duplication burns characters that could be carrying a second keyword.

3. Use the iOS keyword field like a budget, not a brain dump
The 100 character keyword field on iOS is invisible to users and still one of the most wasted assets in indie listings. Here is the discipline that gets the most out of it. It is argued more carefully on upptic.com.
- Separate with commas only. No spaces after commas, they cost characters.
- Single words, not phrases. The store builds combinations itself. “habit,tracker” can rank for “habit tracker”.
- Never repeat words already used in your title, subtitle or developer name. They are already indexed.
- Skip plurals in most cases, and skip your category name, which is indexed automatically.
- Skip competitor brand names. You will get rejected or, worse, legally contacted.
- Add adjacent intent words: what problem, what context, what moment. “morning”, “sober”, “water”, “gym”, “study”.
Before and after
Before (wasteful): habit, habits, tracker, tracking, app, best, free, daily, routine, productivity
After (dense): routine,streak,checklist,goal,ritual,reminder,discipline,journal,mood,water,gym,study,sober,morning
Where do the words come from if you have no paid tool? Mine them for free:
- App Store and Play search autocomplete, typed on a real device, in the market you care about.
- Your own review text and support emails. Users describe your app in the words they search with.
- Reddit threads and forum posts where people ask for an app like yours.
- Google Play Console’s search terms report, which shows the real queries that led to your listing.
- App Store Connect’s App Analytics, which gives you top search terms on recent iOS versions.
4. Write the Google Play long description for humans with keywords sprinkled in
Google Play indexes the full 4000 character description. That does not mean you should pack it. Aim for your main keyword around three to five times, plus natural variants, in a structure people can actually scan:
- First 2 lines: the promise, containing the head keyword.
- A bulleted feature list with secondary keywords inside the bullets.
- A short “who it is for” block with use-case phrases (“for students”, “for shift workers”, “for ADHD routines”).
- A closing line with your support contact, which quietly improves trust.
On iOS the description is not indexed, so write it purely for conversion and put all keyword effort into title, subtitle and keyword field.
5. Fix the first three screenshots before you touch anything else visual
Most users never scroll your gallery. On iPhone search results, the first one to three portrait screenshots are visible without tapping. That set is your real landing page.
Before and after captions
| Slot | Before | After |
|---|---|---|
| 1 | Welcome to Lumen | Track every habit in one tap |
| 2 | Dashboard | Streaks that survive a bad day |
| 3 | Settings & more | Reminders at the right moment |
Practical rules: caption text at least 60px tall at export size, maximum six words, one benefit per frame, and a consistent background colour so the three frames read as one banner. If you have a 15 to 30 second app preview video, add it, but make the first 3 seconds show the product in use rather than a logo animation.

6. Test your icon, because it decides whether anyone reads your title
The icon is the only asset that appears in search results, browse rows, charts and referral links. Both stores give indies free testing infrastructure:
- iOS Product Page Optimization: up to 3 treatments against the original, split by traffic percentage. Icon variants must be shipped inside the binary, so plan them one release ahead.
- Google Play store listing experiments: icon, screenshots, short and long description, run from the Console without a new release.
What to test first, in order:
- A single bold shape versus a detailed illustration. Detail disappears at 60px.
- Background contrast: light background versus dark background. Many lists are viewed in dark mode.
- Symbol choice: literal object versus abstract mark. Literal usually wins for utilities, abstract for social and creative apps.
Do not test icon and screenshots in the same experiment, and do not stop a test early because day two looks promising. For small apps, give a test at least 7 days or a few hundred conversions per variant, whichever comes last. If your traffic is too small for statistical significance, test with a cheap substitute: post three icon mockups side by side in a relevant subreddit or Discord and ask which app people would tap. It is not perfect data, but it beats guessing.
7. Ask for reviews at the moment of success
Rating is both a conversion lever and a ranking input. The difference between 4.2 and 4.7 stars is visible in tap-through rate on almost every indie app that measures it.
The implementation is 20 lines of code. The strategy is the part that matters:
- Trigger after a completed positive action, not on launch. Finished a workout, exported a file, hit a 7 day streak, completed a first project.
- Require a minimum engagement threshold: at least 3 sessions and 2 days since install.
- Respect the system limits (iOS allows the native prompt a maximum of 3 times per 365 days per user) and never ask twice in a session.
- On Android, use the In-App Review API and check the quota behaviour rather than assuming it displays.
- Never gate: asking “do you like the app?” and routing unhappy users away from the store violates both stores’ rules.
Pair this with a visible in-app support path (a “Report a problem” item in settings that opens an email). People who can complain privately leave fewer one-star reviews publicly.
8. Reply to every review, especially the bad ones
Replies are free, they take ten minutes a week, and they do three things: they often convert a one-star into a three or four star update, they show prospective users that the developer is alive, and on Google Play your replies are part of the listing page content.
A usable template:
Thanks for the detail, that sync bug hit accounts created before the 3.2 update. It is fixed in 3.4, which is live now. If it still happens, email support at your domain and I will look at your logs personally.
Specific, dated, no corporate voice. That is the indie advantage, use it. The Ultimate Guide to App Store Optimization covers this in more depth.

9. Localize metadata first, the app second
Full localization is expensive. Metadata-only localization is one of the highest ROI app store optimization tips for indie developers, because each new locale gives you a brand new keyword index in a market where competition is often thinner.
Start with these, in this order, assuming an English app:
| Locale | Why it is worth it |
|---|---|
| English (UK) and English (Australia) | Free extra keyword fields with no translation cost, just different spellings and terms |
| Spanish (Mexico) | On iOS it is indexed in the US storefront alongside English, doubling your US keyword coverage |
| Portuguese (Brazil) | Huge download volume, low competition in many niches |
| German, French, Japanese, Korean | High revenue per user, strong conversion lift from translated screenshots |
How to do it cheaply without producing embarrassing text:
- Draft with machine translation, then pay a native speaker a small fee on a freelance marketplace to review 300 words of metadata. It is usually under 30 dollars per language.
- Do not translate keywords literally. Ask the reviewer what people actually type to find this kind of app.
- Translate screenshot captions too. Translated captions over an English UI still convert better than fully English assets.
- Localize the first three screenshots before localizing the whole gallery.
10. Build custom product pages for every link you share
If you post on Reddit, run a newsletter, or have a TikTok clip about one specific feature, send that traffic to a page that matches the message. iOS custom product pages (up to 35 of them) and Google Play custom store listings let you swap screenshots and text per audience, each with its own URL and its own conversion metrics.
A simple starting set:
- Default page: broadest promise, for search traffic.
- Feature page: one feature, for social or forum links.
- Lapsed or returning user page: what changed since they left.
You get a conversion report per page, which is often the fastest way for a small app to learn which message works before you touch the default listing.
11. Use in-app events and promotional content as free store real estate
In-app events on iOS and promotional content on Google Play are indexed, appear in search and browse, and can be set up in under an hour. For a small app they are one of the few ways to get editorial-style placement without a press contact.
Things that legitimately qualify: a major feature launch, a seasonal challenge, a limited-time unlock, a community event, a content drop. Give each one a keyword-rich name (“30 Day Winter Streak Challenge” beats “Winter Event”) and a clear card image.
Plan one per quarter through 2027 and keep them in a simple calendar. Consistency matters more than scale.

How to measure without a paid ASO tool
Change one thing at a time and watch these four numbers:
| Metric | What it tells you | Which change affects it |
|---|---|---|
| Impressions | Whether you rank for more queries | Title, subtitle, keyword field, localization |
| Tap-through rate | Whether the search result is attractive | Icon, first screenshots, rating, title clarity |
| Page view to install rate | Whether the listing convinces | Screenshots, description, reviews, video |
| Day 1 and day 7 retention | Whether you attracted the right users | Keyword relevance, honesty of your promise |
Two warnings. First, wait at least 2 to 4 weeks after a metadata change before judging, because indexing and ranking shifts are not instant. Second, chasing a keyword that brings users who churn in a day is worse than ranking lower for a precise one.
The five mistakes indies repeat most
- Clever brand name, zero keywords. Nobody is searching for your pun.
- Repeating the same words across title, subtitle and keyword field, wasting half the index.
- Screenshots that show the UI instead of the benefit, with 10px caption text.
- Launching, then never touching the listing again. ASO is a quarterly habit, not a launch task.
- Changing eight things at once and learning nothing from the result.
A realistic 30 day plan for one person
- Day 1: keyword research from autocomplete, reviews and console search terms. Build a list of 30 candidate words.
- Day 2: rewrite title, subtitle, short description and keyword field. Submit.
- Days 3 to 5: redesign the first three screenshots with benefit captions.
- Day 6: ship the smart review prompt in your next build and reply to every existing review.
- Days 7 to 14: localize metadata into English (UK), Spanish (Mexico) and Portuguese (Brazil).
- Days 15 to 30: run one icon experiment, set up one custom product page for your main referral channel, and schedule your next in-app event.
That is the complete loop. Repeat it every quarter, and keep a dated log of each change so you can attribute movement later. A comparable breakdown sits on asotools.io.
FAQ
How long does it take to see results from ASO changes?
Keyword ranking shifts usually start appearing within a few days to two weeks after the store reindexes your listing. Conversion changes such as a new icon or new screenshots show up faster, often within 48 hours, but you still need enough traffic for the numbers to be reliable.
Do I need a paid ASO tool as an indie developer?
Not at the start. App Store Connect, Google Play Console search terms, store autocomplete and your own user reviews cover most of what a small app needs. Consider a paid tool once you are consistently getting thousands of monthly impressions and need competitor keyword data.
Should I put keywords in my Google Play title?
Yes, within the 30 character limit, and keep it readable. Google Play weighs the title heavily, but keyword stuffing can trigger policy issues and hurts tap-through rate. One brand term plus one or two descriptive terms is the safe pattern.
Does the iOS app description affect rankings?
No. Apple does not index the description for search. Write it for conversion and trust, and put your ranking effort into the title, subtitle, keyword field and localized metadata.
How many reviews do I need before ratings start helping?
There is no official threshold, but listings with fewer than roughly 20 to 30 ratings look risky to users and give the stores little signal. Getting past that first cluster of ratings with a well-timed in-app prompt is usually the single biggest early conversion win.
Is localization worth it if my app interface is only in English?
Often yes. Localized store metadata gets you indexed for local keywords and localized screenshots lift conversion even when the app itself is English. Just be transparent in the description that the interface is in English so you do not collect one-star reviews.
How often should I update my app store listing?
Review metadata once a quarter and after every significant feature release. Between those reviews, keep replying to reviews weekly and running one creative test at a time.

