AppScreenshots DocsPlan a complete screenshot set
Turn a launch, feature update, or campaign requirement into a frame-by-frame screenshot plan.
Plan a complete screenshot set
Do the planning before placing pixels. A screenshot set works as a short product story: each frame earns attention for the next one, while the whole set supports one release or marketing goal.
1. Write the requirement in one sentence
Use this format:
For [audience], show why [product or release] helps them achieve [outcome] on [store/platform].
Example: “For busy runners, show that the new training planner turns a weekly goal into a simple daily plan on the iPhone listing.”
This statement keeps the screenshot set from becoming a gallery of unrelated screens.
2. Make a frame-by-frame brief
Start with three to six frames, then adjust the count to the destination store’s current rules. Use a different job for every frame.
| Frame | Job | What to show | Copy direction |
|---|---|---|---|
| 1. Hero | Explain the main promise | The clearest, most desirable product state | Outcome first |
| 2. Key action | Show how the promise happens | The primary workflow | Action + payoff |
| 3. Proof | Build confidence | Results, personalization, data, or a recognizable feature | Specific evidence |
| 4. Differentiator | Explain why this product | A unique capability or integration | Contrast or advantage |
| 5. Depth | Reassure a serious evaluator | Supporting workflow, settings, or ecosystem | Control, breadth, or trust |
Tip: A sequence can be shorter. A focused three-frame story is usually stronger than six frames that repeat the same message.
3. Assemble the production inputs
| Input | Owner | Check before production |
|---|---|---|
| Raw app captures | Product or engineering | Current build, clean data, no debug UI or personal information |
| Copy | Product marketing | One benefit per frame, approved terminology, clear character limits for translation |
| Brand assets | Brand or design | Approved logo, colors, font, illustrations, badges |
| Store requirements | Release owner | Exact device classes, orientations, count, and language markets |
| Language mapping | Release owner and localization reviewer | Website interface locale, screenshot-project locale, target market, and native reviewer for each delivery |
| Review owners | Product, design, legal if needed | Who approves message, visual, and compliance |
4. Select the right creation route
| Situation | Recommended route |
|---|---|
| You already have a clear visual direction and source captures | Start in the Screenshot Editor. |
| You need a first draft of product positioning and a recommended template | Use AI Screenshot Generator, then refine the resulting project. |
| You want a proven layout to customize | Begin with Templates. |
| You only need a single device mockup for a presentation or campaign | Use Mockup Creator. |
5. Produce a master set before localized variants
Build and approve one master language first. In the editor, each canvas is a frame, so the frame order is the storefront reading order. Add, duplicate, delete, and move frames from the controls above each canvas.
Before enabling a localized variant, confirm the website-to-project locale mapping—especially zh/zh-CN, zh-hk/zh-TW, and pt-br/pt. See Language support and locale mapping.
When a visual must continue across adjacent frames, switch the canvas to horizontal orientation and enable continuous mode. Then use Frame Spanning in the selected device’s properties. Use this treatment sparingly: the message must still work if the store shows only one frame at a time.
6. Gate the set before export
Review the set in this order:
- Story: Does the frame order make sense without a spoken explanation?
- Product truth: Does each screen match the release users will receive?
- Readability: Is the main line legible at a small preview size?
- Consistency: Are the device, spacing, color system, and type hierarchy intentional across frames?
- Delivery: Are platform, locale, and reviewer requirements documented?
Next, learn how to work in the Screenshot Editor, or skip to Localization if your master set is already approved.