ASO Screenshot Tool for Testable, Localized Store Visuals

On the App Store, Apple says (opens in a new tab) the first one to three screenshots appear in search results when no app preview is available, depending on their orientation. Apple advises making sure these images highlight the essence of your app. App previews, when present, always come before screenshots (opens in a new tab).

On Google Play, screenshots may appear (opens in a new tab) in search or on the homepage as well as on your store listing. In both stores, your first images often reach people who haven't opened your listing yet.

• Put the strongest benefit on slide one, not onboarding or a login screen.
• Write headlines people can read at thumbnail size: a verb and an outcome, such as "Track spending in seconds".
• Show real UI with realistic data so the screenshot matches what users see after they install.

Product page optimization (opens in a new tab) lets you compare alternate app icons, screenshots and app previews against your original product page. You can test up to three treatments, a test runs for up to 90 days, and you choose what share of traffic goes to the test.

Each treatment can be localized into all of your app's languages or only the ones you choose. Apple notes that more localizations can mean a longer wait for meaningful results. New metadata in a treatment must be approved by App Review before the test can go live.

Play Console offers two kinds of store listing experiments (opens in a new tab). A default graphics experiment tests icon, feature graphic and screenshot variants in your default listing language. A localized experiment can test the icon, feature graphic, screenshots and descriptions in up to five languages.

StoreLocale covers producing the assets. It helps you build test variants quickly and keep every language in step.

• Variants: duplicate slides, change one headline or layout, and keep the rest identical so the test measures one change.
• Localization: text detection and translation are free. The AI repaint that puts translated text inside the app screen costs 1, 2 or 4 credits per image, and unchanged assets aren't billed again when you re-export.
• Export: one ZIP of PNGs organized as Platform / locale / size, for example App Store (iOS)/fr/iphone-6-9/01-track-spending.png.
• Languages: 32 target languages, including Simplified and Traditional Chinese and right-to-left Arabic and Hebrew.

Example: to test a benefit headline in Japanese, German and Brazilian Portuguese on Google Play, duplicate the control set, rewrite slide one, and localize both sets into those three languages. Then export once and upload the variant to a localized experiment. StoreLocale has one generic Portuguese variant, so review its wording for Brazil before uploading.

Apple notes that adding localizations to a test can mean a longer wait for meaningful results. Plan which markets get which variant before you produce anything, and keep the change identical across languages so results stay comparable.

• Test one element at a time, such as the slide-one headline, so a result points to a single cause.
• Start with markets that bring enough traffic to finish the test, and add smaller ones once a winner is clear.
• Keep the control set unchanged during the test, and archive each exported ZIP so you can match results to the exact files.

• It doesn't run A/B tests or measure conversion. Tests and results live in App Store Connect and Play Console.
• It doesn't upload files to either console. You upload the exported PNGs yourself.
• It doesn't research keywords or rankings, and it can't promise a ranking or conversion change.