Automate app capture, then review the screenshot design

Give each stage a clear input and output

Automation is most useful when a release changes the app screen but not the story you want to tell. Stable fixtures, route names and capture filenames make those replacements predictable. They also make it easier to detect a missing screen instead of silently reusing last release's image.

Automate the app state before the screenshot command

For iOS, fastlane snapshot uses an Xcode UI-test target to drive the app and capture named states. Its setup involves a shared test scheme and capture calls in the test, not simply pointing a service at your store URL. Adopt it within your existing app build environment and pin the tooling you validate.

For Android, adb can capture a device screen, but the capture command does not navigate to the correct state or wait for your data. Your test harness must do that. For Flutter, the CLI provides screenshot capture; for React Native, use the project's native device workflow. In every case, validate the output rather than treating an exit code as visual approval.

Use a manifest to prevent stale artwork

Keep a small release manifest in your app repository. Record the app version, source revision, platform, locale, demo fixture, expected filenames and reviewer. A hash of each original image can show whether the asset changed. Do not put passwords, user data or production session tokens in this file.

The downloadable manifest is a starting document, not a connected integration. Fill its blank fields, attach the actual export and record approval only after inspecting it. A missing or unchanged capture should trigger a review, not an automatic claim that the release is ready.

screenshots/
  release-1.4/
    ios/en-US/01-overview.png
    android/en-US/01-overview.png
    release-manifest.md
    approved-exports/

Keep the Skir handoff explicit

1. Open the intended project and verify its platform and board dimensions.
2. Replace each sample or older app image with the matching approved capture. Keep the screenshot as a single image asset.
3. Review all headlines against the new build. A feature rename can make unchanged marketing copy inaccurate.
4. Save, reload and inspect the project. Export the available boards and validate the downloaded files.
5. Move only the approved ZIP into the delivery folder and record its filename in the manifest. Upload through your authorized store workflow.

When to invest in more automation

Track how often you repeat captures, how many locales need review and where mistakes occur. Automating a stable capture sequence can be worthwhile before automating design decisions. If your release pipeline requires a supported generation API with credentials, versioning and service guarantees, evaluate a product that explicitly documents that capability; Skir's current manual workflow is not that interface.