Skip to content

Give Pro and Lite their own edit screenshot - #210

Merged
andiwand merged 1 commit into
mainfrom
split-screenshots-per-app
Oct 3, 2026
Merged

andiwand merged 1 commit into
mainfrom
split-screenshots-per-app

Conversation

@andiwand

@andiwand andiwand commented Oct 3, 2026 •

Copy link
Copy Markdown
Member

Lite dims the Pro tools in an edit, but both listings showed the Pro edit. This PR takes the edit a second time as Lite shows it.

  • -ODRScreenshot edit-lite opens the edit with Features.advancedEditing off. It runs in the Pro build, so no ad sdk and no consent form come up.
  • ScreenshotTests takes 04-edit-lite beside 04-edit.
  • frame-screenshots.py frames it with the headline of 04-edit, which is true for both apps.
  • store_screenshots.py needs the Lite picture for a full set. --stage now needs --app, and for Lite it puts 04-edit-lite in place of 04-edit.
  • The upload_listing lane passes its app to --stage.

Checks:

  • I ran the framing and the staging on a fake capture with all 9 languages and both devices. Lite gets its own edit and Pro keeps its own. A missing Lite picture fails the check.
  • In the simulator, edit-lite shows the Pro badge, the dimmed tools, and the highlighter that still works.
  • The format check passes, and the UI tests build. I did not run the full capture, because it takes about a quarter of an hour per device. The next release run does it.

🤖 Generated with Claude Code

Lite dims the Pro tools in an edit, so the shared edit picture showed
Lite tools that it does not have. The run now takes the edit a second
time as Lite shows it, from the same Pro build. Each listing gets its own
picture in the fourth place, under the same headline.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01P9mp6LYWFtb4rYnGaGuiAm
@andiwand
andiwand merged commit 7621ec7 into main Oct 3, 2026
4 checks passed
@andiwand
andiwand deleted the split-screenshots-per-app branch October 3, 2026 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant