priyanshuraj20/dentwise

1. Overall shape

- Dentwise is a Next.js App Router SaaS with a mixed server/client architecture.

- The app is split into user-facing experiences: landing, appointment booking, dashboard, admin management, Pro upsell, and an AI voice experience.

2. Route-level domains

- src/app/page.tsx is the marketing landing page.

- src/app/appointments/page.tsx contains the booking flow.

- src/app/dashboard/page.tsx is the authenticated patient dashboard.

- src/app/admin/page.tsx is the staff/admin console.

- src/app/pro/page.tsx handles the paid-plan surface.

- src/app/voice/page.tsx exposes the voice-agent experience.

3. Authentication and access control

- The repo is built around Clerk for sign-in, identity, and subscription-aware access.

- src/proxy.ts is the route boundary for auth/redirect logic.

- src/components/UserSync.tsx and src/lib/actions/users.ts indicate a user-sync step between Clerk identity and the app’s own user record.

4. Booking workflow

- The appointment experience is a multi-step client flow in src/components/appointments/*.

- The booking path is explicitly staged as doctor selection → time/service selection → confirmation.

- Hooks such as src/hooks/use-doctors.ts and src/hooks/use-appointment.ts likely coordinate fetching and state across those steps.

5. Core data model and persistence

- Prisma is the data access layer, with the schema in prisma/schema.prisma.

- src/lib/prisma.ts centralizes database access to a PostgreSQL backend.

- The main persisted entities appear to be users, doctors, and appointments, since those are the server action modules present under src/lib/actions/.

6. Server-side application logic

- Business operations are concentrated in Next.js server actions:

- src/lib/actions/appointments.ts

- src/lib/actions/doctors.ts

- src/lib/actions/users.ts

- This keeps write operations, validation, and database mutations on the server boundary rather than in client components.

7. Email notification pipeline

- src/app/api/send-appointment-email/route.ts is a dedicated API route for sending transactional mail.

- src/lib/resend.ts integrates with Resend.

- src/components/emails/AppointmentConfirmationEmail.tsx defines the email content used for booking confirmations.

- Net effect: booking data flows from the app into email delivery after persistence.

8. Admin and operational console

- The admin area is built from a client shell plus focused management widgets:

- AdminDashboardClient.tsx

- AdminStats.tsx

- DoctorsManagement.tsx

- RecentAppointments.tsx

- This subsystem is for operational visibility and CRUD-like maintenance of doctors and appointments.

9. AI voice agent and paid-plan boundary

- src/app/voice/page.tsx and src/components/voice/VapiWidget.tsx integrate the Vapi voice agent.

- src/components/voice/ProPlanRequired.tsx suggests the voice feature is gated behind subscription level.

- The pro route appears to be the plan-upgrade/billing boundary that unlocks voice capabilities.

10. UI system and client data fetching

- The app uses a shared design system built from shadcn/ui primitives in src/components/ui/.

- Page-specific UI is organized into feature folders like landing, dashboard, appointments, admin, and voice.

- src/components/providers/TanStackProvider.tsx shows TanStack Query is used for client-side caching and fetching where interactive screens need it.

11. Runtime and deployment boundaries

- The project runs as a modern Next.js full-stack app on Vercel.

- External dependencies are environment-driven: Clerk, PostgreSQL, Resend, and Vapi.

- Static assets live in public/, while next.config.ts, prisma/, and the App Router directories define the main operational boundaries.

12. Key end-to-end data flow

- Authenticated user enters the booking flow → selects doctor/time → server action writes to PostgreSQL via Prisma → confirmation email is sent through Resend → appointment becomes visible in dashboard/admin views.

- The voice/pro flow is parallel: authenticated user enters /voice → entitlement is checked via subscription state → Vapi widget provides the AI interaction if allowed.