App Store Screenshots for iPhone and Android

Beautiful Figma frames still fail if they ship at the wrong resolution, miss a required device, or only exist in English. This guide is the production manual: what to export, how to organize UAE bilingual sets, and how to QA before App Store Connect and Play Console uploads.

Why device coverage still matters

Apple frequently requires screenshots for specific device classes (e.g., 6.7" and additional sizes depending on current console rules). Google Play focuses on phone screenshots plus optional tablet/Chromebook assets and a feature graphic. Always confirm the live console checklist the week you ship—requirements change with hardware generations.

Operational rule: maintain a source canvas system that scales cleanly to each required export rather than redesigning per device in panic the night before review.

Recommended production system

1. Master storyboard (10 frames max concept; ship 6–8 strong ones).
2. Locale variants: English (UAE) and Arabic (UAE) as full sets.
3. OS variants if UI differs materially (iOS vs Android components).
4. Export presets named by store + device + locale.
5. Archive previous seasonal sets for rollback.

Naming convention example

ios_67_en_01_value.png ios_67_ar_01_value.png play_phone_en_01_value.png play_feature_en.png

Chaos in filenames causes wrong-locale uploads—common when agencies rotate freelancers.

Layout rules that survive real devices

• Keep critical caption text inside a safe central column; store UI and rounded corners crop edges.
• Prefer UI scale that remains legible when the store shows partial carousels.
• Do not rely on status bar content as part of the message; it gets stylized or replaced.
• Test Arabic line heights; translated captions often run longer—allow flexible caption boxes.

Feature graphic (Play-specific)

The 1024×500 feature graphic appears in Play surfaces and ads contexts. Treat it like a billboard: brand mark, short benefit, high contrast. Avoid tiny text. Localize if your Play listing is bilingual—many teams forget and run English graphics over Arabic listings.

Capturing clean UI

• Use demo accounts with realistic AED amounts and UAE addresses.
• Turn off debug banners and localhost API errors.
• Mind privacy: no real customer names, plate numbers, or Emirates ID details in marketing captures.
• Align light/dark mode with brand; sudden dark-mode only screenshots can look like a different app if the store icon is bright.

Localization matrix

If budget forces a sequence, ship EN complete on both stores, then AR screenshots before scaling Arabic UA—not months later.

QA checklist before submit

• ☐ All required sizes attached in consoles
• ☐ No mixed locales in a single language listing
• ☐ Videos meet duration and audio specs
• ☐ Feature graphic not letterboxed incorrectly
• ☐ File weights reasonable for upload reliability
• ☐ Side-by-side compare with live app version
• ☐ Legal approved any badge or partner logo

Common UAE team failures

• Delivering only English iPhone 15 frames and stretching them for Android.
• Arabic captions designed by non-native speakers with broken definite articles—users notice.
• Seasonal campaign live in Meta ads while store screenshots still show last year’s White Friday.
• Using competitor map data or restaurant names in demos without rights.

Collaboration with paid UA

Export CPP-specific iPhone sets that match ad angles (e.g., “0 fee transfers” vs “joint accounts”). Android feature graphics should echo UAC creatives so the handoff from ad to store does not feel like bait-and-switch—policy and performance both care.

Cadence

• Major app release: reshoot if UI chrome changed.
• Seasonal: swap frames 1–3 and feature graphic.
• Quarterly: full audit against competitors’ visual density.

Device-correct screenshots are table stakes; conversion craft lives in messaging. Keep this pipeline boring and reliable so marketers can experiment weekly without engineering fire drills.

Size strategy without spreadsheet despair

Maintain one design master per locale at the largest common phone size you support, then use constrained export rules: scale UI captures from simulators at clean assets, not upscaled blur; keep caption components in relative layout so shorter Android widths do not clip Arabic; validate tablet screenshots only if tablet is a real product surface—empty iPad frames of a phone-only UX look careless. When Apple adds a new required size, update the export preset checklist in the same sprint as the marketing request—treat it like an engineering dependency.

Localization file management

Store assets in a structure marketing and eng share, for example /store/YYYY-MM/campaign_name/{ios,play}/{en,ar}/. Include a README with live copy deck links and approval dates. When paid UA asks what is live on a given Custom Product Page, answer from git or DAM—not memory.

Colour and brand systems under store chrome

Store backgrounds and light/dark system settings affect perceived contrast. Test icon + first screenshot adjacency: if both are low-contrast greys, search results flatten. Fintech brands often use deep greens or blues—ensure caption chips still pop. Avoid seasonal filters that break brand recognition (icon stays constant while screenshots go full neon)—users should still connect ads, icon, and frames.

Collaboration with engineering for true UI

Marketing-only mockups diverge from production fonts and spacing. Prefer staging builds with demo mode, feature flags that unlock rich sample catalogues, and snapshot pipelines that can feed marketing when stable. The closer screenshots are to production, the fewer “app looks different” reviews you earn after install.

Upload and review day runbook

Freeze copy deck; export all sizes; second person verifies locale folders; upload to consoles; preview on web and device; submit with notes if UI changed significantly; after approval, archive previous set as rollback. Timebox this runbook so it does not slip past campaign start dates. Track operational KPIs: hours from brief to live, error rate on uploads, and number of hotfix resubmits per quarter—these measure whether production quality is under control.

Related guides

• Seasonal ASO: Ramadan and Shopping Events
• Track ASO KPIs: Impressions, CVR, Rank
• Paid UA vs ASO: How They Work Together
• ASO Tools Worth Using in 2026
• Custom Product Pages and Store Experiments
• Meta Ads for UAE Businesses: Start Here

---

Part of the Dubai Marketing Playbook by Shabang — practical marketing for UAE businesses.