android-aso▌
eronred/aso-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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).
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
- 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?
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
Use Appeeky keyword tools, then adapt for Play:
GET /v1/keywords/metrics?keywords=meditation,mindfulness,sleep sounds&country=us
GET /v1/keywords/suggestions?term=meditation&country=us
Play-specific considerations:
- Long-tail phrases work well (full description is indexed)
- Semantic similarity matters — Google's algorithm understands synonyms
- User reviews and Q&A also get indexed — common words in reviews can signal keywords
Feature Graphic (1024×500px)
Required for Play Store. Appears at the top of your listing when no video is present.
- Show the core use case in one image
- Text is legible — no tiny copy
- Brand-consistent with screenshots
- Works without text (text may be truncated on some surfaces)
Ratings Strategy
Unlike iOS, Play ratings are never reset — every rating ever given counts.
To improve your rating:
- Respond to every 1–3 star review (boosts score algorithmically)
- Reply invites re-rating — users can update their review
- Use
review-managementskill for response templates - Fix the issues mentioned in low ratings and reply: "Fixed in version X.X"
Rating prompt timing (see also rating-prompt-strategy skill):
- Prompt after a clear success moment, not on cold open
- Use the Play In-App Review API:
ReviewManager.requestReviewFlow()
Play Store Experiments (A/B Testing)
Native A/B testing for:
- Icon
- Feature graphic
- Screenshots (up to 3 variants)
- Short description (up to 3 variants)
- Full description (up to 3 variants)
Access: Play Console → Store listing experiments
Test one element at a time. Run for minimum 7 days or 1,000 impressions.
Pre-Launch (Early Access)
Use Early Access to:
- Collect reviews before public launch
- Get indexed by Google before launch
- Get editorial consideration from Google Play
Output Format
Play Store Listing Draft
Title (30): [text]
Short desc (80): [text]
Full Description:
[Hook — 2–3 sentences, primary keyword in first 167 chars]
✨ Features:
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
[Social proof paragraph]
[CTA sentence]
[Keyword-rich closing paragraph]
Keywords targeted: [list primary keywords used]
ASO Audit (Play)
Score each field 1–10:
Title: [N]/10 — [note]
Short description: [N]/10 — [note]
Full description: [N]/10 — [note]
Screenshots: [N]/10 — [note]
Feature graphic: [N]/10 — [note]
Ratings: [N]/10 — [note]
Overall: [N]/60
Top 3 improvements:
1. [specific change with expected impact]
2. [specific change with expected impact]
3. [specific change with expected impact]
Related Skills
aso-audit— iOS-focused audit (compare approaches)metadata-optimization— iOS metadata (different field rules)review-management— Respond to Play reviews to recover ratingrating-prompt-strategy— In-App Review API timing and strategyab-test-store-listing— Play Experiments methodologylocalization— Per-language listing optimization
How to use android-aso on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add android-aso
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches android-aso from GitHub repository eronred/aso-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate android-aso. Access the skill through slash commands (e.g., /android-aso) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★45 reviews- ★★★★★Pratham Ware· Dec 28, 2024
android-aso has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Michael Yang· Dec 24, 2024
android-aso fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Mei Taylor· Dec 12, 2024
We added android-aso from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Fatima Shah· Dec 4, 2024
android-aso reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sakshi Patil· Nov 19, 2024
Solid pick for teams standardizing on skills: android-aso is focused, and the summary matches what you get after install.
- ★★★★★Yusuf Wang· Nov 15, 2024
Registry listing for android-aso matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mei Farah· Nov 11, 2024
I recommend android-aso for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Anaya Sethi· Nov 3, 2024
Useful defaults in android-aso — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Mei Liu· Oct 22, 2024
android-aso has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chaitanya Patil· Oct 10, 2024
We added android-aso from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 45