Start with the decision your screenshot must support
A screenshot set is not a gallery of every feature. It is a short sales sequence. Decide which user problem the app solves, which outcome matters most, and what proof the interface can show. That decision gives the first screenshot a clear job and prevents later screens from repeating the same message.
Capture the real product first
Prepare clean product states before adding frames or marketing copy. Use realistic data, remove test labels, close keyboard overlays, and keep status bars consistent. Each capture should prove the claim that will sit beside it. If the headline promises faster planning, show the planning interaction or its useful result.
- Use the current production interface
- Remove personal and test data
- Keep time, battery, and status bars consistent
- Capture the state that proves the benefit
- Use a repeatable device and viewport setup
- Save source captures before adding decoration
Plan the sequence before designing
Give every screen a distinct role. A practical sequence starts with the main promise, follows with proof, shows the most important workflow, answers a likely objection, and ends with a supporting capability. You do not need to fill all ten App Store slots. Use only the number needed to tell a complete story.
Write one message per screen
Keep the headline short enough to understand at thumbnail size. Lead with the user outcome instead of the internal feature name. Supporting copy should clarify the claim, not repeat it. Read the set in order with the app UI hidden. If the story still makes sense, the message hierarchy is working.
Build a flexible visual system
Choose one type scale, one spacing rhythm, one background family, and one device treatment. Keep important copy inside a generous safe area so the design can adapt to other device ratios and languages. Consistency should come from the system, while each screen keeps a distinct message and composition.
Export for the exact App Store slot
App Store Connect accepts specific pixel dimensions for each display slot. Export from a master layout into the accepted iPhone, iPad, and Apple Watch dimensions you support. Do not stretch one finished JPEG into a different ratio. Reflow the layout and check the result at its final pixel size.
Run a final store-ready review
Review the full sequence on a phone-sized display, not only on a large design canvas. Check spelling, product accuracy, text contrast, localization, file format, dimensions, and order. Then compare the uploaded preview in App Store Connect with the exported source files before submitting the app version.
- One clear promise in the opening screen
- A different role for every later screen
- Readable text at thumbnail size
- Real product UI that supports each claim
- Accepted dimensions for every target slot
- Final review in every published locale