The first screenshot has one job
The first image should communicate the strongest user benefit quickly. Use a short headline, show real product UI, and avoid clutter that competes with the message.
Lead with outcome
Use copy that names the benefit instead of describing internal features only your team understands.
Make the interface readable
Crop and frame the app UI so the important screen content is visible at store thumbnail sizes.
Keep style consistent
Use shared type, color, background, and device rules so the screenshot set feels like one product story.
Build a system, not one-off images
The more often your app changes, the more valuable reusable screenshot pages become. A repeatable system makes release updates and localization less painful.