On an iPhone, in portrait orientation, a visitor sees roughly the first two and a half screenshots before they have to lift a thumb. On Android, it’s similar: the feature graphic plus the first couple of screenshots do the work before anyone scrolls. Everything after that is for the minority who were already leaning toward downloading. The first two images are for everyone else.
That’s not a design opinion, it’s a viewport constraint. And most listings we review spend their two most valuable slots on a splash screen and a random feature, instead of the one argument that actually gets someone to tap Get.
If your first two screenshots don’t communicate anything without the app description open next to them, they’re not doing their job.
What “Decide It” Actually Means
Most visitors don’t read your description before deciding to install. They skim the icon, the rating, and the first couple of screenshots, then decide in a few seconds. Your caption text has to work as a headline someone reads mid-scroll, not as a caption someone reads after they’ve already decided to care.
Three Mistakes That Waste the First Slot
1. Leading with a login or splash screen
It’s the first thing a new user sees when they open your app, so it feels natural to lead with it. But it’s the least persuasive image you own. It shows nothing about what the app actually does. Save it for a middle slot, if you use it at all.
2. Writing captions like feature labels
“Track Expenses” describes a feature. “Never argue about money again” sells an outcome. Both are technically accurate, but only one gives a stranger a reason to keep looking. Write the caption first, then pick the screenshot that supports it, not the other way around.
3. Treating all screenshots as equally important
If every screenshot gets the same amount of design effort, none of them stand out. Spend 80% of your design time on the first two. The rest can be simpler, more literal product shots. By that point, the visitor is already convinced or already gone.
How to Actually Test This
Don’t guess which opening argument works best. Test it. Apple’s Product Page Optimization (PPO) lets you A/B test up to three screenshot variants against your current default, split by traffic source if you want. Google Play Console offers Store Listing Experiments for the same purpose on Android. Both are free, both are under-used, and both will tell you in a few weeks what months of internal debate won’t.
A few practical rules for running the test well:
- Change one variable at a time. If you swap the caption and the screenshot and the order, you won’t know which change moved the number.
- Let it run long enough to be real. Low-traffic apps need more time to reach a statistically meaningful sample, so don’t call a winner after three days.
- Test the argument, not just the art style. A different color scheme rarely moves conversion much. A different value proposition often does.
A Framework for the First Two Slots
If you’re starting from nothing, this ordering works for most apps:
- Slot one: the single biggest reason someone should care, in five words or fewer, paired with the app’s core screen in a realistic (not idealized) state.
- Slot two: proof or specificity, such as a number, a result, or the feature that makes you different from the three competitors also showing up in that search.
Everything after slot two can go deeper into features, social proof, or use cases. By then, you’re talking to people who are already listening.
Screenshots don’t work in isolation. App preview videos autoplay ahead of them and set the same first impression under different rules, your icon is doing similar first-glance work everywhere else in the store, and if you run paid traffic, custom product pages let you swap this exact hierarchy per audience instead of compromising on one version for everyone.
Frequently Asked Questions
How many screenshots should the first two actually cover?
One idea each, not a shared idea split across both. The goal is that someone scrolling past at speed understands the core value proposition from screenshot one alone, with screenshot two reinforcing or extending it.
Does screenshot order matter on Android the same way it does on iOS?
Yes, arguably more. Google Play crops differently across devices and often shows screenshots in a horizontal scroll where the first one gets outsized attention, so the same front-loading principle applies.
Should text overlays be used on screenshots?
Short, large, high-contrast text overlays generally help, since most visitors skim rather than read the full description, but overlay text should support the image, not duplicate what’s already obvious from it.
Want a second opinion on your current screenshots before you commit budget to a redesign? We review creative as part of every ASO audit. Let’s talk →