Capture and review localized app-store screenshot sets

Why use this

1. A developer preparing store images may need several languages and device layouts from the same app. Small translation changes can cause clipping, while a screenshot can show a different state from the caption beside it.

2. This job could create a consistent review package that connects each locale, screen state and claim. Reviewing those dimensions together helps the owner catch mismatches before deciding which assets are suitable for publication.

Why an agent / simpler alternative

Useful judgment

Coordinate locale text, capture state and visual layout while surfacing translation ambiguity and unsupported promotional claims.

Simpler alternative

Use a fixed screenshot template when only a few already-approved captions change.

Unsuitable when

The task requires unsupported rating claims, fabricated product capabilities or publication without review.

Proposed inputs

1. Name

   Capture specification

   Owner

   App owner

   Minimum scope

   Approved build, device targets and screen states

   Quality check

   Define synthetic display data and required states

2. Name

   Caption/locale pack

   Owner

   Product or marketing owner

   Minimum scope

   Approved wording, translations and claim evidence

   Quality check

   Check locale codes, terminology and evidence dates

Access and setup — proposed or unknown

Proposed minimum

1. Begin with a private capture manifest and caption/layout review; no simulator execution or store access.

Compatibility unknowns

1. Current build tooling, simulator support, rendering scripts and runtime compatibility are unknown.

External actions requiring approval

1. Running builds, paid image generation, uploading assets or publishing store listings requires authorization.

Expected deliverable and review checks

Proposed artifact

Localized screenshot manifest with caption mappings, fit exceptions and approval checklist.

Critical checks

1. Match each caption to the depicted feature; inspect text overflow, locale consistency, dimensions and claim support.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   Translated text fits but changes the promise

   Why it matters

   Visual QA misses a substantive claim change

   Proposed response

   Request language review against the approved meaning.

2. Signal

   A capture retains another locale's data

   Why it matters

   The set appears partly localized

   Proposed response

   Recheck state initialization and flag the affected screen.

Effort and cost — unknown

Setup work

1. Define device/locale matrix and approved claims.

Ongoing review

1. Review text and images together before each release.

Unknowns

1. Build reliability, translation review, rendering effort and generation costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent two locales, two screen states and one long translated caption plus an unsupported rating badge; review the asset manifest only.

Acceptance checks

1. Flag overflow risk and unsupported claim; verify locale/state pairing; produce no publication action.

Stop conditions

1. Stop if a claim lacks evidence or a capture would expose real user information.

Limits

1. Correct dimensions and fluent captions do not establish store acceptance, truthful claims or marketing performance.