Survey WaitlistPRO

ComingSoon43: Survey Waitlist

A Polaris pre-launch survey card with a square eyebrow, a heading, a single-choice question with selectable radio options, and a working rounded email-capture form that swaps to a success state on submit.

Installation

Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.

Radix flavor

npx shadcn add "https://ui.beste.co/r/comingsoon43?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

npx shadcn add "https://ui.beste.co/r-base/comingsoon43?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the block to components/beste/block/comingsoon43.tsx.

Quick start

The installed file exports comingsoon43Demo alongside the block: the exact props behind the preview above. Spread it to get a working survey card in one line.

import { ComingSoon43, comingsoon43Demo } from "@/components/beste/block/comingsoon43";

export default function Page() {
  return <ComingSoon43 {...comingsoon43Demo} />;
}

Then replace the demo with your own props. Written out, a trimmed setup looks like this:

import { ComingSoon43 } from "@/components/beste/block/comingsoon43";

export default function Page() {
  return (
    <ComingSoon43
      label="Help Us Build"
      labels={{
        placeholder: "Enter your email to send it",
        success: "Thanks. Your answer helps us build the right thing first.",
      }}
      heading="One quick question before we launch."
      question="What would make the biggest difference to your workflow?"
      options={[
        "Getting set up in under five minutes",
        "Bringing my existing data with me",
        "Working smoothly with my team",
      ]}
    />
  );
}

Props

type ComingSoon43Labels = {
  placeholder?: string;
  success?: string;
};

Behavior notes

• The options form a role="radiogroup" where a useState selected index toggles the active styling on each role="radio" button; the choice is local only and is not submitted anywhere.
• The email form owns its own state; handleSubmit calls preventDefault and only flips to the success panel when the trimmed email is non-empty, so there is no external callback to wire.
• On submit the whole question, options, and form are replaced by a bg-muted success panel with a Check badge and labels.success.
• The question and the options grid each render only when their prop is set or non-empty, so the card degrades to just an email capture when you omit them.
• Every string is plain text with no inline markup parsing, so any HTML passed in shows as escaped text.