---
name: app-store-description
description: "Use this skill to create or optimize app store descriptions (Apple App Store, Google Play Store) using real audience insight. Triggers include: requests to write app store listings, optimize app descriptions, improve app store conversion rates, increase app downloads, refine app store pages, write app subtitles or short descriptions, or test app store messaging with target users. Works for both new apps that need a description from scratch and existing apps that need optimization. Uses OriginalVoices Digital Twins (ask_twins) to understand what makes target users download an app, what information they need, what language resonates, and what builds trust — then creates or optimizes app store descriptions grounded in real user perspectives."
---

# App Store Description Agent

## Overview

Create or optimize app store descriptions (Apple App Store and Google Play Store) using real audience insight. This workflow researches your target users to understand what drives them to download apps, what information they scan for, what language resonates, and what triggers hesitation — then uses those insights to write new descriptions or optimize existing ones for better conversion.

## Workflow Steps

### Step 1: Gather App & Listing Details

Collect from the user:
- **App name**: The app's name
- **App category**: Category on the store (e.g. "Productivity", "Health & Fitness", "Finance", "Education")
- **Target audience**: Who is this app for? (e.g. "Freelancers aged 25-40 who struggle with invoicing", "Parents of toddlers looking for educational screen time")
- **App store platform**: Apple App Store, Google Play, or both
- **Current description** (if optimizing): The existing app store description to improve
- **Key features**: Core features or capabilities (if not clear from description)
- **Key differentiator**: What makes this app different from competitors
- **Pricing model**: Free, freemium, paid, subscription
- **Goal**: New description from scratch, or optimize an existing one

**If creating from scratch, also gather:**
- **Problem it solves**: What user problem does this app address?
- **Core value proposition**: The main reason someone should download it

### Step 2: Research App Download Behaviour & Preferences

One comprehensive research call to understand what drives app download decisions and how the target audience evaluates app store listings.

**If optimizing an existing description:**
```
ask_twins(
  audience: "[detailed target audience]",
  questions: [
    "When you're browsing the app store for a [app category] app, what do you look at first? What makes you tap on an app to learn more?",
    "Here's the current description for an app called [app name]: '[paste current description]'. What's your initial reaction? Would this make you want to download it?",
    "Based on that description, is it clear what this app does and why you'd use it? What's confusing or unclear?",
    "What do you like about this description? What stands out as good or compelling?",
    "What's missing from this description? What would you need to know before downloading a [app category] app?",
    "What concerns or hesitations would you have about downloading this app based on this description?",
    "Does the tone of this description feel right for a [app category] app? Does it feel trustworthy?",
    "What would make this description more convincing? What would push you to hit the download button?",
    "When comparing [app category] apps, what do you look for in the description to decide between options? What makes one stand out over another?",
    "What are the biggest frustrations you have with [problem the app solves]? What words would you use to describe that frustration?",
    "If you saw this app was [pricing model], would the description justify that? What would need to be different?",
    "Is there anything in this description that turns you off or makes you less likely to download?"
  ]
)
```

**If creating a new description from scratch:**
```
ask_twins(
  audience: "[detailed target audience]",
  questions: [
    "When you're browsing the app store for a [app category] app, what do you look at first? What makes you tap on an app to learn more?",
    "What are the biggest frustrations you have with [problem the app solves]? What words would you use to describe that frustration?",
    "What would an ideal [app category] app do for you? What would make you think 'I need this'?",
    "When reading an app description, what information do you need to see before you'll download? What's essential vs. nice-to-have?",
    "What makes you trust an app enough to download it? What signals credibility in the app store?",
    "What would make you choose one [app category] app over another? What's the deciding factor?",
    "How do you feel about [app category] apps that are [pricing model]? What would the description need to say to justify that?",
    "What turns you off when reading app descriptions? What makes you skip an app and keep scrolling?",
    "When it comes to [problem the app solves], what matters most to you? Speed, simplicity, features, design, price?",
    "What [app category] apps do you currently use? What do you like and dislike about how they describe themselves?",
    "If an app said it could [core value proposition], what would your reaction be? Would you believe it? What would make it credible?",
    "What words or phrases would grab your attention in an app description for something that helps with [problem]?"
  ]
)
```

### Step 3: Analyse Audience Insights

Review responses and extract insights specific to app store description optimization:

**Download Drivers:**
- What makes them tap "Get" or "Install"
- What information is essential before downloading
- What language grabs their attention

**Current Description Feedback (if optimizing):**
- What's working and should be kept
- What's missing or unclear
- What turns them off or creates doubt

**App Store Browsing Behaviour:**
- What they scan first in a listing
- How much of the description they actually read
- What makes them compare further vs. move on

**Language & Tone:**
- Words and phrases that resonate
- Tone preferences (professional, casual, energetic, minimal)
- Language that feels trustworthy vs. overhyped

**Concerns & Objections:**
- Hesitations about downloading
- Pricing sensitivity and value perception
- Trust signals they need to see

**Competitive Differentiation:**
- What they look for when comparing apps
- What would make this app stand out
- What competitors do well or poorly in their descriptions

### Step 4: Write or Optimize the App Store Description

Using the insights from Step 3, create the app store listing elements.

**App Store Listing Elements to Deliver:**

**1. Subtitle / Short Description (required)**
- Apple App Store subtitle: up to 30 characters
- Google Play short description: up to 80 characters
- Lead with the strongest hook from research

**2. Full Description**

Structure the description using what the audience said matters most:

**First paragraph (above the fold — this is critical):**
- Open with the problem or outcome that resonated most
- Make it immediately clear what the app does and who it's for
- Use the audience's own language where possible

