Skip to main content
Screenshots sell the app once someone lands on the product page. Appeeky Spec keeps a copy of your live App Store screenshots next to the listing, so you and your coding agent can see what is live, and it checks the sizes of a new set before you upload it.

​
Download the live set

Screenshots come from the same App Store version that pull reads: the version you are preparing when there is one, otherwise the live version. Store access works the same as for the listing; see Connect the stores. screenshots pull covers the App Store only.

​
Where the files live

One folder per locale, one folder per display type inside it, and the screenshots numbered in store order. Pulled files are saved as PNG. Pulling again overwrites files with the same number. It does not delete extra files you added. Commit the folder if you want the history of your screenshots in git, and pull requests that show old and new sets side by side.

​
Check sizes and counts

It reads every .png, .jpg and .jpeg file under appeeky/screenshots/app-store/ and checks:
  • Count: no more than 10 screenshots per display type.
  • Size: the pixel size matches one the display type accepts. Landscape is fine: the same sizes turned sideways.
A folder with another name gets the count check only. Every problem is an error, and the command exits 1 when it finds one. With no appeeky/screenshots/ folder, there is nothing to check. check runs these screenshot checks too, together with the listing rules, so one command covers both:

​
Prepare a new set

  1. Run screenshots pull to start from what is live.
  2. Put the new images in the same folders, named in the order you want (01.png, 02.png, …).
  3. Run screenshots check and fix any size or count errors.
  4. Open a pull request, so the team sees the new set before it ships.

​
How screenshots relate to push

push sends listing text only. It does not upload screenshots, so screenshot errors do not stop a listing push; push prints them as a warning. The pull request report from the GitHub Action lists screenshot errors next to the listing check and fails the check when there are any, so a bad set is caught before the merge. Upload new screenshots with the App Store Connect CLI or in App Store Connect.

​
Measure a new set

A listing push is measured for you. A new screenshot set is not a listing push, so track it as an experiment with one metric, usually store conversion:
conversion (downloads ÷ product page views) is measured for you with APPEEKY_API_KEY: experiment add records the baseline, and verify closes the experiment when it is due. Upload the new set the day you start the experiment, so the before and after windows line up. See Experiments. Next: Experiments · Write and check your listing · Troubleshooting