Separate launches cleanly
Keep new launches, feature updates, seasonal campaigns, and localization passes in separate projects so review and export history stay easier to trace.
Feature
Project-based workspace for every app listing
Organize apps, projects, device sets, and locales in a browser-first workspace designed for repeat release cycles.
A project-based structure keeps screenshot production closer to real release work, where every app, launch, locale, and storefront variation needs its own clean working area.
Reuse without drift
Duplicate existing structures instead of rebuilding them, which helps teams preserve slide order, device selections, and layout consistency from one release to the next.
Stay browser-first
Because the workflow lives in the browser, teams can organize screenshot work without introducing a heavier backend requirement for every project state change.
Why it matters for screenshot production
This feature matters most when screenshot production is a repeated operational task rather than a one-off design deliverable. The more often the listing changes, the more important clean project boundaries become.