Most App Store listings die at the subtitle — the second highest-CTR field on the page gets a generic tagline that wastes every character. These prompts squeeze the title, subtitle, promo text, and screenshot captions into compounding ranking + conversion work. When a version ships, take the same audience picture into drafting release notes with AI so the listing copy and the “What’s New” panel reinforce each other.
Best for
- First App Store launch
- ASO refresh between feature drops
- New version drop with promo-text reset
- International / locale expansion
- Indie devs without a dedicated ASO budget
1. App title + subtitle (App Store)
App: {one-line, target keyword}. Generate 8 title + subtitle pairs.
Constraints:
- Title ≤30 chars, subtitle ≤30 chars
- Combined must signal niche + outcome
- No "AI-powered" filler unless the keyword itself is "AI"
- Each pair targets a different searcher intent (problem-aware, solution-aware, branded)
Output: table with columns Title | Subtitle | Intent | Char count.2. Promotional text (App Store)
For App Store promo text (170 chars max), write 5 variants for {app}. This field appears above description, is indexable, and updatable without review. Use it for time-sensitive copy: new feature, seasonal angle, or proof point.
Each variant must:
- Lead with the news, not "We're excited to announce"
- Include 1 concrete benefit
- Stay under 170 chars including punctuation3. Description first 3 lines (above the fold)
For App Store description, write 5 variants for the first 3 lines that show before "more". Each variant:
Line 1: hook in <80 chars, no question marks
Line 2: what the app actually does (concrete verb + object)
Line 3: who it's for, by role or job-to-be-done
Avoid: "Welcome to {app}", "Are you tired of", emoji bullet lists.4. Description full draft
Draft a full App Store description for {app} in ≤4000 chars:
1. Hook paragraph (the first 3 lines from above)
2. Key features section: 4-6 bullets, each starts with a user verb
3. Social proof: 2-3 short quotes or numeric proof points
4. Pointer to "What's New" + "Privacy"
5. Closing CTA
Voice: confident, specific. No marketing fluff.5. Screenshot caption copy
I have 5 App Store screenshots covering {features}. Write a caption per screenshot:
- Top line ≤25 chars (the headline)
- Bottom line ≤35 chars (the supporting beat)
- Each caption tells one story; don't repeat the feature name verbatim
- Caption 1 = strongest user outcome, not the cleverest line
Output: numbered list with both lines per screenshot.6. Google Play short description
For Google Play (80-char short description), write 6 variants for {app}.
- Lead with the user outcome, not the category name
- Include the primary keyword once, naturally
- 3 variants benefit-led, 3 variants problem-led
- Count chars including spaces and confirm ≤807. Keyword research for ASO
My app does {functions}. Suggest 30 candidate keywords, ranked by likely intent match × competition (low/med/high). For each: 1 line of why it fits.
Then pick the 10 to target across the title + keywords field, and explain the rationale (head term, mid-tail, branded, defensive).8. Localization brief
I'm localizing my US listing to {locale}. Identify:
1. Terms that won't translate (cultural, idiomatic, brand-language)
2. Cultural adjustments needed in the screenshots
3. Screenshot text translation length budget vs source
4. Store-specific conventions for that locale (rating prompts, payment terms)
5. Top 5 native-language keywords to swap into the keywords field9. Title A/B test plan
For {app}, design a 4-week App Store title + subtitle A/B test plan:
Week 1: baseline measurement (CVR, impressions, keyword rank for top 5 terms)
Week 2: variant A — keyword-led title
Week 3: variant B — outcome-led subtitle
Week 4: pick winner, document rationale
Output: test matrix + the exact metric thresholds that decide the winner.10. What’s New copy
Write 4 variants of "What's New" copy for {app} v{version}. The release shipped: {features + fixes}.
Each variant ≤500 chars:
- Lead with the most-asked-for change
- Group: New / Improved / Fixed
- 1 specific number per release if available (faster by X%, supports Y new languages)
- No "various bug fixes and improvements" filler11. Review-response templates
Write 6 App Store review-response templates for {app}:
1. 5-star with a feature request → thank + commit to consider
2. 4-star with a small bug → acknowledge + ETA
3. 3-star confused user → onboarding pointer
4. 2-star angry → ownership + support email
5. 1-star wrongly-attributed problem → polite correction
6. 1-star pricing complaint → value reframe
Voice: human, not corporate. ≤300 chars each.12. Search Ads keyword bid sheet
For {app}, draft an Apple Search Ads bid sheet covering my top 10 ASO keywords:
Columns: Keyword | Match type (exact / broad / search match) | Suggested bid range | Negative keywords to add | Daily cap rationale
Notes on which keywords to defend (branded), which to expand on (mid-tail), and which to drop after 2 weeks if CPI is too high.Common mistakes
- Wasting the subtitle on a tagline that repeats the title
- Using one description for every locale and store
- Screenshot captions that exceed the safe char budget and get cropped on small devices
- Ignoring the promo-text field because “we don’t have news” — it’s also indexable
- Treating Google Play short description as a mini App Store subtitle — different conventions