📦 Install
clawhub install aso-playbook
What you get after installing:
- Keyword research methodology for finding low-competition, high-intent terms
- Screenshot hypothesis and message-hierarchy framework
- A/B testing and evidence-capture framework for iOS and Android
App Store Optimization Basics — Keywords, Screenshots & Ratings
🌍 Language / 语言: 中文 | English | 日本語 | 한국어
The fundamentals of ASO for developers who'd rather build than market — but need downloads.
- Keyword research: Finding low-competition, high-intent keywords for your category
- Screenshot optimization: Turn user intent into testable screenshot hypotheses
- Rating strategy: How to ask for reviews without annoying users
- Localization basics: Which markets to target first and how to test
- A/B testing: What to test, how long to run, and interpreting results
Minimum viable ASO workflow
- Export the last 28 days by country and traffic source: impressions, product-page views, first-time downloads, conversion rate, proceeds, D1/D7/D30 retention.
- Build a keyword sheet with relevance, current rank, search popularity, competition, destination locale and target page.
- Change one variable family at a time: metadata, icon, first three screenshots, preview video, rating prompt or localization.
- Record the exact before/after version, release date, storefront and external UA activity.
- Keep a test only when conversion improves without a material decline in retained users, rating quality or revenue.
Evidence gate
Do not claim an ASO win from downloads alone. A valid case needs, at minimum:
- keyword rank or search-impression change;
- impression → product-page-view rate;
- product-page-view → first-time-download rate;
- D7 or D30 retained-user outcome;
- dates, storefronts, app version and paid-campaign overlap.
No controlled Gingiris App Store before/after dataset is bundled with this skill yet. The workflow is executable; any uplift claim must come from the user's own App Store Connect or Play Console export.
Compliance gate
Never recommend bought ratings/reviews, artificial searches or installs, device/account farms, chart manipulation, or packages intended to evade enforcement. Use official storefront experiments, authentic-user review prompts and transparent paid acquisition. Historical notes that mention black-hat tactics are research records, not execution guidance.
Related Gingiris Skills
1---2name: aso-playbook3description: Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.4---56## 📦 Install78```bash9clawhub install aso-playbook10```1112**What you get after installing:**13- Keyword research methodology for finding low-competition, high-intent terms14- Screenshot hypothesis and message-hierarchy framework15- A/B testing and evidence-capture framework for iOS and Android1617---1819# App Store Optimization Basics — Keywords, Screenshots & Ratings2021> 🌍 **Language / 语言**: [中文](#中文版) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md)2223The fundamentals of ASO for developers who'd rather build than market — but need downloads.2425- **Keyword research**: Finding low-competition, high-intent keywords for your category26- **Screenshot optimization**: Turn user intent into testable screenshot hypotheses27- **Rating strategy**: How to ask for reviews without annoying users28- **Localization basics**: Which markets to target first and how to test29- **A/B testing**: What to test, how long to run, and interpreting results3031## Minimum viable ASO workflow32331. Export the last 28 days by country and traffic source: impressions, product-page views, first-time downloads, conversion rate, proceeds, D1/D7/D30 retention.342. Build a keyword sheet with relevance, current rank, search popularity, competition, destination locale and target page.353. Change one variable family at a time: metadata, icon, first three screenshots, preview video, rating prompt or localization.364. Record the exact before/after version, release date, storefront and external UA activity.375. Keep a test only when conversion improves without a material decline in retained users, rating quality or revenue.3839### Evidence gate4041Do not claim an ASO win from downloads alone. A valid case needs, at minimum:4243- keyword rank or search-impression change;44- impression → product-page-view rate;45- product-page-view → first-time-download rate;46- D7 or D30 retained-user outcome;47- dates, storefronts, app version and paid-campaign overlap.4849No controlled Gingiris App Store before/after dataset is bundled with this skill yet. The workflow is executable; any uplift claim must come from the user's own App Store Connect or Play Console export.5051### Compliance gate5253Never recommend bought ratings/reviews, artificial searches or installs, device/account farms, chart manipulation, or packages intended to evade enforcement. Use official storefront experiments, authentic-user review prompts and transparent paid acquisition. Historical notes that mention black-hat tactics are research records, not execution guidance.5455## Related Gingiris Skills56- Full version: https://clawhub.ai/gingiris-1031/skills/gingiris-aso-growth57- All skills: https://clawhub.ai/gingiris-103158- Follow: [@WeiYipei on X](https://x.com/WeiYipei)