A stranger spends somewhere around six or seven seconds on your App Store page before they install or swipe away. Most of that is the first screenshot.
Not your description. Nobody reads the description until after they've half-decided. Not your feature list — that's below the fold on a screen they already left. The first one or two screenshots are the whole pitch, and for most apps that pitch is some version of:
here is our diagram canvas, here is our notebook, here is our 3D view
A tour. A product menu. Every screen says look what we built, and not one of them says look what you get.
We shipped exactly that for Xenition — our AI workspace, a Flutter app on iOS and Android. Five screenshots, each a clean, honest tour of a feature. They were nice. They did nothing.
So we threw them out and rebuilt the set around one question the old ones never asked: what does this person's life look like after they install? These are the seven rules we now run every single screenshot through before it ships.
I'll be straight about the thing everyone wants and I can't honestly give you: a clean before/after conversion number. We changed too much at once to pin a percentage on any one move. What I can give you is the framework, and the one test that tells you in ten seconds whether a concept is going to work.
1. The first screenshot is the entire pitch — so lead with the value, not the UI
Screen one has one job: make a stranger understand, instantly, why this app is worth their next thirty seconds. Everything after it is for the 20% who swiped. Screen one is for everyone.
Which means the most expensive mistake is spending it on your prettiest UI instead of your clearest promise.
And here's the part that stung: we couldn't write a good screen one until we admitted we didn't actually know, in one sentence, what we were promising. We'd been describing the app to ourselves — "it's an AI workspace with a canvas and a notebook and—" — a feature list wearing a value prop's clothes.
The rule: you don't start screen one in a design tool. You start it by finishing the sentence "after you install this, you can finally ___." If you can't finish it, no amount of design saves the screenshot.
That sentence comes from research — your reviews, your support tickets, the words real users use — not from a meeting where everyone already knows what the app does.
2. Sell the outcome, not the feature
Nobody wants an AI calorie tracker. They want to lose fifteen pounds without thinking about it. Nobody wants a meditation app. They want to stop lying awake at 2am. Nobody wanted our notebook. They wanted to stop pasting half-finished thoughts between four different apps.
The feature is the how. The outcome is the why, and the why is the only thing a stranger is shopping for.
This is the one that quietly rewrites every other decision. Once you know the outcome you're selling, the headline writes itself, the visual picks itself, and whole screenshots delete themselves because they were selling a how nobody asked about.
The rule: write the outcome first, in the user's words, then ask what to show to prove it. Never the other way around.
3. One screenshot, one message
The strongest concepts are almost always the simplest. Every screenshot gets exactly one primary message, and everything else on it exists only to support that one message.
You're allowed secondary information. You are not allowed a second thing that competes for the eye. The test is brutal and useful: if a stranger looked at this screen for one second and then you took it away, what's the one thing they'd remember? If the answer is "a few things, I guess," you have three weak screenshots glued into one.
The rule: one idea per screen, loud enough that it survives a one-second glance. If two ideas are fighting, that's two screenshots.
4. Make the idea legible with every word hidden
People look before they read. Always. The image lands in the eye before the headline gets a vote, which means if your concept only makes sense after someone reads the copy, you've already lost the ones who didn't.
So we do one exercise on every concept, and it's the most valuable ten seconds in the whole process:
Cover every headline and every caption. Can you still roughly tell what the app does?
If yes, you have a real visual hook and the copy is a bonus. If no — if the screenshot collapses into a meaningless UI mockup the moment the words disappear — there's a stronger visual idea you haven't found yet. Go find it. The copy should make a clear idea clearer. It should never be the thing carrying the idea.
The rule: hide the text. If the screenshot stops making sense, the problem was never the copy.
5. Put a human in it
Our eyes are wired to find other people. In a wall of near-identical app listings, a face, a hand, or a real-life moment grabs attention faster than one more floating phone mockup — every time.
A human element does something a UI screenshot can't: it lets the viewer picture themselves using the app instead of just inspecting it. There's a difference between "here is a dashboard" and "here is a person getting their evening back because of this dashboard," and the second one is the one that converts.
The rule: wherever it honestly fits, show the person, not just the product. Relatable beats impressive.
6. Earn trust with signals you didn't fake
Running underneath every install decision is one suspicious question: can I actually trust this?
Trust gets built in small signals — ratings, real reviews, download counts, an award, a press mention, a recognizable logo. These are usually treated as an afterthought, a badge slapped on screen five. Pulled forward and shown honestly, they can change how the entire app is perceived.
The word that matters is honestly. If you don't have the numbers yet, do not invent them or stretch a claim. A fake "4.9★ — 2M users" on a two-week-old app reads as exactly what it is, and the one thing worse than no trust signal is a transparently fake one. Credibility and honesty are themselves a trust signal — arguably the strongest one you own early.
The rule: show the real proof you have, prominently. Show no proof you don't. Never the middle option.
7. Fewer words, and make the ones left bigger
Founders try to cram the entire pitch into one headline. The best headlines go the other way: the shortest ones win.
Short copy is easier to read, easier to remember, easier to scan at a swipe — and the real payoff is mechanical. Shorter copy lets you make the words bigger. On a phone-sized tile in a scrolling list, a three-word headline at huge size beats a clever two-line sentence squeezed into eight-point type, and it isn't close. Size is attention.
And don't try to sound smart. Use the exact words your users use. "Stop losing your notes" beats "Unified knowledge persistence" in every test a real human has ever run.
Top comments (3)
Honestly, take the clash of clans approach. You are marketing a solution to a fabricated need, your marketing material is meant to turn an optional into a need. You use gems to speed up, but to progress fast, you need to raid alot, so you need gems, else you're struggling to defend and attack the whole time. So if you're marketing eg. a health and fitness app, your app needs to be the holy grail. You tell them 'this is why you arent losing weight, but it's alright, here's the solution'. That 'realization' is what marketing material is all about, create a need and market a solution.
You post touched on many valid point but I believe the most valid is the shortest, "the shortest ones win". Can be on any number of social posts but that has always been true. Good read. Keep moving forward.
Great work