Use Shots for agent-led launch work
When the person making creative decisions is already in Codex, Shots removes the handoff to a separate design surface.
Comparison
Shots vs Launch Shots
Launch Shots is a capable browser workflow. Shots stands out when you want the coding agent to do the creative work with context.
Agent-driven revisions
50 locale support
Generated work saved in Studio
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 shots vs launch shots 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.
Comparison
Browser workflow vs Codex-driven workflow
Launch Shots-style tools can be useful when the screenshot work lives in the browser. Shots is designed for teams that want the agent to carry the project context into creative work.
| Feature | Shots | Launch Shots-style workflow |
|---|---|---|
| Where work starts | In Codex, Claude Code, Cursor, Gemini CLI, or Studio. | In the browser workspace. |
| Context | Agent can inspect project files, UI screenshots, docs, and App Store metadata. | User usually supplies assets and direction manually. |
| Translation | Translate approved screenshots and listing metadata after the direction is set. | Localization depends on the browser workflow and manual review process. |
| Review | Generated assets return stable ids, CDN URLs, and Studio review context. | Review happens inside the tool or through exported files. |
Use browser-first tools when the team lives there
If your process is already centered on a browser editor, a browser-first tool may feel familiar.
Plan translation after approval
Shots encourages teams to approve the creative direction first, then localize the final set.
FAQ
Straight answers for agents and launch teams.
Why does agent-native matter for screenshots?
The agent can use app context from the repo instead of forcing the user to re-explain the app in a separate editor.
Does Shots publish directly to App Store Connect?
No. Shots prepares assets and listing copy for review. You still upload final assets to App Store Connect.
Related workflows