Writing Your App Store Listing So People Actually Install

A practical 2026 guide to writing the App Store listing copy that drives installs — the name, subtitle, keywords, screenshots, and description that actually convert.

Your App Store listing converts visitors to installs in about 7 seconds — most users decide based on the icon, name, subtitle, and first screenshot. This is how to write each of those pieces so the conversion math works.

Background

The App Store listing is a conversion page disguised as metadata. Most indie developers under-invest here: they write the name, dump a description, and move on. But the listing is what stands between Search Console-style discovery and an actual install. In 2026, with AI Overviews and indirect referrals dominating top-of-funnel, the listing has to do more heavy lifting than ever. The good news: small, specific copy changes routinely double install conversion rates.

How to tell

  • You are submitting an app for the first time or doing a major listing refresh.
  • Your current install conversion (from product page views to installs) is below 30%.
  • You have not A/B tested any element of the listing.
  • Your screenshots are mockups or generic device frames with no captions.

Step by step

Every field below carries: char limit + writing rule + real comparison + AI drafting prompt. Open App Store Connect → My App → Distribution → fill as you go.

  1. App Name (30-char limit): clarity > category words > keywords.

    Bad:  MyHabitTrackerPro2026          (stacked + version number, fake-pro)
    Bad:  Habit Tracker - Daily Streaks  (3 category words mashed together)
    Good: Pocket Habits                  (short + memorable + implies category)
    Good: Streaks                        (a verb-concept, nothing else)

    AI Prompt (have AI generate 10 candidates):

    I'm shipping a <category> app whose core is <one sentence>.
    Give me 10 App Name candidates:
    - ≤14 characters (leave room for subtitle)
    - No generic category words ("Tracker" / "Pro" / "App" all banned)
    - No year / version number
    - Easy to read, easy to spell, easy to type in App Store search
    - For each: phonetic / association / potential ambiguity
  2. Subtitle (30-char limit): name the outcome, not the function.

    Bad:  Habit tracker app             (restates category — wasted slot)
    Bad:  Become a better you           (generic feel-good, zero info)
    Good: Build habits in 5 minutes     (time + action + outcome)
    Good: 21 days to a new routine      (specific number + visualized promise)

    AI Prompt:

    App Name is <name>. Give me 8 subtitle candidates:
    - ≤30 characters
    - Must include 1 concrete number or time
    - Must state "what the user gets", not what the feature is
    - 5 angles: time / number / counter-conventional / pain / identity

    For batch A/B variants, see AI workflow for App Store listing copy.

  3. Keywords (100-char limit, comma-separated, no spaces): only this field drives search ranking.

    Collection workflow:

    1. Open App Store search, type 1-2 seed words ("habit"), record every autocomplete
    2. Search volume: https://www.appfigures.com/asometrics/ or SensorTower (free tier is enough)
    3. ASO reports for 3 competitors via Mobile Action or AppTweak (free scans)
    4. Sort candidates by "high volume × low competition", fill until you hit 100 chars

    Rules:

    - Do NOT duplicate words already in App Name or Subtitle (Apple indexes both automatically)
    - No "the" / "and" / "in" stopwords
    - Singular only — the system auto-stems
    - No spaces — only commas: habit,streak,daily,routine,morning,...
  4. First 3 screenshots: these appear in search results. Spec: 1290x2796 (iPhone 6.7”).

    Each = 1 benefit + 1 real screen. Template:

    Screenshot 1: primary promise
      Top caption (≤8 words): Build habits in 5 minutes
      Screen: today's 3 habit cards, 2 already checked
    
    Screenshot 2: key differentiator
      Top caption: 21-day streaks, new ritual
      Screen: 21-day calendar view, streak chain highlighted
    
    Screenshot 3: social proof
      Top caption: "Sticks better than my todo list" — TechCrunch
      Screen: user achievement share card

    Tools: Screenshots.pro / AppLaunchpad / Figma templates + Fastlane snapshot for batched 6.7” / 6.5” / 5.5” sets.

  5. Description first 2 lines (~170 visible chars): must stand alone in the preview.

    Bad:  "Welcome to Pocket Habits! This is an app for building habits, created by..."
          (both visible lines are pure self-intro)
    
    Good: "No willpower needed. 5 minutes a day, 3 core habits, automatic after 21 days.
           2000+ users quit doomscrolling and started morning runs."
          (2 lines = 1 mechanism + 1 social proof)
  6. Rest of the description: pure structure, no marketing speak. Fixed 5 blocks:

    ## Who this is for
    - You want ≤3 core habits (not 10)
    - You tried Notion / Todoist but didn't stick
    - You have 5 minutes a day for a ritual
    
    ## Core features (each ≤1 sentence)
    - Morning / midday / night ritual, 5 minutes each
    - 21-day streak view, prompts you for the why on a break
    - 100% offline, no login, no cloud
    
    ## Who this is NOT for
    - Want a full GTD system: use OmniFocus
    - Want team collaboration: this is a solo tool
    - Want AI to schedule for you: this is a manual ritual
    
    ## Privacy
    - 100% offline, zero telemetry
    - No account, delete app = delete data
    
    ## Contact
    email@yourdomain.com / @your X handle
  7. Release Notes (“What’s New”): write something real on every update:

    Bad:  "Bug fixes and improvements"         (-1 trust)
    Bad:  "Performance improvements"           (-1 trust)
    
    Good:
      v1.4.2 (2026-05-21)
      New: export streak history as CSV
      Fix: 21-day calendar misaligned on iPad
      Fix: ritual reminder didn't show in landscape
      UX: a "free day" button appears after 7 consecutive days

    Rule: list exactly what changed, separate New / Fix / UX, use numbers when measurable (“Startup time: 1.2s → 0.4s”).

  8. Icon: required 4-size sanity check before submit:

    1024x1024 full size:    check detail isn't overloaded
    180x180 (@3x):          actual iPhone home screen
    120x120 (@2x):          search results list
    60x60:                  Notification Center / Spotlight

    Export the icon to 60x60, drop it into iOS Simulator or a Sketch artboard, view from 30cm — if you can identify it in 1 second, pass; if it’s mush, redo. Rule: 1 main shape + high contrast + no text.

    AI Prompt for icon brief:

    App Name is <name>, core mechanic is <one sentence>. Give me 5 icon concepts:
    - Each = 1 primary shape (object / monogram / abstract form)
    - Describe shape, colors (HEX values), background type
    - Explain why this shape stays recognizable at 60x60
    - List 2 "looks like X existing app" risks

    Once picked, build in Figma / Affinity Designer using Apple’s icon templates (start at 1024x1024).

