When to use this playbook
| Use it when | Skip it when |
|---|---|
| You’re preparing a mobile game / app store listing | You haven’t validated the concept yet — use game concept validation first |
| You have multiple icon, screenshot, or description options to test | You have nothing to compare (generate options first) |
| You want player-representative feedback before launch | You need post-launch retention data (that’s analytics, not pre-test) |
Audience targeting. Because this tests a mobile game, the polls target mobile gamers
(
mobileyes) in the core 25–44 age range and report results by age and gender. Adjust the
targeting to your game’s actual demographic — a kids’ puzzle game and a hardcore strategy game
have very different players. Use list_available_targeting to see options.The sequence
Test your gameplay trailer
Open-ended feedback on whether the trailer makes players want to download.
Sample size and cost. Defaults to 50–100 respondents per element test (ranked tests use
100 for a clearer winner; open-ended uses 50). For a tighter budget, 50 across the board is fine
for directional results. The final validation uses 100. See
sample size guidance.
Run this playbook with an AI agent
Copy prompt for AI
Paste this prompt into Claude, ChatGPT, Cursor, or any AI agent connected to the
PickFu MCP server, CLI,
or REST API. The agent will run the entire loop on your behalf —
creating polls, reading responses, and iterating until a winning variation emerges.
Step-by-step (human operator view)
1. Compare icon designs
| Setting | Value |
|---|---|
| Poll type | Ranked choice |
| Question | ”Which game icon makes you MOST want to download and play a mobile [GENRE] game? Explain what catches your eye.” |
| Options | 3–4 icon variations |
| Audience | Mobile gamers, 25–44 (report by age + gender) |
| Sample size | 100 |

2. Test your gameplay trailer
| Setting | Value |
|---|---|
| Poll type | Open-ended |
| Question | ”Watch this gameplay trailer for a mobile [GENRE] game. Would you download it? What excites you or puts you off?” |
| Options | Your gameplay trailer / video preview |
| Audience | Mobile gamers, 25–44 |
| Sample size | 50 |
3. Rank your screenshots
| Setting | Value |
|---|---|
| Poll type | Ranked choice |
| Question | ”Which image would make you MOST likely to download and play a mobile [GENRE] game? Tell us what about the image makes you want to play.” |
| Options | 4–8 screenshot options |
| Audience | Mobile gamers, 25–44 |
| Sample size | 100 |
4. Test your app description
| Setting | Value |
|---|---|
| Poll type | Ranked (3+ versions) or Head-to-head (exactly 2 versions) |
| Question | ”Which app description would make you MOST likely to download this mobile [GENRE] game? What about the description appeals to you?” |
| Options | Your description versions, as text options |
| Audience | Mobile gamers, 25–44 |
| Sample size | 50–100 |
5. Validate the full listing
| Setting | Value |
|---|---|
| Poll type | Multi-question survey |
| Q1 | Star rating: “Based on this app store listing, how likely are you (1–5) to download this game?” |
| Q2 | Open-ended: “What’s the most appealing thing about this game based on the listing?” |
| Q3 | Open-ended: “Is there anything confusing or that would stop you from downloading?” |
| Q4 | Multi-select: “What type of game does this look like?” (Strategy, Action, Puzzle, Casino, Sports, RPG, Simulation, Other) |
| Context | Upload a screenshot of the full app store listing as the Q1 context image |
| Audience | Mobile gamers, 25–44 |
| Sample size | 100 |
Recommended targeting by genre
These are the demographics most likely to play each genre. You know your audience best — adjust as needed, and use list_available_targeting for the exact trait codes.| Genre | Targeting | Why |
|---|---|---|
| Strategy | mobile gamers, 25–34, 35–44, male | Strategy core demo |
| Casino / Slots | mobile gamers, 35–44, 45–54, 55–64 | Casino skews older |
| Sports | mobile gamers, 18–24, 25–34, male | Sports skews young male |
| Casual / Puzzle | mobile gamers, 25–34, 35–44, female | Casual skews female |
| RPG / Fantasy | mobile gamers, 18–24, 25–34 | RPG skews younger |
Pro tips
- Character-focused icons beat logos. Across hundreds of gaming icon tests, icons with a character face or figure out-perform abstract logos and text-only icons. Always include a character concept.
- Test icons at display size. Upload icons at roughly 60×60px — the size they appear on the store shelf. Performance at small size is what matters, not full-resolution polish.
- Lead with your strongest screenshot. Position 1 gets 3–5× more views than position 4+, so your #1-ranked screenshot should occupy the first slot.
- Vibrant colors win on the shelf. Saturated treatments consistently out-perform muted or dark ones in icon testing.
- Re-test after major updates. Re-run the screenshot and full-listing steps after any major update or seasonal re-skin so the listing reflects the current game.
Troubleshooting
My ranked description poll won't launch.
My ranked description poll won't launch.
Ranked polls need 3–8 options. If you only have two description versions, switch the poll type
to head-to-head (exactly 2 options). Add a third version to keep it ranked.
Players misidentify the genre in Q4 of the full-listing validation.
Players misidentify the genre in Q4 of the full-listing validation.
If the multi-select genre answers scatter or point to the wrong category, your icon + screenshots
are sending mixed signals. Revisit steps 1 and 3 — the winning assets should make the genre
unmistakable at a glance.
Should I target broadly or narrowly?
Should I target broadly or narrowly?
Target the demographic that matches your game. A hardcore strategy game tested on casual players
gives misleading results. Use list_available_targeting to find the
right mobile-gamer and age filters, and report by age + gender to spot segment differences.
Related
- ASO advanced tests & FAQs (help center) — video preview, Custom Product Page, featured-graphic tests, and common questions
- Game concept validation — validate the concept before building the listing
- Best practices for survey design
- MCP server reference
- PickFu CLI
