Screenshot delivery needs a repeatable state, device destination and naming scheme. An attractive image at the wrong size or with synthetic content presented as real is not a submission-ready asset.
- 1Select device
- 2Seed safe content
- 3Navigate state
- 4Capture and inspect
Work through the example
Record the runtime and dimensions for each output. Verify current App Store display requirements before exporting release media.
Start with a disposable branch and synthetic data. Write the expected outcome before changing the implementation, then keep the first failing result. This prevents a later repair from quietly redefining the task. The procedure below is grounded in the repository reference; its examples must still be checked against your project and installed toolchain.
Implementation reference
The following focused section is adapted from the maintained project guide. It preserves the source’s examples and limitations.
Artifact Naming
Use stable paths so iterations can be compared:
artifacts/visual/home-pass-01-compact.png
artifacts/visual/home-pass-01-accessibility-xxl.png
artifacts/visual/home-pass-02-compact.png
artifacts/visual/home-pass-02.mov
When visual diffing is added, compare the same route, device, appearance, locale, and content-size category. A screenshot from a different simulator configuration is not a clean comparison.
Acceptance and failure review
| Checkpoint | What to inspect | If it does not match |
|---|---|---|
| Select device | Confirm the input and environment | Preserve the failure and return to this step |
| Seed safe content | Inspect the intermediate artifact | Preserve the failure and return to this step |
| Navigate state | Run the focused check | Preserve the failure and return to this step |
| Capture and inspect | Record the observed result | Preserve the failure and return to this step |
Ask the agent to explain the smallest change that resolves the observed mismatch. Keep unrelated refactors out of the repair. A change that makes a warning disappear is not enough if the behavior or ownership contract has changed. Re-run the same acceptance check so the before and after results are comparable.
Evidence and limits
The baseline screenshot is demonstration evidence, not a complete App Store screenshot set.
This is an educational guide. Its presence in the series does not certify a completed client-specific lab. The series evidence record separates executed checks from exercises and blocked environments.
Inspect the source used in this lesson.
Related reading
- Five checks for an AI-built SwiftUI app
Use persistence, search and accessible states to make “it works” a testable claim.
What to do next
Next: From Figma to SwiftUI with an agent: variables to tokens to code