capturing-preview-screenshots-in-ci

What problem does it solve?

This skill solves the problem of turning local Jetpack Compose @Preview work into a shared, browsable visual artifact that teams can review and validate consistently from CI.

Core Features & Use Cases

• Device-rendered preview capture: Renders every @Preview on a real Android device/emulator using Compose HotSwan so screenshots reflect device fonts, real image loading, GPU rendering, and system chrome.
• Automated “capture all” workflow: Uses the HotSwan Gradle task captureAllPreviews to scan source files, launch previews via HotSwanPreviewActivity, and collect PNGs into a catalog.
• Deterministic CI catalogs: Supports demo mode and per-preview render-delay tuning with @PreviewScreenshot to avoid half-painted captures for animated or data-loading previews.
• Team-friendly HTML delivery: Produces an index.html catalog suitable for deployment (e.g., GitHub Pages) so designers/QA/PMs can browse changes per commit.
• Tool comparison guidance: Helps decide when to use HotSwan device screenshots versus host-JVM tools like Paparazzi and Roborazzi (for pixel-diff vs device fidelity).

Quick Start

Ask your AI coding agent to configure HotSwan for your app module and run captureAllPreviews in CI so every @Preview becomes a PNG and a deployable HTML catalog on each commit.