Mobile app / PROJECT CASE STUDY

Appointment Booking App Case Study: Haven

An appointment product connecting practitioner availability with a detailed booking review and the customer’s mobile appointment journey.

Wellness appointment app overview
Industry
Wellness
Focus
Appointments
Experience
Mobile app

Project brief and workflow decisions

Scheduling involves the selected service, practitioner, location and time. The supplied desktop screen brings practitioner columns and appointment details into the same view, helping a staff member inspect the selection before confirming the booking.

01

Availability in a shared view

Practitioners appear in separate columns against common appointment times. Date and location controls establish the scope of the availability grid. Available and Booked labels communicate slot state without requiring a separate lookup.

02

Selection with a detail panel

The selected slot is highlighted while a side panel presents the relevant appointment information. Time, duration, clinic and appointment type stay close to the confirmation action so the reviewer can assess the complete booking context.

03

Customer and staff journeys

The project combines this scheduling view with mobile appointment screens. That pairing connects the customer’s service selection with the staff-side view of availability and the final booking details.

An appointment is a combination of service, resource, time and location. Keep those details visible together at the confirmation step rather than scattering them across disconnected screens.

Explore the relevant development service for this project workflow to discuss your requirements.

Enterprise reference architecture

A proposed engineering design for this workflow. The enterprise scenario and stack below are illustrative architecture choices; they are separate from the confirmed project screens.

The enterprise scenario

A multi-location appointment business coordinates practitioner calendars, service durations, rooms and staff-assisted rescheduling.

Architecture objective: Protect reservation integrity under concurrent requests while keeping customer requests, temporary holds and confirmed appointments understandable.

Proposed technology stack and rationale

Client and operations tools

Flutter for mobile; React and TypeScript for scheduling

Provide distinct client booking and staff availability views over the same scheduling rules.

Scheduling domain

ASP.NET Core with explicit appointment commands

Centralise service duration, resource eligibility and allowed cancellation transitions.

Reservation store

PostgreSQL with transactional overlap constraints

Enforce the selected practitioner and time-window rules at the database boundary, not only in the calendar UI.

Workflow coordination

Hangfire background jobs and idempotent provider activities

Coordinate reminders, wait-list offers and external-calendar updates without assuming remote calls execute only once.

Identity and operations

OIDC, scoped staff roles and Application Insights

Separate client, practitioner and scheduler permissions and trace each booking decision.

Technical challenges and design approach

1

Concurrent slot selection

Two customers can select the same visible slot. Use a transactional constraint for the final reservation and return a clear alternative when the conflict is detected.

2

Rescheduling across resources

Changing the practitioner or duration can invalidate the selected time. Validate the full proposed appointment before releasing or replacing the existing reservation.

3

Location-specific time

The display zone and the resource’s scheduling zone may differ. Preserve both the appointment instant and the relevant local scheduling context.

How the proposed workflow fits together

  1. The client selects a service and location before requesting available resources.
  2. A hold or reservation command validates the complete resource and time combination.
  3. The transaction either commits the appointment or returns an explicit availability conflict.
  4. Staff review and rescheduling use versioned commands against the authoritative record.
  5. Reminder and calendar workers reconcile external outcomes without changing confirmation state implicitly.

Acceptance and failure-path checks

  • Two concurrent confirmations cannot create overlapping accepted reservations under the agreed rule.
  • Repeated rescheduling requests retain a stable outcome and history.
  • Reminder or calendar failures are visible without losing the appointment.
  • Authorisation tests cover clients requesting records that belong to another person.

The tradeoff

Use strong consistency for reservation acceptance and eventual consistency for secondary calendar projections. A cached calendar is a useful view, not the reservation authority.

Architecture references: ASP.NET Core documentation and PostgreSQL constraints. These describe engineering patterns, rather than certify this project’s implementation.

What the project brings together

  • Practitioner availability grid
  • Date and clinic selection
  • Appointment review before confirmation

Let’s create what’s next.

Bring your idea. We’ll help you find a clear way forward.

Discuss your project