your store listing does more selling than your app does, because most people decide from the first three screenshots without ever opening it. Capture screenshots from a simulator or emulator with a clean status bar and realistic data, give each one a short benefit caption, put your strongest feature first, and use every character of your title, subtitle and keyword fields without repeating words. Keep everything accurate to the real app, or review will send it back.
You spent weeks building the app with AI and an afternoon on the listing. That's the usual ratio, and it's backwards for the first month after launch: until you have reviews and word of mouth, the listing is almost the only thing deciding whether people download.
This guide is the developer's version of App Store Optimization (ASO): concrete specs, scripts to capture screenshots consistently, and the metadata rules that actually affect ranking.
Disclosure: this guide is from LetsDeployIt, where we prepare store listings as part of publishing AI-built apps.
How people actually see your listing
On both stores, people meet your app in search results first. There they see your icon, name, rating and, on the App Store, usually the first three portrait screenshots or your preview video. Most never scroll further.
That means:
- Screenshot 1 must explain the app on its own.
- Screenshots 1 to 3 do most of the work. The rest are for people already interested.
- Your title is doing double duty: it's what people read and one of the strongest search signals.
The specs you need (and where to confirm them)
Store requirements change with new devices, so treat these as a starting point and check what App Store Connect and Play Console show for your app.
App Store
- Up to 10 screenshots per device size and language.
- iPhone screenshots for the largest display size App Store Connect asks for; smaller sizes can be scaled from them.
- iPad screenshots too, if your app runs on iPad.
- Optional app previews (short videos), up to 3 per device size.
Google Play
- 2 to 8 phone screenshots (and tablet screenshots if you target tablets).
- A feature graphic, 1024×500, required.
- An icon, 512×512.
- An optional promo video via YouTube.
Capturing clean screenshots from the command line
Hand-made screenshots from your own phone show your real battery level, notifications and carrier. Capture from a simulator or emulator instead, with a fixed status bar and the same data every time.
iOS Simulator
# Boot the device you want (pick the size App Store Connect requires)
xcrun simctl boot "iPhone 16 Pro Max"
open -a Simulator
# Clean status bar: 9:41, full battery, full signal
xcrun simctl status_bar booted override \
--time "9:41" --batteryState charged --batteryLevel 100 \
--cellularMode active --cellularBars 4 --wifiBars 3
# Capture
xcrun simctl io booted screenshot ./screens/ios/01-home.png
# Check the size before uploading
sips -g pixelWidth -g pixelHeight ./screens/ios/01-home.png
Android Emulator
# Enable demo mode for a clean status bar
adb shell settings put global sysui_demo_allowed 1
adb shell am broadcast -a com.android.systemui.demo -e command enter
adb shell am broadcast -a com.android.systemui.demo -e command clock -e hhmm 0941
adb shell am broadcast -a com.android.systemui.demo -e command battery -e level 100 -e plugged false
adb shell am broadcast -a com.android.systemui.demo -e command notifications -e visible false
# Capture
adb exec-out screencap -p > ./screens/android/01-home.png
# Exit demo mode afterwards
adb shell am broadcast -a com.android.systemui.demo -e command exit
Make the data look real
Empty states and "Test User 1" make an app look unfinished, and placeholder content is itself a common reason for rejection. Create a dedicated demo account with realistic names, photos and numbers, and capture every screenshot from it. Bonus: the same account doubles as the demo login App Review asks for.
If you update screenshots often, automate the flow with an end-to-end tool like Maestro or fastlane's snapshot, so every release can regenerate them in the same states.
Designing screenshots that convert
Raw screenshots rarely convert as well as designed ones: a caption, a background and the screenshot inside a device frame or on its own. You can build them in Figma with a template, or with a screenshot generator.
One idea per screenshot
Each screenshot should show one benefit with one short caption. A good sequence for a typical app:
- The core promise: the main screen with your main benefit. "Plan a week of dinners in 2 minutes."
- How it works: the key action. "Pick what you like, we build the list."
- The payoff: the result. "Your shopping list, sorted by aisle."
- A differentiator: what competitors don't do.
- Trust or detail: sync, privacy, widgets, dark mode.
Caption rules
- Benefits, not features. "Never forget a bill" beats "Push notifications".
- Short. Aim for a few words people can read at thumbnail size in search results.
- Big text. If you can't read it at the size of a search result on a phone, it's too small.
- Consistent. Same font, color, position and frame across all screenshots.
Stay accurate
App Review checks that screenshots show the app in use. Captions, backgrounds and frames are fine; mockups of features that don't exist, fake reviews or misleading claims are not. Don't show other platforms' devices or names in your App Store screenshots either.
Metadata: the fields that affect search
App Store
- App name (30 characters): your brand plus your main keyword, such as "Mealy: Weekly Meal Planner". The strongest search field.
- Subtitle (30 characters): a second keyword phrase that reads like a benefit.
- Keyword field (100 characters): comma-separated, no spaces after commas, no words already in the name or subtitle (they're indexed already), no competitor brand names.
- Promotional text (170 characters): shown above the description and editable without a new review, which makes it ideal for launches and updates.
- Description: written for people, not search. Lead with the benefit and keep the first lines strong; most readers only see those before "more".
Google Play
- Title (30 characters): brand plus main keyword, as on iOS.
- Short description (80 characters): shown prominently on the listing; make it a clear benefit.
- Full description (4,000 characters): Google uses this text for search, so include your main keywords naturally a few times. Don't stuff them; it reads badly and can violate Play's metadata policy.
Finding keywords
Start with how real users describe the problem, not how you describe the product. Your support emails, reviews of competing apps and the store's own search suggestions (type a word into the store search and note the autocomplete) are free keyword research. Pick specific phrases you can realistically rank for over broad ones like "productivity".
After launch: test and iterate
- Test your screenshots. Apple's product page optimization and Google's store listing experiments let you A/B test icons, screenshots and descriptions with real traffic.
- Localize. Translating the listing (even before the app) can open new markets cheaply.
- Update with every meaningful release. New feature, new screenshot. Outdated screenshots hurt conversion and accuracy.
- Watch conversion, not just downloads. Both consoles show how many listing visitors install. That's the number your screenshots control.
Listing mistakes that cause rejections or hurt installs
- Screenshots with placeholder content or "lorem ipsum".
- Screenshots of features that aren't in the submitted build.
- Competitor names or trademarks in your keywords or title.
- Keywords repeated across the name, subtitle and keyword field (wasted characters).
- A first screenshot that's a logo or splash screen instead of the app.
- Tiny captions that are unreadable in search results.
- No iPad screenshots when the app runs on iPad.
A pre-submission checklist
- Screenshots captured with a clean status bar and a realistic demo account.
- First three screenshots explain the app on their own.
- One benefit and one short caption per screenshot, consistent design.
- Required sizes for every device the app supports.
- Google Play feature graphic ready.
- Name and subtitle include your main keywords; keyword field has no repeats.
- Description leads with the benefit; Play description includes keywords naturally.
- Everything accurate to the build you're submitting.
The rest of what the stores require, from privacy forms to account deletion, is in our launch checklist.
FAQ
Do I need a designer for store screenshots? No. A template and the five-screenshot structure above get most apps a professional result. Spend the effort on screenshot 1.
Should I use device frames? It's a style choice. Frames look polished; frameless, full-bleed screenshots show more of the app. Pick one and stay consistent.
Can I change screenshots after launch? Yes. On the App Store, new screenshots go live with a new version or through product page optimization tests; on Google Play, you can update the listing anytime.
Does the iOS description affect search ranking? Apple relies mainly on the name, subtitle and keyword field for search. Write the description for people.
Conclusion
Your listing is your app's landing page, and for most people it's the only part of your app they'll ever see. Capture clean, realistic screenshots with scripts you can rerun, lead with your strongest benefit, use every metadata character well and keep it all accurate to the build.
If you'd rather hand off the listing along with the rest of the launch, LetsDeployIt prepares screenshots, metadata and store requirements as part of taking AI-built apps through both stores. See plans.
Drop a link to your app's listing in the comments, and we'll suggest one improvement to your first screenshot.
Top comments (1)
Two things worth adding to the Android half:
adb exec-out screencap -p > file.pngpipes raw bytes through the shell, so on Windows (PowerShell or Git Bash) the PNG comes out corrupted -adb shell screencap -p /sdcard/01.pngfollowed byadb pullis the safe version there. And any screen with FLAG_SECURE set captures as solid black, which is easy to miss until you open the file, so it is worth stripping that flag in the debug build you shoot from.