Screenshot System

Make screenshots boring to refresh.

The best screenshot pipeline is deterministic, privacy-safe, and release-repeatable.

Deterministic state

Use stable demo fixtures so screenshots stay consistent across releases.

Privacy-safe media

Never capture local personal data or production user records for marketing assets.

Versioned slugs

Asset slugs should map cleanly to page sections and remain stable over time.

Today Command Center screenshot asset

Today Command Center

/product/screenshots/today-command-center.svg

Goals, Habits, and Life Areas screenshot asset

Goals, Habits, and Life Areas

/product/screenshots/goals-habits-life-areas.svg

Memory and Reflection screenshot asset

Memory and Reflection

/product/screenshots/memory-reflection.svg

Privacy and Secure Box screenshot asset

Privacy and Secure Box

/product/screenshots/privacy-secure-box.svg

1. Prepare demo state

Use deterministic sample data and one canonical simulator profile.

2. Run capture flows

Use Maestro navigation scripts and `xcrun simctl io booted screenshot` for repeatable captures.

3. Publish assets

Export optimized images into `public/product/screenshots` with stable, documented slugs.