compose-previews-tooling

To prevent Compose preview theme drift, use a @PreviewWrapper to apply module-wide theming consistently across UI iterations. This ensures previews remain visually accurate without duplicating theme definitions in every individual preview function.

Use @PreviewParameter to generate meaningful state variants for your Compose previews without manual duplication. This injects data-driven states into your UI components, expanding preview coverage efficiently while avoiding preview explosion.

The best way to profile Compose performance is using Macrobenchmark with a strict release-only rule. Relying on Compose previews or Layout Inspector for performance conclusions leads to misleading results, so route profiling effort to the correct pipeline phase.

Choose Paparazzi for Compose screenshot testing when you need a real Android runtime, and choose Roborazzi for CI-friendly rendering. Your selection depends on whether your tests require actual Android runtime execution or fast continuous integration rendering.

Yes, you can use Compose previews and tooling for Compose Multiplatform workflows by applying correct platform and tool selection using CMP applicability rules. This ensures your preview setup and profiling tools function correctly across different platform targets.

Use Compose Compiler Reports and Composition Tracing when you need to interpret layout results and defer state reads. These tools provide decision trees for routing profiling effort correctly, preventing incorrect performance conclusions during UI optimization.