How to create App Store screenshots with Codex and Shipper

With Shipper Plugin, Codex can create and refine screenshot sets inside Shipper. Headlines, mockups, colors, and supported layout elements remain editable, so you can make the next change yourself or ask Codex to continue.

You need Shipper on your Mac, Codex, and the Shipper connection enabled. Design, adaptation, and PNG export are free in Shipper. Localization, App Store Metadata, and App Store Connect Publishing require Shipper PRO. Access to Codex and external AI services is separate.

Start with one language and one supported screenshot specification. A source set you can review gives later adaptations a clear foundation.

Gather the app screens that explain your main use cases. You can import existing captures or bring in screens through Device Hub. Use demo data you are comfortable sharing, and make sure Codex can access the files you reference.

Your brief needs four things:

• The intended audience and the problem your app helps them solve.
• The real features and screens you want to highlight.
• Your app name, brand colors, and terms to preserve.
• The starting language and screenshot specs, or a request to check the available choices.

A useful starting point is: “This app helps independent tutors plan lessons. Use the supplied schedule, lesson notes, and progress screens. Focus on keeping lesson preparation organized.” That gives the design a purpose without inventing claims.

Ask Codex to propose the sequence before creating the full set. Each screenshot should explain something distinct. Three useful messages are better than six versions of the same promise.

Propose a screenshot sequence using the supplied app screens. For each frame, suggest a short headline, the supporting screen, and the benefit it explains. Flag any message that the available screens do not support.

Check whether the first frame makes the app’s purpose clear and the following frames add useful detail. Apple’s product page guidance recommends using captured app UI and focusing each subsequent screenshot on a main benefit or feature.

Use Shipper Creative Lab to explore the visual direction, then agree on a Shipper Creative Target: the story, tone, and composition that will guide the set. Be specific about what matters to your app.

Explore a light, minimal direction using our supplied colors. Keep the app screen large enough to read, use short headlines, and avoid decorative elements that compete with the interface.

A reference can help explain spacing or hierarchy. Say which aspect you like rather than asking for another app’s identity. Review the first composition before applying the direction across the set.

Once you have agreed on the sequence and direction, ask Codex to create it in Shipper. You can start with a template or a blank canvas; both can be refined in the design workspace.

Create the agreed screenshot set in Shipper for [app name], using [source language] and [supported specs]. Use the supplied captures and our agreed Shipper Creative Target. Keep the project editable. Save it for review without sending anything to App Store Connect.

Replace the bracketed details with your choices. If you already have a project, name it and explain whether to add a set or update existing work.

Open the result in Shipper and try changing a headline or mockup position. The composition remains editable; text already embedded inside an imported app capture is still part of that image.

Give feedback by frame and by element. Explain what should change and which parts already work.

In frame 3, shorten the headline to “Keep lesson notes together” and enlarge the app screen. Preserve the background, typography, and other frames.

You can also adjust the project directly in Shipper. Before the next request, ask Codex to inspect the current state so it works from your latest changes.

Review both the sequence and individual frames: repeated messages weaken the story, while clipped text or an unreadable capture makes an otherwise useful frame harder to understand.

Use Adaptive Screenshot Specs to carry the accepted design into another supported specification. The composition is a starting point for review, not a guarantee that every layout will need no adjustment.

Check line breaks, device framing, and the size of important UI details in each adapted set. If the app has a different iPad or Mac interface, provide captures that represent that experience.

Ask Codex to adapt the approved set to the destination you need and identify anything that needs refinement. You can keep the source set as the reference for the next adaptation.

When you need another language, localize the accepted screenshot text and, if relevant, the metadata in the same project. Specify the destination locale and add app names or branded terms to Preserved Words.

Review meaning, tone, and line breaks. A concise translation is often more useful than shrinking the headline to fit. Text inside an imported capture is not translated as editable screenshot text, so supply localized app captures when needed.

The guide to creating localized screenshots without rebuilding every design covers these checks in more detail.

Use Preview to check the screenshot order, readability, and consistency. Before handing off the set, confirm:

• Each message matches a real feature shown in the app.
• The right captures appear in each frame and locale.
• Headlines and interface details remain legible.
• The requested screenshot specs and languages are ready.

Export PNGs when you need files. If you use App Store Connect Publishing, review the Target App and the exact assets, metadata, specs, and locales before confirming the send. Uploading these materials does not submit the app for App Review or release it.

Your project stays available in Workspace. For the next update, reopen it, replace the captures or messages that changed, and continue from the design you already approved.