App Store Optimization
App creative and screenshot testing
One part of App Store Optimization, described on its own: find out which screenshots actually earn the install instead of arguing about them.
In plain terms, what is app creative and screenshot testing?
Find out which screenshots actually earn the install instead of arguing about them. In practice that means structured tests through the native experiment tools on both stores, sized to reach significance, and then the harder half: first-screenshot work, which carries most of the decision and gets the least attention.
Why this work exists
It rarely appears in a post-mortem, and it is often the answer.
Within App Store Optimization this is the item with the clearest cause and effect, which is why it is scoped on its own.
The nearest piece of work to it is measuring installs that came from the store against installs that came from ads. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
When it is right, nobody has to ask permission to act on it.
The gap between that and where most accounts start is why this is scoped as app creative and screenshot testing rather than as a line inside something larger. Making the app discoverable through Siri and the assistant layer, not only search is the usual second step once it is in place.
When this is the right work
What makes this the next piece of work:
- Your screenshots were made at launch and never tested
- Page view to install conversion sits below category average
- Creative decisions get made by whoever is most senior in the room
If none of those is true, something else is probably the constraint, and the App Store Optimization overview maps the alternatives. The usual neighbours are finding the localisations that are worth doing properly and watching what the category ranking does after each release.
What the work covers
The work itself:
- Structured tests through the native experiment tools on both stores, sized to reach significance. The effort here scales with the size of the estate, not with the size of the brief.
- First-screenshot work, which carries most of the decision and gets the least attention, done before anything downstream is committed to.
- App preview video testing, including whether having one helps your category at all. Boring, necessary, and the first casualty when a deadline moves.
- Localised creative for the markets where a translated caption is not enough. One pass is rarely enough; the second is much faster.
How it runs
How an engagement on this actually proceeds.
Writing it down for the next person
The reasoning gets recorded alongside the result, so a decision taken in March can still be defended in September by somebody who was not there.
Deciding what not to do
A list of things deliberately left alone, with the reason for each. It saves the same conversation happening four times over the following year.
The second look
A fortnight after the first pass, the same ground gets covered again with fresh eyes. The second pass finds a different class of problem from the first.
What each part runs into
The four parts do not fail in the same way:
- Structured tests through the native experiment tools on both stores, sized to reach significance: the Dallas version of this has to deal with a procurement step nobody accounted for
- First-screenshot work, which carries most of the decision and gets the least attention, where a Melbourne engagement contends with a measurement baseline that was never taken
- App preview video testing, including whether having one helps your category at all – working in Ajmer this means accounting for a language mix the content has to match rather than assume
- Localised creative for the markets where a translated caption is not enough, and in Pune the constraint on it is an enquiry path that runs through a messaging app rather than a form
The failure mode
Stopping a test early because it looks good. App store experiments are noisy and an early read is usually wrong.
The damage is less in the wasted work than in the conclusion it leads to.
How it is measured
Page view to install conversion rate, by variant and by market. It is reported with the existing metrics rather than replacing them, because a new number nobody recognises persuades nobody.
Two people should be able to calculate it independently and get the same answer. If they cannot, it is the wrong measure.
What you end up with
The concrete artefact is a tested creative set with the numbers behind each decision, and a backlog of the next hypotheses worth running.
Structured so one section can be lifted out and sent on without the rest.
How it differs by sector
By sector, the same scope produces different priorities:
- In Ecommerce and retail the binding constraint is that margin per order decides everything, and the product feed is usually the weakest asset.
- Manufacturing and industrial: the thing that changes the scope here is that low volume, high value, and a specification sheet that decides the deal.
- For B2B services, a buying committee, a long cycle, and attribution that has to survive both. and that shapes how far this can go.
The industry pages carry the rest of that detail. Ecommerce and retail and Manufacturing and industrial are the two where this piece of work most often decides the outcome.
Common questions
How long does a creative test need?
Long enough to reach significance at your traffic, which for most apps is two to four weeks. Shorter than that and you are reading noise.
Do preview videos help?
In some categories a great deal and in others not at all. It is cheap to test and expensive to assume.
Will we speak to the person doing the work?
Yes. The person who diagnoses app creative and screenshot testing is the person who does it and the person on the review call. Handing a finding to somebody else to execute is where most of the value leaks. There is more on this in Conversion Rate Optimization, and a different angle on it in Digital PR and Link Building.
What happens if we stop after this?
You keep everything: A tested creative set with the numbers behind each decision, and a backlog of the next hypotheses worth running. Documented so your own team can continue it, including the parts we would have done next and why. The short version is here. Lead form or Landing page and Local SEO or National SEO are the long ones.
What if we disagree with the diagnosis?
Then we look at the data together. Page view to install conversion rate, by variant and by market is the test, and a finding that cannot survive being questioned is not a finding worth acting on. What does a technical SEO audit actually check? goes through this properly, and What is a good conversion rate? shows where it stops working.
Ask about app creative and screenshot testing
Whatever context you have is enough to start. The first reply is a read on the problem, not a proposal.
Begin with the diagnosis, not the pitch
We will tell you if the answer is that you do not need us yet. That happens often enough to be worth saying out loud.