Internal tools and SaaS surfaces where the calendar is part of a bigger workflow.
Developer use case
A React scheduler component for products that keep changing.
If the user story is 'move work around, resize appointments, switch planning views, and persist those changes into our app', you are shopping for a scheduler component. That is the product shape CalendarCN is built for.
Teams that need optimistic move and resize behavior wired into product state.
React and Next.js apps that care about owning the implementation instead of embedding a widget.
Builder route
What you get out of the box
CalendarCN is a React scheduler component for product teams that need direct editing, recurring events, resource lanes, and a controlled state model.
Wire `date`, `view`, and `events` into your own state while the calendar handles visible range and interaction UI.
Use one event contract across month, week, day, and agenda so teams can change planning mode without changing data shape.
Start with the scheduler wrapper for evaluation, then move to `CalendarRoot` and `CalendarToolbar` when you need fine control.
Evaluation
What makes this a scheduler, not just a calendar
Use these criteria to decide whether this route actually matches your product and evaluation context.
- Use this when you need a scheduling surface inside an existing product, not a standalone consumer calendar.
- The controlled API is a strength if your app already owns validation, persistence, and business rules.
- If you need a massive plugin ecosystem before shipping anything, broader incumbents may fit better.
Next step
Go deeper without losing the install path
Move from search intent into evaluation fast: docs, patterns, and API pages that match this use case.