gensht

Original field notes

Five Source Screenshot Mistakes Found in Real Generations

Common source screenshot and generated-set mistakes observed across 68 tracked Genshot candidates, with a transparent method and practical prevention checks.

8 min readVerified August 27, 2026

Short answer

The recurring failures were not only visual: repeated copy, wrong source order, invented helper text, unwanted device-like shells, and palette drift all survived otherwise attractive compositions. Review the complete set, not isolated images.

Method and limits

We reviewed 68 tracked MyPR Google Play candidates stored in the Genshot repository, including persisted manifests where available. The collection contains production Generations and local explorations. Findings are qualitative failure patterns, not prevalence statistics.

The app and target were Android. These observations help review a generation workflow, but they do not replace Apple’s App Store rules or prove iOS listing performance.

Five failures that looked polished in isolation

Observed generation failure patterns
FailureObserved evidencePrevention
Repeated copySeveral four-image runs reused the first copy group.Bind one caption to one source image and reject duplicates.
Source-order driftOne bold direction changed the intended screen sequence.Store and inspect ordered source identifiers.
Invented labelsExploratory Hebrew images added English helper text.Forbid new visible copy and OCR every candidate.
Device-like shellsRounded hardware-like framing survived a no-frame instruction.Name both device frames and device-like shells in constraints.
Palette driftOne candidate introduced green outside the requested palette.Compare sampled colors with the approved Brand Profile.

Inspect source screenshots before generation

  • Remove notifications, debug overlays, loading states, and clipped system sheets.
  • Replace names, messages, balances, and account details with fictional information.
  • Capture the same theme, locale, and app version across the intended sequence.
  • Prefer the screen that proves the caption rather than the screen with the most UI.
  • Keep original source identifiers so every generated image can be traced back.

Review the set at three levels

  1. Step 1

    Image

    Check UI fidelity, copy, crop, privacy, and unwanted elements.

  2. Step 2

    Sequence

    Check source order, repeated claims, pacing, and visual rhythm.

  3. Step 3

    File

    Check dimensions, format, transparency, locale, and display target.

  4. Step 4

    Publish

    Verify the reviewed set and Apple processing state.

Sources and verification

Product capabilities and changing requirements were checked against these primary pages. External pages can change after the verified date above.

Related App Store screenshot resources

Real experimentOne App, Three Store Screenshot Directions: A Real Genshot ExperimentCopywritingApp Store Screenshot Captions: Examples and Editing ChecklistRelease checklistApp Store Screenshot Release Checklist

Run the release checklist

Catch source, copy, ordering, and privacy problems before the upload step.

Run the release checklist