Common pitfalls

  • Writing the listing as a feature list. Users do not buy features; they buy outcomes. Lead with the outcome.
  • Using mockup screenshots with fake data. Real screens with real-looking data convert better.
  • Putting all keywords in the description hoping for ranking boost. Description is not used for keyword ranking; the keyword field is.
  • Translating the listing with machine translation only. Native speakers can tell, and conversion suffers.
  • Ignoring the subtitle. It is the most under-used field in indie app listings.
  • Forgetting to update screenshots after major UI changes. Stale screenshots tank install rates after redesigns.

Who this is for

Solo indie developers writing or refreshing an App Store listing.

When to skip this

Apps with dedicated marketing or growth teams who already run A/B tests — your process is more sophisticated than this.

FAQ

  • Can I A/B test the listing?: Yes, via Product Page Optimization (PPO) in App Store Connect. You can run up to 3 variants against control. Use it for screenshots and icons especially.
  • How important are reviews to conversion?: Very. Below 4 stars and conversion drops sharply. Above 4.5, gains plateau. Encourage reviews from satisfied users using the in-app review prompt — but never bribe.
  • Should I translate the listing?: For your top 3-5 markets, yes — but use native speakers, not pure MT. The ROI on quality translation is high.
  • How often should I update the listing?: Subtitle and screenshots: every major version or every 2-3 months. Description: as features change. Icon: rarely, and never lightly.

Tags: #Indie dev #App Store #App launch #Content ops