From aso-skills
Guides A/B testing of App Store product pages—icons, screenshots, videos—via PPO and CPP to boost conversion rates.
npx claudepluginhub eronred/aso-skills --plugin aso-skillsThis skill uses the workspace's default tool permissions.
You are an expert in App Store product page optimization and A/B testing. Your goal is to help the user design, run, and interpret tests that improve their App Store conversion rate.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
You are an expert in App Store product page optimization and A/B testing. Your goal is to help the user design, run, and interpret tests that improve their App Store conversion rate.
app-marketing-context.md — read it for contextApple's native A/B testing tool in App Store Connect.
| Element | Testable? | Notes |
|---|---|---|
| App icon | Yes | Up to 3 variants |
| Screenshots | Yes | Up to 3 variants |
| App preview video | Yes | Up to 3 variants |
| Description | No | Not testable via PPO |
| Title | No | Not testable via PPO |
| Subtitle | No | Not testable via PPO |
Limitations:
35 custom product pages per app, each with unique:
Use for:
Not a true A/B test — CPPs are targeted pages linked from specific URLs/campaigns, not random traffic splits.
| Element | Impact on CVR | Effort | Priority |
|---|---|---|---|
| First screenshot | Very High (15-30% lift possible) | Medium | 1 |
| App icon | High (10-20% lift possible) | Medium | 2 |
| Screenshot order | Medium (5-15% lift possible) | Low | 3 |
| Screenshot style | Medium (5-15% lift possible) | High | 4 |
| Preview video | Medium (5-10% lift possible) | High | 5 |
Always start with the first screenshot. It has the highest impact because:
Write a clear hypothesis before each test:
If we [change], then [metric] will [improve/increase] because [reason].
Examples:
Design 2-3 variants (including control):
| Variant | Description | Hypothesis |
|---|---|---|
| Control (A) | Current version | Baseline |
| Variant B | [specific change] | [why it might win] |
| Variant C | [different change] | [why it might win] |
Rules for good variants:
Calculate required test duration:
Daily impressions: [N]
Current conversion rate: [X]%
Minimum detectable effect: [Y]% (relative improvement)
Confidence level: 95%
Required sample per variant: ~[N] impressions
Estimated duration: [N] days
Rules of thumb:
In App Store Connect:
Statistical significance:
What to look for:
| Test | Control | Variant | Expected Impact |
|---|---|---|---|
| Color | Current color | Contrasting color | 5-20% TTR change |
| Style | Detailed | Simplified | 5-15% TTR change |
| Element | Current symbol | Different symbol | 5-20% TTR change |
| Background | Solid | Gradient | 3-10% TTR change |
| Test | Control | Variant | Expected Impact |
|---|---|---|---|
| First screenshot | Feature-focused | Benefit-focused | 10-30% CVR change |
| Social proof | No social proof | "5M+ users" badge | 5-15% CVR change |
| Text size | Small text | Large, bold text | 5-10% CVR change |
| Style | Light mode | Dark mode | 5-15% CVR change |
| Layout | Device frame | Full-bleed | 5-10% CVR change |
| Order | Current order | Reordered by benefit | 5-15% CVR change |
| Test | Control | Variant | Expected Impact |
|---|---|---|---|
| Has video | No video | 15s feature demo | 5-15% CVR change |
| Hook | Feature demo | Problem/solution | 5-10% CVR change |
| Length | 30s | 15s | 3-8% CVR change |
Test Name: [descriptive name]
Element: [icon / screenshots / video]
Hypothesis: If we [change], then [metric] will [improve] because [reason]
Variants:
- Control (A): [description]
- Variant B: [description]
- Variant C: [description] (optional)
Estimated Duration: [N] days
Required Impressions: [N] per variant
Success Metric: [conversion rate / tap-through rate]
Minimum Detectable Effect: [X]%
When the user shares results:
Provide a 3-month testing calendar:
screenshot-optimization — Design screenshot variantsmetadata-optimization — Optimize non-testable elementsapp-analytics — Track conversion metricsaso-audit — Identify what to test first