Strategy

A/B testing your store screenshots

Both stores will split your traffic and tell you which gallery wins. Most teams never switch it on, and the ones who do usually stop the test three days early. Here is how to run it so the answer means something.

Reading time: about 7 minutes

The two tools

Apple App Store

Product Page Optimization

Where
App Store Connect → your app → Product Page Optimization
Variants
Up to 3 treatments plus the control
Traffic
You set the share of traffic each treatment receives
Reports
Impressions, product page views, conversion rate, improvement vs baseline

Treatments require App Review approval before they start serving.

Google Play

Store Listing Experiments

Where
Play Console → Grow users → Store presence → Store listing experiments
Variants
Multiple variants, testing graphics or text
Traffic
Configurable split across the audience you target
Reports
Installs per variant with a confidence interval Play calculates for you

Free, and available for the default listing or a localised one.

What to test, in order

Ranked by how much of your conversion the variable actually controls.

  1. 1

    The first screenshot

    It appears in search results and is cropped on the product page. Nothing else you can test has this much leverage.

  2. 2

    The first headline

    Same image, different line. Isolates message from design, which is the cleanest test you can run.

  3. 3

    Portrait vs landscape first frame

    A landscape opener occupies more of the gallery row. It is a big, cheap swing worth testing once.

  4. 4

    Art direction across the set

    Bold Contrast against Minimal Light, whole gallery. Coarse, but decisive when you are choosing a direction.

  5. 5

    Screenshot order

    Same assets, reordered. Costs nothing to produce and sometimes moves conversion more than new artwork.

  6. 6

    Trust proof placement

    Ratings or press moved from frame five to frame two. Tests whether your audience needs reassurance early.

Six rules for a test worth trusting

One variable per test

Change the first screenshot or the first headline, never both. A two-variable test that wins tells you nothing about which change to keep.

Run for one to two weeks minimum

Store traffic has a weekly rhythm. A test stopped on day three is measuring the weekend, not your artwork.

Do not stop early on a good day

Peeking at a running test and stopping the moment it looks positive is how teams ship changes that are noise. Decide the duration before you start and hold it.

Expect modest wins

A 5–15% lift on conversion is a real, compounding result. Claims of doubling conversion from a screenshot swap almost always come from a listing that started badly broken.

Low-traffic apps need a bigger difference

If you get a few hundred page views a week, only a large effect will ever clear the noise. Test coarse changes — a whole art direction, not a word — or fix the obvious problems first and skip testing.

Re-test after a redesign or a season

A winner is a winner for the artwork and the audience you had. Both change. Re-run after a major UI change and, if your category is seasonal, at the turn of the season.

Reading the result honestly

Four outcomes that are easy to misread in your own favour.

A win with overlapping confidence intervals
Not a win. Play reports the interval for a reason; if it crosses zero, keep running or accept there is no difference.
A win driven by one country
Segment before you ship. A treatment that wins overall by winning hugely in one small market can lose everywhere else.
A conversion win with lower retention
A more aggressive headline can convert better and attract worse-fitting users. Check the downstream numbers before adopting.
A flat result
Genuinely useful. It means the variable you tested is not what is limiting you — move your attention to a different one rather than iterating on it.

Testing questions

Can you A/B test App Store screenshots?+

Yes. Apple's Product Page Optimization lets you run up to three treatments against your live page, with screenshots, app icon or preview video as the variable. Treatments go through App Review before they start serving.

Is Google Play screenshot testing free?+

Yes. Store Listing Experiments are built into Play Console at no cost and report installs per variant with a confidence interval. It is the cheapest conversion work available to an Android app, and most teams never switch it on.

How long should a screenshot test run?+

One to two weeks at minimum, so the test covers full weekly cycles, and longer if your traffic is low. Decide the duration before you start — stopping early on a favourable day is the most common way these tests mislead.

What should I test first?+

The first screenshot, then the first headline. Those two carry most of the conversion, because search results show only the first two or three frames and most people decide in seconds.

How do I produce the variants?+

Generate them from the same upload. Asking for multiple art directions gives you genuinely different compositions of the same screen rather than recolours, which is what a coarse-variable test needs.

Produce the variants in one batch

Four art directions of the same screen, generated together, is exactly the input a coarse-variable test needs.

See the four directions