The asymmetry nobody designs for
On both stores, your first one or two screenshots appear in search results and above the fold on the listing. Everything after that requires a deliberate horizontal swipe, which most visitors never make. Yet most sets are designed as an even sequence of eight, as though each panel gets equal attention.
Design as though panels one and two are the whole listing, and the rest are for the minority who are already interested.
What frame one has to do
One job: make the outcome obvious to someone who has never heard of your app and is not reading carefully. Not your logo. Not a welcome screen. Not your cleverest feature. The outcome.
A test that costs nothing: show frame one to someone unfamiliar with the app, for two seconds, then ask what the app does. If they cannot answer, no amount of work on panels four through eight will help.
Ordering the rest
- The promise. The outcome, stated plainly.
- The proof. The actual UI doing the thing, so the promise is credible.
- The differentiator. The one reason to pick you over the obvious alternative.
- Depth. Secondary features, for people already convinced.
- The nudge. Whatever reduces the last hesitation — privacy, offline, no account needed, works with what they already use.
Captions
Short enough to read at a glance, in the user’s language rather than yours. The recurring mistakes are feature names with no outcome attached, generic claims that any app could make, and captions long enough to need reading rather than scanning.
Keep the caption size consistent across the set. Inconsistent caption sizes — one panel’s headline wrapping to three lines while another sits on one — is one of the clearest amateur tells, and it is entirely avoidable.
What gets you removed rather than ignored
Never put a number inside a device screen that is not real. Fabricated ratings, invented download counts, made-up streaks, fake review quotes. Both stores treat this as misrepresentation, and unlike a weak caption it is a removal risk rather than a conversion problem. Our pipeline is built not to produce it.
Then actually test it
Everything above is a prior, not a result. Apple’s Product Page Optimization and Google’s Store Listing Experiments both let you run a variant against your live listing with real traffic. Change one thing at a time, start with frame one, and let the traffic settle the argument. More on that on the product page optimization page.