What a good store screenshot actually does

A store screenshot is read, not viewed. Someone scrolling a listing gives the first image about a second, and in that second they are answering one question: is this for me? A pixel-perfect capture of your settings screen does not answer it.

The first frame carries the whole pitch

Treat frame one as a headline with a picture attached, not a picture with a caption attached. The rules that follow are boring and they work:

• One idea per frame. If it needs a comma, it needs two frames.
• Six words or fewer above the device, in a size that survives a thumbnail.
• Show the screen the promise happens on, not the screen you are proudest of.
• Order the set as a story: what it does, how it feels, why it is trustworthy.

Legibility beats fidelity

The most common mistake is shrinking a real screen until it is technically present and practically invisible. Crop in. Show a third of the interface at a size someone can read, rather than all of it at a size nobody can.

The same goes for contrast. A screenshot set is looked at on a phone, outdoors, next to five competitors. Subtle is a desktop luxury.

Make it rebuildable

Whatever you produce, produce it in a form you can regenerate. Store listings change; you will redo this set. Keep the text as text and the layout as data, so that next quarter's version is an edit rather than an excavation:

project
  screens/     the raw captures
  layouts/     frame, crop, safe area
  copy/        one file per locale

That is the shape MockSnaps builds around, and it is worth adopting even if you never use it.