Build your own Calendly.

# Build an original app inspired by Calendly

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original appointment scheduling app called Openhour, inspired by Calendly. It is for a solo professional sharing bookable meeting times. The main journey is defining availability, sharing an event page, and allowing an invitee to reserve a conflict-free time.

## Design
Use a crisp, friendly interface with a host dashboard and a separate public booking flow. Put event details beside a date picker and available slots on desktop; use a step-by-step layout on mobile. Make the active timezone visible. Use an original blue-accented brand.

## Features
1. Event types: create a title, description, duration, location or meeting link, booking horizon, notice period, and buffer between meetings. Publish a shareable event slug.

2. Availability: configure weekly hours and date-specific overrides in the host timezone. Derive slots from duration, buffers, existing bookings, and booking limits.

3. Booking: invitees choose a date, their display timezone, a slot, and enter name and email. Show a summary before confirming and a clear confirmation afterward.

4. Manage meetings: hosts see upcoming and past bookings; invitees can cancel or reschedule through scoped, unguessable management tokens.

5. Calendar export: download an .ics event containing the correct start/end instants, description, and location. Keep email and calendar-provider integrations as clearly documented optional extensions.

## Tech stack
Use the existing repository and conventions if there is one. If starting from scratch, use React with TypeScript and a practical, lightweight styling approach. Pick well-maintained libraries only when they materially help. Keep components, domain logic, and data access separate. Explain your chosen stack briefly, then begin implementation.

Follow the persistence requirements in Data & behavior. Personal tools may use IndexedDB. Products with public submission, bookings, permissions, or shared messaging require an authenticated backend with server-side authorization and durable storage. Use infrastructure already available in the environment. Do not put secrets in frontend code. If external infrastructure is unavailable, build a clearly labeled local demo, provide the schema and setup instructions, and state which shared features need configuration. Do not present simulated sharing or authentication as production functionality.

## Data & behavior
Host {id, userId, name, timezone}; EventType {id, hostId, slug, durationMinutes, location, noticeMinutes, bufferMinutes, horizonDays}; AvailabilityRule; DateOverride; Booking {id, eventTypeId, startAtUTC, endAtUTC, inviteeName, inviteeEmail, status, managementTokenHash}. Use a real backend for public booking. Enforce conflict checks and insert reservations atomically; never trust client-only slot calculations.

Acceptance checks and scope:
Test two invitees booking the same slot concurrently, daylight-saving transitions, timezone changes, buffers, notice periods, cancellation and rescheduling, and .ics import. Validate and rate-limit public booking inputs. If infrastructure is unavailable, label the local demo and do not claim its URLs work for other users. Exclude payments, round-robin scheduling, and external calendar sync from the MVP.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.