ASO Basics for Indie App Developers: The By-Hand Guide

The short answer

App store optimization (ASO) is how you get your app found and installed inside the App Store and Google Play without paying for it. For an indie dev, it comes down to four levers you control by hand: the title and subtitle (where your main keyword lives), the keyword field or long description (where you feed the search algorithm), the screenshots (which decide whether a browser taps install), and the "what's new" note (a free marketing slot most people waste on a changelog). You do not need a paid tool to start. Pick one real keyword your target user would actually type, put it in your title, write your first two screenshots to sell the outcome not the feature, and treat every update note as a tiny ad. Change one thing at a time and wait two to four weeks before you judge it.

The four levers, plain

ASO sounds like a discipline. It's really four fields and a set of images. Here's what each one does.

Title and subtitle. This is the single strongest signal. On the App Store your app name plus subtitle carry the most keyword weight, and on Google Play the title does. So your title should not be just your brand. If you built a habit tracker, "Streak" alone is a wasted title. "Streak: Daily Habit Tracker" tells a searcher and the algorithm what you are. Put your one real keyword here. Not five. One, the one people type.

Keywords (App Store) and long description (Google Play). The two stores work differently, and this trips up first-timers. Apple gives you a hidden 100-character keyword field, comma-separated, no spaces, no repeats. Google has no keyword field at all. Instead Google reads your long description, so you write naturally and make sure your main terms show up a few times without stuffing. Same goal, two different mechanics.

Screenshots. This is where most indie devs lose. Search gets you seen. Screenshots get you installed. The first two are the whole game because that's all a scrolling user sees before deciding. Do not just paste raw UI. Add a short caption on each that names the payoff: "Track every habit in one tap," not a bare screen of your list view. You can build these by hand in Figma or even Canva. The bar is clarity, not polish.

The "what's new" field. Every update gives you a note, and almost everyone types "bug fixes and performance improvements." That's a marketing slot you're throwing away. A browsing user reads it as a signal the app is maintained. Write the benefit: "You can now set reminders that actually stick." Save the bug IDs for your own log.

A concrete example you could copy today

Say you shipped a simple water-reminder app. Here's the by-hand pass, start to finish.

Open the store search bar and type "water." Watch what autocompletes: "water reminder," "water tracker," "drink water reminder." That autocomplete is free demand data, straight from the store. It's telling you the real phrases people use.

Set your title to "Water Reminder: Drink Tracker." One keyword up front, a close variant right after. For Apple's keyword field you'd add the terms you couldn't fit: hydration,daily,intake,goal,health,drink. No spaces, no repeating "water" since it's already in your title. For Google, you write a description that says "water reminder" and "hydration tracker" naturally in the first two lines, because Google weights the top of the description most.

Then the screenshots. Screenshot one: a clean shot of the reminder firing, captioned "Never forget to drink again." Screenshot two: the progress ring, captioned "See your streak grow every day." That's the install decision, made in two frames.

Ship it. Two weeks later, open the console and look at the conversion rate, impressions to installs. If it moved, you learned something. If you'd changed title, keywords, and screenshots all at once, you'd have no idea which one did it. So change one lever per cycle.

Why one-at-a-time matters

The stores don't give you a clean lab. Impressions swing with seasonality, featured placements, and pure noise. The only way to read a change honestly is to isolate it and give it time. Edit the title, wait a month, read the conversion rate. Then move to screenshots. It's slow, and that slowness is exactly why most people skip the discipline and then wonder why their numbers are flat. The by-hand version works. It just asks for patience.

Frequently asked questions

How long does ASO take to show results?

Give it two to four weeks per change before you read anything into it. The stores re-index on their own schedule, and impressions swing day to day, so a single day tells you nothing. Change one thing at a time, wait, then compare the conversion rate in your store console. If you edit five things at once you learn nothing when the number moves.

Do I need a paid ASO tool as an indie dev?

No, not to start. The free keyword data inside App Store Connect and Google Play Console, plus the store search bar autocomplete, will get you most of the way. Paid tools like AppTweak or Sensor Tower are useful once you have traffic and want to size keyword demand precisely. Spend the money on that after you have shipped and iterated the free version, not before.

What matters more, keywords or screenshots?

They do different jobs, so it's not really a contest. Keywords get you found in search. Screenshots decide whether the person who found you taps install. If your keywords are weak nobody sees the page, and if your screenshots are weak the people who see it bounce. Fix keywords first so you have traffic to convert, then pour your effort into the first two screenshots.

Does the "what's new" field affect ASO?

Not the search ranking directly, but it affects conversion, which the algorithms watch. A benefit-led what's new tells a browsing user the app is alive and improving, and that nudges the install. Writing a dev changelog there wastes a marketing slot. Say what the user gets, not which bug ID you closed.

Where this goes next

Everything above is real and you can start it this afternoon. That's the point of writing it out. ASO isn't a secret, it's a set of fields and a habit of testing one lever at a time.

But doing it well eats time. Pulling keyword demand, writing screenshot captions that actually convert, wiring ASO into the rest of your marketing so search, social, and your update notes all pull the same direction, and knowing which numbers to trust. That's the part that takes reps to figure out. I wrote down the full sequence, the templates, and the gotchas in The Solo Founder's App-Marketing Playbook, alongside the bridge-seam content play, meta and TikTok lockstep, and how to market for free. If you'd rather not rediscover it all by hand, that's the shortcut. You can find it at wandering-castle.com/teardown.