Store promises: the deception that destroys trust
Massive promises. Heavily retouched screenshots. AI everywhere. Everything looks incredible. Then the user downloads… a…
Your app store screenshots are your most-viewed marketing material. Most developers treat them as an afterthought. The best ones treat them as a conversion tool.
Before a user reads a single word of your app description, they have already scrolled through your screenshots. You will find plenty of articles quoting a precise conversion uplift for getting them right — 18%, 20%, 35%. Treat all of those as advertising: every one traces back to a company selling app store optimisation, and there is no independent research behind them.
What is verifiable is what the two stores require, and both are stricter and more specific than most teams realise. Apple's guideline 2.3.3 is the starting point : "Screenshots should show the app in use, and not merely the title art, login page, or splash screen. They may also include text and image overlays." (Apple App Store Review Guidelines 2.3.3, 2026). Note the second sentence — overlays are explicitly allowed, so "no text in screenshots" is simply false for Apple.
Google is the one with the hard number. Its preview-asset guidance caps marketing text : "Taglines should not take up more than 20% of the image", and it asks that "Screenshots must demonstrate the actual in-app or in-game experience" (Google Play Console Help, 2026). The most important consequence is that the standard ASO template — a big headline banner above a phone frame — can breach the 20% cap on its own.
A screenshot is a promise about what the user's life will look like if they download your app — but it has to be a promise the app keeps, because both stores treat the listing as part of the product. Show the result of using the app in a real context rather than a settings screen with a caption.
The key difference between the two platforms is worth knowing before you brief a designer. Google explicitly discourages device frames, listing "Device imagery (as this can become obsolete quickly or alienate some users)" among elements to avoid, bans call-to-action text such as "Download now", and bans any claim of ranking or awards — "do not use words like 'Best,' '#1,' 'Top'" (Google Play Console Help, 2026). Apple takes the opposite line on frames but requires them to be Apple's own, used "as is and without modification" (Apple Marketing Resources and Identity Guidelines, 2026). In short : one set of screenshots for both stores usually breaks one of them.
The first screenshot in your set is the most critical. It is the only one most users will see before deciding whether to keep scrolling. It should communicate your core value proposition in under three seconds. A screenshot with a clean UI, a short punchy headline, and a clear visual benefit passes that test. A screenshot of an empty state with no context fails it.
Effective app store screenshots typically combine three elements: the app UI itself, a short text overlay that tells the story behind the UI, and a device frame or background that provides visual context. The text should be short — five words is better than fifteen. It should complete the thought "This app lets you..." in a way that creates desire, not just description.
Color matters. Your screenshots should feel cohesive as a set and consistent with your brand. Users scroll through them in sequence, so each screenshot should either deepen the same story or introduce a new compelling benefit. Avoid the trap of dedicating screenshots to minor features — every screenshot that does not communicate a strong benefit is a wasted opportunity.
Both the App Store (via Apple's Product Page Optimization) and Google Play (via Store Listing Experiments) allow developers to A/B test screenshots directly. This is one of the most powerful optimization levers available for free, and it is dramatically underused. Running a simple test with two versions of your first screenshot can produce conversion rate data that would cost thousands of euros to gather through any other channel.
I help clients develop screenshot strategies as part of the launch planning process and set up A/B tests post-launch to continuously improve the conversion rate on their listing. What happens before the download matters as much as what happens inside the app.
Ready to turn your app store page into a proper conversion asset? Let's talk about your listing.
12 years of experience, iOS + Android, one dedicated contact. Free 30-minute call to scope your need — no commitment, no jargon.
Book a call →
Before a user reads a single word of your app description, they have already scrolled through your screenshots. You will find plenty of articles quoting a precise conversion uplift for getting them right — 18%, 20%, 35%. Treat all of those as advertising: every one traces back to a company selling app store optimisation, and there is no independent research behind them.
What is verifiable is what the two stores require, and both are stricter and more specific than most teams realise. Apple's guideline 2.3.3 is the starting point : "Screenshots should show the app in use, and not merely the title art, login page, or splash screen. They may also include text and image overlays." (Apple App Store Review Guidelines 2.3.3, 2026). Note the second sentence — overlays are explicitly allowed, so "no text in screenshots" is simply false for Apple.
Google is the one with the hard number. Its preview-asset guidance caps marketing text : "Taglines should not take up more than 20% of the image", and it asks that "Screenshots must demonstrate the actual in-app or in-game experience" (Google Play Console Help, 2026). The most important consequence is that the standard ASO template — a big headline banner above a phone frame — can breach the 20% cap on its own.
A screenshot is a promise about what the user's life will look like if they download your app — but it has to be a promise the app keeps, because both stores treat the listing as part of the product. Show the result of using the app in a real context rather than a settings screen with a caption.
The key difference between the two platforms is worth knowing before you brief a designer. Google explicitly discourages device frames, listing "Device imagery (as this can become obsolete quickly or alienate some users)" among elements to avoid, bans call-to-action text such as "Download now", and bans any claim of ranking or awards — "do not use words like 'Best,' '#1,' 'Top'" (Google Play Console Help, 2026). Apple takes the opposite line on frames but requires them to be Apple's own, used "as is and without modification" (Apple Marketing Resources and Identity Guidelines, 2026). In short : one set of screenshots for both stores usually breaks one of them.
The first screenshot in your set is the most critical. It is the only one most users will see before deciding whether to keep scrolling. It should communicate your core value proposition in under three seconds. A screenshot with a clean UI, a short punchy headline, and a clear visual benefit passes that test. A screenshot of an empty state with no context fails it.
Effective app store screenshots typically combine three elements: the app UI itself, a short text overlay that tells the story behind the UI, and a device frame or background that provides visual context. The text should be short — five words is better than fifteen. It should complete the thought "This app lets you..." in a way that creates desire, not just description.
Color matters. Your screenshots should feel cohesive as a set and consistent with your brand. Users scroll through them in sequence, so each screenshot should either deepen the same story or introduce a new compelling benefit. Avoid the trap of dedicating screenshots to minor features — every screenshot that does not communicate a strong benefit is a wasted opportunity.
Both the App Store (via Apple's Product Page Optimization) and Google Play (via Store Listing Experiments) allow developers to A/B test screenshots directly. This is one of the most powerful optimization levers available for free, and it is dramatically underused. Running a simple test with two versions of your first screenshot can produce conversion rate data that would cost thousands of euros to gather through any other channel.
I help clients develop screenshot strategies as part of the launch planning process and set up A/B tests post-launch to continuously improve the conversion rate on their listing. What happens before the download matters as much as what happens inside the app.
Ready to turn your app store page into a proper conversion asset? Let's talk about your listing.
12 years of experience, iOS + Android, one dedicated contact. Free 30-minute call to scope your need — no commitment, no jargon.
Book a call →We write about mobile app development, user experience design, App Store optimization, project management, and industry trends. Our articles are based on real experience from client projects.
We aim to publish regularly with a focus on quality over quantity. Each article is written from hands-on experience, not generic advice.
Absolutely! Feel free to reach out via our contact page or book a consultation. We love hearing what questions our readers and clients have.
Most of my projects run remotely, and in practice that changes very little. We talk over video whenever you need to, not only at major milestones, and you can reach me with questions at any point during the project — I always answer.
You can also write to me directly on WhatsApp: same number I use every day, a French professional line that works internationally.