ASO for Indie Developers: A 2-Hour Weekly Routine
A practical, repeatable 2-hour weekly ASO routine for indie app developers: keywords, competitors, screenshot updates, and efficient workflows that get results.
Why Block ASO Time (and How Little You Need)
If you touch your store listing for new launches or big updates and that's it, you're not running an ASO routine. Indie or not, the stores change fast—search intent, competitor moves, even basic keyword rankings can swing in a week. Two scattered hours when you feel inspired won't cut it. Schedule a two-hour recurring slot. Treat it as non-negotiable as your app's backend maintenance, because frankly: visibility is harder to fix once you lose it.
Workspace First: Save Yourself from Spreadsheet Purgatory
One of the new headaches for solo devs: too many files scattered everywhere. Keywords in a sheet, screenshots in a Figma file, notes on which competitor just updated lost in Slack or your to-do list. Centralize. I use ScreenshotWhale’s App Projects workspace because it ties my target keywords, tracked competitors, and current store assets together. Find a single source of truth—less time on logistics, more cycles for thinking.
Routine, Not Ritual: The Actual Weekly Steps
0. Prep: Block Everything Else
- Shut notifications—this is not code time. No releases. No slack. No context switches.
- Open your workspace (App Projects tab in ScreenshotWhale or whatever you use for tracking keywords, screenshots, and notes).
- Pull up last week’s ASO notes—force yourself to scan what actions you took.
1. Keyword Tracking (20-30 min)
- Fire up App Store Connect & Google Play Console. Hit your keyword ranking pages. I look at the Search tab in App Store Connect and Play Console Performance → Store Listing → Organic keywords.
- Which tracked keywords lost/gained rank vs. last week? Look for drops, new entries, and keywords that moved up but are still below the top 10.
- Add/retire keywords if needed. This is tactical: swap in one or two each week based on real search volume and relevance. Resist overhauls—those tank your ability to measure.
- If you’re early: focus on 2-3 moderately competitive keywords, not long-tail stuff nobody searches.
- Copy quick notes into your workspace. “Ranking up for ‘habit tracker’; lost ground on ‘daily planner’; test ‘goal setter’ next.” Short and to the point.
2. Competitor Review (25 min)
- Do a literal store search for each core keyword you track. Who’s crept above you? Who disappeared? Fakes, clones, new power players? (Do this in incognito—algorithms muddle results in a logged-in window.)
- Pick 2-3 direct competitors (real apps: WaterMinder if you make a utility, Yazio if you’re in health, or whatever is realistically outpacing you right now).
- Check for visible updates: new icons, headline copy, feature graphics, review surges, social proof. Will take five minutes per app if you’re organized.
- Look for patterns: is everyone leading with new features? Are they suddenly flaunting more ratings? Are screenshots now more visually dense or less cluttered than yours?
- Jot actionable specifics (not “looks better than mine”; try “Swapped to white background, 85% review quote in slot 2, third screenshot promises expert tips”).
- Drop promising new tactics into your workspace. Even if you don’t act this round, you’ll spot trends over months.
3. Quick Ratings/Review Pass (10 min)
- Open your own product page(s). How are your recent reviews trending? Anything damaging creeping up? Sort recent reviews and flag anything you can respond to or that signals a real problem (“keeps crashing on install”).
- Consider running a single push notification/alert in your app (if you dare), nudge for reviews—but only if ratings dipped or no new ratings came in last week.
- Again, log a one-sentence action or none: “Need to answer review from John re: login bug.” Store it in the workspace for next round.
4. Screenshots & Creative Quick Audit (35 min)
- Scan your store listing (iOS & Android) in situ. Are you still leading with the most compelling shot, or is it old UI? Any features still unrepresented?
- Compare slot-for-slot with a top-3 competitor. If you shipped a feature update, you need it in the very first screenshot. Old UI creeps in fast—test yourself by looking on a different device or shrink the window.
- Pencil in one creative change to test (headline, background color, swapping screenshot order).
- Create a fresh variant using templates or AI if you have time. I use ScreenshotWhale for this—under App Projects, I can fork my last screenshots, update the device or copy, and push a new variant in about 10 minutes. You could do this in Figma or Photoshop, but you’ll blow the rest of your hour. If no major assets need a refresh, just document that fact (“no update needed, parity with top 2 in first impression”).
Optional (If You Finish Fast):
- Look at store metrics for A/B tests. Is your new copy or screenshot actually converting? Play Store Experiments or App Store Product Page Optimization will tell you, if you bothered to run a variant.
- Glance at downloads, conversion rates—only take action if something’s dramatically up or down. Otherwise, more "data" is usually just a distraction for indie-scale apps.
How Not to Waste Your 2 Hours
Do not:
- Rewrite your entire keyword set every week. You’ll lose signal and direction.
- Overthink color shades or word arrangements before validating shifts with a simple swap in app store assets.
- Funnel hours into massive screenshot redesigns if A/B tests haven’t told you anything concrete. Test one thing, then move on.
Beyond the Basics: Keeping Projects Maintainable
Circle back monthly to archive abandoned keywords. If your workspace (ScreenshotWhale or your own Notion doc) is full of features from 2022, wipe them. If "competitor X" unlisted their app, remove them from your tracker. If screenshot sizes changed (it happens), run a batch update using the latest template. This quarterly housecleaning saves hours and keeps weekly ASO from spiraling into chaos.
Why This Routine Works
Manual? Yes. Boring compared to shipping new features? Definitely. But nothing else lets you spot changes before your download curve goes flat. When your ASO lives in App Projects, you move faster: you’re tracking keywords, slotting in new screenshots, watching direct competitors, and never guessing about which change triggered what result. Two focused hours, every week—no "magic" productivity ritual. Just the unglamorous grind that actually gets indie apps found.
Put this into practice on your own listing
Import your live app into an ASO workspace — metadata, keywords, competitors, and store screenshots in one place.
Import my app