Use case
Manage App Store screenshots like files, not form uploads.
Screenshot sets are the most repetitive part of a release: multiple device sizes, multiplied by every locale you support. appBoard turns that grid into something you can actually see and manage from your Mac.
The screenshot problem
App Store Connect uploads screenshots through a per-device, per-locale web widget. For an app with 2 device classes and 20 locales, a full refresh means dozens of drag-and-drop sessions — and the browser gives you no overview of which locale is stale or which size is missing.
Missing or outdated screenshot sets are also a common source of last-minute release friction: you find out when you try to submit, not when the gap appears.
How appBoard handles it
appBoard treats screenshot sets as a first-class part of your app metadata.
- Visual overview of every screenshot set per device size and locale
- Upload and replace sets in bulk from your Mac — no browser widget round-trips
- Spot missing locales or device sizes before you hit submit
- Changes sync through the official App Store Connect API
- Release checklist ties screenshots, metadata, and review info into one pre-submit pass
Fits your existing pipeline
If you generate marketing shots with a screenshot tool — device frames, localized captions, gradient backdrops — appBoard is the delivery end of that pipeline: point it at the exported files and get them into every listing without re-uploading by hand.
Frequently asked questions
Can appBoard upload screenshots for all locales at once?
appBoard manages screenshot sets across all localizations from one view and uploads through the official App Store Connect API, so refreshing many locales no longer means many separate browser sessions.
Does it support all current device sizes?
appBoard works with the screenshot display types App Store Connect exposes via its API, including current iPhone and iPad sizes as Apple updates requirements.
Does appBoard create the screenshots too?
appBoard focuses on managing and delivering screenshots to App Store Connect. Pair it with your capture/design tool of choice — for example ShotSmith, our companion macOS app for designing device-framed App Store screenshots.
What happens if a set is incomplete?
Incomplete sets are visible in the overview rather than surfacing as a submission error later. The release checklist highlights gaps before you submit for review.
Try it on your next release
appBoard is a native macOS app for App Store Connect metadata, screenshots, pricing, and release prep.
