App Store assets: from screenshots to a sales system

More Store space means more responsibility

On 5 October, Apple introduced new image and video formats for product page headers and search results. They arrive alongside a central Asset Library and an App Store Connect preview that shows product pages and search results in Dark Mode, on different devices and in different orientations.

At first this sounds like a design task: export two more formats, upload them and move on. In practice, the role of the Store presence is changing. A row of screenshots is becoming a small content system that has to keep brand, value, product reality, seasonality and localisation aligned.

Responding with more one-off files creates a collection that may be attractive but cannot be maintained. Treating assets as a product makes it possible to prepare releases calmly, test messages and switch campaigns without starting again every time.

Four jobs need four different pictures

One Store asset should not try to explain everything. Existing and new surfaces have distinct jobs:

• The search result asset should make the app's purpose obvious at a glance.
• The product page header establishes tone and expectation before people explore the details.
• Screenshots show the real flow and provide evidence for specific benefits.
• App previews demonstrate motion, interaction and context of use.

Apple notes that In-App Events, previews and screenshots may still appear when no dedicated search result asset is supplied. That is not a reason to fill every field. It is a reason to decide deliberately which surface does which job.

For a travel app, search could make the destination and route benefit instantly clear. The header creates a sense of place and brand. The first three screenshots then move from planning to live navigation to a saved trip. Reusing one key visual in four sizes would waste that narrative.

Start with a message, not a format

Before opening Figma, each asset series needs one short sentence: Who is this app valuable to at this moment, and why?

That sentence produces three layers:

1. Promise: the most important benefit a new visitor should understand.
2. Proof: the real feature or content that supports the promise.
3. Action: the next useful step in the story, not necessarily a painted-on download command.

For a family app, the promise might be “know that everyone arrived safely”. The proof is a real map or status view. The story then continues into notifications and routines agreed by the family. Communication stays concrete without burying the interface in advertising copy.

Apple recommends one clear idea for headers and an immediately recognisable purpose in search results. That constraint is useful: an asset is not a pitch deck.

Build a system from components

A resilient template is not one rigid master image. It is a set of reusable rules:

• a defined focal area that survives cropping;
• a small number of colour roles rather than baked-in backgrounds;
• a set of approved interface captures;
• one visual treatment for product, people or illustration;
• short messages that can be localised;
• light and dark variants;
• documented export sizes and filenames.

The focal area matters. Apple advises keeping key content in a safe central area because assets can appear differently across devices and orientations. A layout cannot work only in its most flattering desktop preview. It must retain one clear idea after an aggressive crop.

We would define a universal visual first, then derive header, search and campaign variants from it. The formats remain related, but each is recomposed for its own context. Recognition comes from systematic choices, not identical placement.

Use the Asset Library as a production plan

The new Asset Library in App Store Connect centralises images, videos, previews and screenshots. Assets can be uploaded and submitted for approval before they are needed. A seasonal visual can therefore be prepared in advance and activated later instead of entering production on campaign day.

To prevent the library from becoming another dumping ground, each asset needs at least:

• market and language;
• format and intended surface;
• product version or UI state;
• campaign and validity period;
• approval status;
• owner;
• link to the editable source.

A name such as en-GB_search_winter_v03_approved is not glamorous, but it prevents somebody uploading “final-final-new” minutes before release. Editable sources remain in the design system; only reviewed exports reach the Store.

Separate the product release from the marketing release

Many teams create Store screenshots only once the app build is finished. Three deadlines then collide: QA verifies the application, marketing writes the copy, and design chases current screens through device mock-ups.

A staggered workflow is calmer:

1. Product defines visible changes and the UI freeze early.
2. Marketing decides whether they require a new message or only updated proof.
3. Design works with stable test data and defined states.
4. Localisation receives copy with context, not a spreadsheet of isolated words.
5. QA compares the asset, the actual app and the Store preview.
6. Approved assets enter the library before launch.

Apple allows assets to be submitted either with a new app version or through the Asset Library. That separation creates useful lead time. It does not replace an accuracy review: anything promised in an image must be true in the app that ships.

Localisation means recomposition

A German sentence is often longer than its English source. Arabic changes reading direction; Japanese changes typographic density. Symbols, people and seasonal imagery also carry different meanings across markets.

Templates therefore need flexible text zones rather than dependence on one line length. Better still, the visual idea works before copy is added and text merely makes it precise. Apple recommends short phrases and requires overlaid text to be localised for the languages the app supports.

Review by market, not only by language. A Hamburg winter campaign may feel odd in Sydney in December. The Asset Library is particularly useful for regional and seasonal sets, provided the team records their target market and validity clearly.

Preview is a test, not an approval photo

The new App Store Connect preview shows headers, screenshots, metadata and search-result creative before publication. This is where visual design and product reality meet.

Our review would include at least these questions:

• Is the main idea clear in the smallest relevant presentation?
• Does it work in both light and dark appearances?
• Is any important element too close to a vulnerable edge?
• Does the interface represent the current product?
• Are claims verifiable and correct for the target market?
• Do header, search and screenshots form one story rather than three campaigns?
• Does the idea work without audio and without a long explanation?

Apple has also released new screenshot and preview specifications for iPhone Duo. From April 2027, new submissions must include iPhone Duo screenshots. That makes a useful stress test for any asset system: if one new device triggers a complete rebuild, the template was probably too rigid.

Measure what the asset actually changes

Beauty is not an experiment. A clear hypothesis is: “A header showing the concrete outcome helps first-time visitors more than an abstract brand image.”

Apple points to Product Page Optimization for testing alternative header visuals. Change one important variable per test where possible: the idea, image, order or benefit. If the visual, subtitle, screenshots and campaign all change at once, even a better result will not explain what caused it.

Store metrics should be accompanied by qualitative signals. Can a test participant explain the purpose after five seconds? Do they expect a feature that does not exist? Does the message match support questions and the reasons people actually buy, stay or leave?

A winning option should not simply be adopted forever. Record it as new knowledge in the system: market, audience, hypothesis, period and result.

The smallest useful start

This does not require a months-long rebrand. One focused session can establish a strong foundation:

1. inventory the first three screenshots and the new search presentation;
2. select one audience and one core promise;
3. build a universal visual with a safe focal area;
4. derive search, header and three connected screenshots;
5. test German and English with real copy lengths;
6. inspect every option in light, dark, device and orientation previews;
7. define one test and one success criterion.

The decisive change does not happen in the export dialog. Store assets move from a final design chore before release to a reusable part of the product. That is when they can sell without becoming louder — because each image knows which question it has to answer.

Sources

• Apple Developer: Showcase your apps with new assets on the App Store
• Apple Developer: App Store asset best practices and resources
• Apple Developer: Prepare and submit your apps for iPhone Duo