Any screen, panel, or card that would otherwise be blank—e.g., a dashboard before data loads, an integration page with no sources, or a folder with zero files. A well-designed empty state teaches, nudges action, or delights, instead of wasting space.
Yes. Drag blocks—text, images, buttons, or advanced components like cards and accordions—directly into your product. Publish changes instantly without a deploy. Our guide on creating no-code empty states.
Absolutely. Use segmentation rules (role, plan tier, language, NPS, custom traits) so each audience sees the copy or CTA that’s most relevant.
Tie any block—e.g., “Connect an integration” card—to a product event such as integration.connected. When that event fires, Candu hides or replaces the prompt automatically.
Yes. All blocks are fully responsive. Columns collapse into a single stack and typography scales, so you never need a separate mobile guide.
Duplicate the variation, assign a traffic split (e.g., 50 / 50), and Candu tracks click-through, conversion, or custom events for each version—no external flag tool required. Learn about experimentation in Candu.
The Candu runtime is ~45 KB gzipped, loads asynchronously from a global CDN, and has no measurable impact on Core Web Vitals.