**Feature/benefit section:**
- Lead with benefits, supported by features
- Prioritize based on what the audience said matters most
- Use short, scannable lines or bullet points

**Social proof / trust section (if applicable):**
- Include trust signals the audience said they need
- Reference credibility markers (awards, press, user count, ratings)

**Closing / CTA:**
- Address the top objection or hesitation
- End with a clear reason to download now

**Platform-specific guidelines:**

| Element | Apple App Store | Google Play |
|---------|----------------|-------------|
| **Subtitle** | 30 characters max | N/A |
| **Short description** | N/A | 80 characters max |
| **Full description** | 4,000 characters max | 4,000 characters max |
| **Formatting** | Plain text only (no markdown, no HTML) | Supports limited HTML and emoji |
| **Keyword strategy** | Keywords field separate — don't stuff description | Keywords in description help ranking |

**If optimizing — apply a LIGHT TOUCH:**
- Keep elements the audience liked
- Add missing information they said they need
- Adjust tone or language based on feedback
- Address concerns they raised
- Reorder sections based on what they scan first

**If creating from scratch:**
- Build entirely around what the audience said drives downloads
- Use their language and frame the problem the way they describe it
- Front-load the most compelling hook
- Include every piece of information they said is essential

### Step 5: Deliver the App Store Description Package

**PRIMARY DELIVERABLE — App Store Description:**

Output the complete, ready-to-publish listing for each platform requested:
- Subtitle or short description
- Full description (within character limits)
- Formatted for the specific platform

**THEN provide supporting materials:**

**1. Optimization Summary:**
- **Key insights applied**: Top 3-5 audience insights that shaped the description
- **What changed** (if optimizing): Key changes made and why
- **Expected impact**: What should improve (clarity, conversion, differentiation)

**2. Before vs. After (if optimizing):**
- **Original**: Key sections from the original
- **Optimized**: How they were improved
- **Why it's better**: Grounded in audience insight

**3. Audience Insight Summary:**
- **Download drivers**: What makes them install
- **Information needs**: What they must see before downloading
- **Language that resonates**: Words and phrases that grabbed attention
- **Turn-offs**: What made them skip or hesitate
- **Trust signals**: What builds credibility
- **Competitive factors**: What makes an app stand out

**4. Keyword Suggestions:**
- Terms and phrases the audience naturally used when describing the problem and solution
- Language patterns to incorporate into metadata and keywords fields

**5. Additional Recommendations:**
- Screenshot and preview suggestions based on what the audience said they look for
- Rating/review strategy aligned with audience trust signals
- A/B test suggestions for description variants
- Localization considerations if audience feedback suggests it

## App Store Description Framework

| Element | Audience Insight Source | Approach |
|---------|------------------------|----------|
| **Subtitle / short description** | What grabs attention first | Lead with strongest hook in their language |
| **Opening line** | Top problem or desired outcome | Start with what resonated most |
| **Feature order** | What they said matters most | Prioritize by audience preference |
| **Benefit framing** | How they describe success | Use outcome language, not feature language |
| **Trust signals** | What builds download confidence | Include what they said they need to see |
| **Tone** | Professional vs. casual preference | Match their expectation for the category |
| **Length** | How much they actually read | Front-load value, keep scannable |
| **CTA / closing** | What hesitations they have | Address top objection, give reason to act |

## Tips for Best Results

- **First three lines are everything**: Most users see only the first 1-3 lines before "Read More" — make them count
- **Use their language**: Mirror the exact words your audience uses to describe the problem and desired outcome
- **Benefits over features**: "Track expenses in 10 seconds" beats "Built-in expense tracker"
- **Be specific**: "Used by 50,000 freelancers" beats "Trusted by thousands"
- **Address the pricing objection**: If it's paid or subscription, justify value in the description
- **Platform matters**: Google Play rewards keyword-rich descriptions for ASO; Apple does not
- **Scannable format**: Short paragraphs, line breaks, and bullet points (where supported)
- **Light touch when optimizing**: Keep what's working, fix what's not — don't rewrite for the sake of it

## Common App Store Description Pitfalls

- **Burying the value**: Most compelling benefit hidden in paragraph three instead of line one
- **Feature dumping**: Lists of features with no explanation of why they matter to the user
- **Generic opening**: "Welcome to [App Name]!" wastes the most valuable real estate
- **Overpromising**: Claims that feel too good to be true reduce trust
- **Ignoring the fold**: Assuming users will tap "Read More" — most won't
- **Wrong tone for category**: A finance app that sounds like a game, or a fitness app that reads like a textbook
- **No differentiation**: Description could apply to any competitor in the category
- **Keyword stuffing**: Cramming keywords at the expense of readability (especially on Google Play)
- **Ignoring pricing context**: Not addressing value for money when charging a subscription

## Red Flags (Description Issues)

- First three lines don't clearly explain what the app does
- No mention of the core problem or user need
- Features listed without benefits
- Tone doesn't match what the audience expects for the category
- Missing trust signals the audience said they need
- Doesn't address top concerns or objections
- Reads like marketing copy rather than a genuine description
- No differentiation from competing apps

## Green Lights (Strong Description)

- Opens with the problem or outcome the audience cares about most
- Clear what the app does within the first three lines
- Uses language the audience naturally uses
- Features framed as benefits with outcomes
- Includes trust signals the audience values
- Addresses pricing and value perception
- Tone matches audience expectations
- Stands out from competitors based on what users said matters
- Scannable and front-loaded for the "above the fold" reality