The 30-Minute ASO Checklist for Indie iOS Developers

Most ASO advice is written for teams with a growth lead, a designer on call, and an agency retainer. You have a release to cut and maybe half an hour while the build uploads.

Good news: half an hour is enough. Thirty focused minutes per release beats the zero minutes most indie developers actually spend — and zero is the real competition here, not the agency playbook. You need a checklist, a timer, and the discipline to stop when it rings.

This is that checklist. Five time-boxed passes over the metadata Apple indexes and the assets that convert humans, then a lightweight monitoring loop that runs between releases. Run the full pass every time you submit a build.

[00:00–05:00] App name: brand + head keyword

You get 30 characters, and the name is widely treated as the heaviest-weighted search field on the page. Spending all 30 on your brand is a luxury reserved for apps people already search for by name. Indie reality: nobody is typing your brand yet, so the name has to earn discovery too.

The formula is boring and it works: Brand: head keyword. One brand, one head phrase, nothing else. A hypothetical habit tracker called Streakly might ship as Streakly: Habit Tracker — 23 characters, brand intact, head keyword indexed.

• One head keyword, not a list. Names stuffed with keyword salad risk rejection in review, and they look desperate in search results anyway.
• Pick the phrase people type, not the phrase you use internally. "Habit tracker" beats "behavioral consistency engine."
• Front-load what matters. Thirty is a hard limit, and names can truncate even earlier in tight layouts. Brand first only if it's short.

[05:00–10:00] Subtitle: a benefit or a search phrase, never fluff

Another 30 indexed characters, displayed directly under your name in search results. Two valid plays:

1. Conversion play: a concrete benefit. "Track habits in 10 seconds" tells a scanner exactly what they get.
2. Ranking play: your second-best search phrase, written so it still reads like something a human would say.

What never works: generic fluff. "The best productivity app" ranks for nothing and convinces no one. And don't repeat a word that already appears in your name — it's indexed once either way, so the duplicate buys you nothing but wasted characters.

[10:00–15:00] Keyword field: 100 characters, zero waste

The invisible field in App Store Connect: comma-separated terms with a 100-character budget, and it's the easiest place on the whole listing to find wasted characters. The rules:

• No spaces after commas. habit,streak,routine, not habit, streak, routine. Spaces are characters, and characters are budget.
• No words already in your name or subtitle. They're indexed from those fields; a duplicate here is pure waste.
• No plurals of words you already have in singular. Apple's own search guidance covers this — the engine handles the variants for you.
• Skip "app," your category name, and competitor brand names. The first two are dead weight; the last is a rejection risk.
• Spend the full 100. Individual terms combine with your name and subtitle words to match longer phrases, so every leftover character is a phrase you don't rank for.

Five minutes: open the field, delete the waste, refill to 100 out of 100.

[15:00–25:00] Screenshots: the first frame carries the conversion

Ten minutes here, because this is where installs are won or lost. In search results, your first screenshots render before anyone taps into your listing — and most people never tap. Frame one is doing conversion work on every impression you get, whether you designed it for that job or not.

The order that works: outcome, proof, workflow.

1. Outcome first. The result the user wants, stated plainly in the caption and visible in the frame.
2. Proof second. The actual UI doing the actual thing — no mockup theater.
3. Workflow third. How it fits into their day.

Two checks in this pass:

• The caption test. Read only your captions, top to bottom. If they don't form a coherent pitch on their own, rewrite them. Captions get read; UI details get skimmed.
• The rival test. Search your head keyword in the App Store and look at what the top five results lead with. If every first frame is the same dashboard shot, leading with something else is free differentiation. If everyone leads with social proof, ask why before you ignore it.

This pass is an audit, not a redesign. If frame one fails the test, file a ticket for the next release and move on. The timer doesn't care about your Figma ambitions. Apple's product page documentation is the reference for exact asset specs when you do the follow-up work.

[25:00–30:00] What's New: specific beats generic

"Bug fixes and performance improvements" is a wasted at-bat. What's New isn't a search play — it's read by two audiences of humans: existing users deciding whether you're still alive, and comparison shoppers checking whether you or your rival shipped more recently.

• Name the thing. "Fixed the crash when importing more than 500 entries" beats "stability improvements" every single time.
• Lead with the feature if there is one, and the biggest fix if there isn't.
• Three lines is plenty. This is a heartbeat signal, not a changelog dump.

An app whose last five What's New entries are all generic reads as abandoned, even when it isn't. Specificity is cheap and it signals maintenance.

[30:00+] The loop that runs between releases

The 30-minute pass is a snapshot. Rankings are a time series, and your listing lives next to competitors who are also iterating. Three habits cover the gap, at maybe ten minutes a week:

Track 3–5 keyword ranks — yours and a rival's

Not fifty keywords. Three to five terms that actually describe your app, checked weekly, tracked against the rival you most often lose installs to. Movement in that delta tells you when a metadata change worked — theirs or yours. We wrote up the full method in our keyword rank tracking guide.

Watch 1–3 rivals for listing changes

When a rival changes their subtitle, swaps their first screenshot, or moves their price, that's them running their own 30-minute pass — free intel about what they think isn't working. Catching it by hand means re-reading their listing on a schedule and diffing from memory, which is exactly why nobody catches it by hand. The mechanics are in how to track competitor apps on the App Store.

Mine rival reviews quarterly

One- and two-star reviews of a competing app are a sorted list of unmet demand in your exact market. Once a quarter, read a batch and tag the recurring complaints. Anything a rival is structurally unable to fix is a positioning line for your subtitle or your first screenshot. Full method in competitor review analysis.

This ongoing loop is the part Rival Radar automates. It watches rival listings and flags changes with a severity level, tracks your keyword ranks against theirs per country, and surfaces recurring complaints from their reviews — all built from public App Store data, stored locally on your phone, no account required. The free tier covers your single most important rival — enough to start the loop this checklist asks for — and Pro widens the watchlist to five.

The printable checklist

That's the whole system. No agency, no dashboard subscription you'll cancel in month two, no forty-tab spreadsheet. Thirty minutes at every release, ten a week in between. Set the timer and ship.