C
ConvexCompose
Modules
← All modules
B

Booking

In production Operations

Resource scheduling without the conflicts

app.use(booking) Future install shape; not yet published

About

Schedule rooms, equipment, or any resource with conflict detection, recurring bookings, and Google Calendar sync. This runs in a real production deployment today as a plain function module; it is mid-extraction into a contract-conformant Component plus headless hooks, not yet a published installable package.

How it ships

Every ConvexCompose module is the same shape. Take the Component and hooks and bring your own UI, or drop in the optional reference UI.

Layer 1 · MUST
A Convex Component (convex.config.ts + schema + functions), app.use()-installable into your deployment
Layer 2 · MUST
Headless useX() hooks: router-free, style-free, navigation passed in as callbacks
Layer 3 · OPTIONAL
An OPTIONAL React Native + NativeWind reference UI; ignore it and bring your own surface

Highlights

  • Runs in a real production deployment
  • Mid-extraction: not yet a published installable package
  • Per-resource booking calendar
  • Conflict detection
  • Google Calendar sync

Proving ground

A real production deployment exercises these domains; one opinionated consumer, not a requirement.

B
A real production deployment
50+ portals on one Convex deployment

Not a published package yet

No ConvexCompose module is an installable npm package today. What exists is the contract, a real production proving ground running 31 authored Components, and packaging in progress led by convex-diary and convex-audio-analyzer.