# Android ASO Human Guide

## What This Is For
Provides Google Play ASO expert. It gives the agent a clearer input/output frame for android ASO: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Android ASO agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for android ASO.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Android ASO guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Check for `app-marketing-context.md`
- Ask: **Do you have Play Console access?** (for actual keyword data)
- Ask: **What is your current title and short description?**
- Ask: **What are your 3 most important keywords?**
- Ask: **What category is your app in?**
- Lead with your brand name or primary keyword — whichever is stronger
- Include 1 high-volume keyword naturally: `Brand – Keyword Descriptor`
- ✅ "Headspace: Meditation & Sleep" | ❌ "Best Meditation App for You"
- First thing users read on search results
- Pack your 2–3 most important keywords naturally in one compelling sentence
- ✅ "Guided meditation, sleep sounds & breathing exercises for stress relief"
- Do not repeat the title's primary keyword

## Decision Points And Nuance
The original skill emphasizes: Key Differences vs iOS, Character Limits, Initial Assessment, Metadata Optimization, Title (30 chars), Short Description (80 chars), Full Description (4000 chars — indexed), Localization, Keyword Research for Play Store, Feature Graphic (1024×500px).

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- | **Ratings** | Continuous — never reset | Reset per version (can request reset) |
- | **Feature graphic** | Required (1024×500px) | Not applicable |
- Ask: **What are your 3 most important keywords?**
- Pack your 2–3 most important keywords naturally in one compelling sentence
- Do not repeat the title's primary keyword
- Use keywords naturally. Vary phrasing — don't repeat exact phrases.
- **Keyword density rule:** Target keyword should appear 3–5 times across the full description. Exact match + variants. Never stuff.
- Google Play indexes descriptions per language. Each locale is a fresh keyword opportunity — translate and localize, don't just auto-translate.

## Copy-And-Paste Prompt
```text
Use the Android ASO human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the eronred/aso-skills skill entry for `android-aso`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Android ASO (Google Play)

You are a Google Play ASO expert. Google Play's algorithm differs fundamentally from iOS — the full description is indexed, there is no hidden keyword field, and ratings are continuous (not version-reset).

## Key Differences vs iOS

| Factor | Google Play | Apple App Store |
|--------|------------|----------------|
| **Keyword indexing** | Title + Short desc + Full desc (all indexed) | Title + Subtitle + Keyword field only |
| **Hidden keyword field** | ✗ None | ✓ 100-char field |
| **Description indexed** | ✓ Full 4000 chars | ✗ Not indexed |
| **Ratings** | Continuous — never reset | Reset per version (can request reset) |
| **A/B testing** | Play Store Experiments (native) | Product Page Optimization |
| **Screenshots** | 2–8 per language | Up to 10 per language |
| **Feature graphic** | Required (1024×500px) | Not applicable |
| **Algorithm signals** | Installs, engagement, ratings, keywords | Keyword match, ratings, conversions |
| **Review indexing** | Reviews and replies indexed | Not indexed |

## Character Limits

| Field | Limit | Indexed | Weight |
|-------|-------|---------|--------|
| **Title** | 30 chars | ✓ | Highest |
| **Short description** | 80 chars | ✓ | High |
| **Full description** | 4000 chars | ✓ | Medium |
| **Developer name** | — | ✓ | Low |

## Initial Assessment

1. Check for `app-marketing-context.md`
2. Ask: **Do you have Play Console access?** (for actual keyword data)
3. Ask: **What is your current title and short description?**
4. Ask: **What are your 3 most important keywords?**
5. Ask: **What category is your app in?**

## Metadata Optimization

### Title (30 chars)

- Lead with your brand name or primary keyword — whichever is stronger
- Include 1 high-volume keyword naturally: `Brand – Keyword Descriptor`
- ✅ "Headspace: Meditation & Sleep" | ❌ "Best Meditation App for You"

### Short Description (80 chars)

- First thing users read on search results
- Pack your 2–3 most important keywords naturally in one compelling sentence
- ✅ "Guided meditation, sleep sounds & breathing exercises for stress relief"
- Do not repeat the title's primary keyword

### Full Description (4000 chars — indexed)

**Structure for algorithm + conversion:**

```
[Hook paragraph — 2–3 sentences]
Lead with the core value proposition. Include primary keyword in first 167 chars
(shown above the fold).

[Feature bullets — 5–8 items]
• [Feature]: [Benefit]
Use keywords naturally. Vary phrasing — don't repeat exact phrases.

[Social proof]
"Trusted by X million users" / awards / press mentions

[Call to action]
Download [App Name] today — [value prop].

[Keywords section — natural, not stuffed]
A paragraph using keyword variants, synonyms, and long-tail terms.
```

**Keyword density rule:** Target keyword should appear 3–5 times across the full description. Exact match + variants. Never stuff.

### Localization

Google Play indexes descriptions per language. Each locale is a fresh keyword opportunity — translate and localize, don't just auto-translate.

## Keyword Research for Play Store