App Store Listings
Part of App store optimisation
Choosing screenshots that explain the product
Select and order app store screenshots that show the real task, useful result and relevant access conditions.
Choose screenshots that let someone recognise the app’s main task and see how it works. Put accurate, informative images first. A polished sequence is less useful if it never shows what a person can do or what result follows.
Plan a short explanation
Before selecting images, write the question each should answer: what is this app for, what does the person do, and what useful state follows? Add another use case only if it matters to the intended audience. These are editorial roles, not store requirements.
For a hypothetical appointment app, opening images might show available times, a booking choice and a confirmed appointment. If booking requires sign-in, account for that step rather than implying immediate access. Use screens from a current product version and sample information that does not expose a real customer.
Apple recommends images captured from the app interface. Put the clearest explanation early in the sequence, so the task is understandable without the rest of the images.
Give each image one job
Check what a viewer can understand at a small size. Frame a busy screen so the important action is legible without hiding context that changes the claim. A short caption can explain an action or benefit, but it should not promise a result the screen does not support.
| Question | What to check |
|---|---|
| What task is visible? | Show a recognisable product action, not only a decorative home screen. |
| What happens next? | Follow a plausible path or label a separate use case clearly. |
| Who can do this? | Account, device, location and paid-feature conditions should not contradict the image. |
| Is the text readable? | Keep captions legible without covering essential controls. |
| Is the screen current? | Match interface labels and features to the released app. |
Screenshot Quality Check – What to Verify
- Task visibilityIs the key action clear at small size? Avoid decorative home screens.
- Next step clarityDoes the sequence follow a logical path or clearly label separate use cases?
- User eligibilityEnsure account, device, location and paid-feature conditions match the image.
- Text readabilityCaptions must be legible and not obscure essential controls.
- Interface accuracyScreens must reflect the actual features and labels in the released app.
Check store and language requirements
Apple accepts one to ten screenshots and publishes specifications for supported device sizes. Where an app preview is present, Apple says it precedes screenshots on iPhone, iPad, Mac and Apple TV product pages. Check each store’s current upload requirements when preparing files.
Where images contain words, use language versions that match the app’s supported experience. For an Australian listing, check any displayed wording, date, place or currency against the actual Australian experience.
App Store Screenshot Requirements (Australia)
- Apple App Store – Max screenshots
- 10
- Australian language support
- Use Australian English spelling and local context (e.g., GST, ABN, ATO, superannuation).
- Currency format
- AUD (Australian Dollar) – ensure pricing reflects local values.
- Date format
- DD/MM/YYYY for Australian listings.
Check comprehension
A person unfamiliar with the app can view the sequence without the description and explain the promised task, first action and apparent limits. Revise images that cause a mistaken expectation.
A later experiment can compare alternative screenshot messages. For initial selection, each image should accurately represent the current product and help a visitor decide whether it meets their need.
![Write app descriptions around real tasks: Lead with the main task and its useful result, using 'can [task] to [result]'; Explain features that make the task possible, including saving, sharing or returning to work; Place limits like subscriptions or device needs near the claims they qualify. Writing an app description around actual use cases](/covers/writing-an-app-description-around-actual-use-cases-640.webp?v=4fc47029)
