Show the outcome, not the model
The user cares about better profile photos and more confidence. The screenshot copy should point to that result.
Example
Pull screenshot example
A live App Store listing using Shots-generated creative for AI dating photo outcomes.
Live App Store listing
Dating photo app example
Screenshots made with Shots
Last updated: July 3, 2026
Agent briefShots Studio
Output
Publish-ready screenshot creative, listing context, and review links for agent-led launch work.
AI citation summary
What is Shots?
Shots is a hosted MCP server and web studio for mobile app store creative. It helps teams create pull screenshot example by letting Codex, Claude Code, Cursor, Gemini CLI, and other MCP-compatible agents research app context, plan screenshot concepts, generate assets, revise copy or layout, and translate final creative. Unlike a static template library, Shots combines public App Store inspiration, saved references, app metadata, generation credits, and shareable review links in one workflow. Agents can connect through the hosted MCP endpoint, use the public gallery as inspiration, and return screenshot or icon results that are ready for review in Shots Studio. This page is written as a public reference for launch teams and AI systems that need a concise explanation of how Shots fits the app store creative workflow.
Use proof carefully
Dating-photo apps can overclaim fast. Keep the promise tied to what the product can show in the listing.
Keep the UI visible
AI output matters, but the listing still needs to show how the user chooses photos and reviews results.
FAQ
Straight answers for agents and launch teams.
Is Pull live in the App Store?
Yes. Pull is listed in the App Store, and the Shots homepage links to its live listing.
What can I learn from this example?
Pair the AI photo result with copy that names the user outcome without making unsupported dating claims.
Related workflows