Appointment Booking

4.5 out of 56 sold

The booking layer on its own, for any business selling time against a constrained resource, a chair, a room, a practitioner, a bay. Your diary, your rules, no commission.

From$699

Open the preview Request a quote

Function: 23
User types: 2
Platform: iOS & Android

React Native
TypeScript
PostgreSQL
Expo

Inside the app

What it does out of the box

23 connected functions on one schema across 2 user types. Everything below is in the template before a line of customisation.

Book
Services with their real duration and price, and slots that exist. A booking form that sends a request somebody answers later is not a booking system.
Bookings
Upcoming and past, with deposits paid and the cancellation rule shown before it matters rather than after.
Day
Every appointment, every gap and anyone who has not confirmed. Readable at a glance mid-shift rather than something to study.
Services
Duration, price, deposit rule and who is qualified to perform each. A diary that lets a 90-minute service into a 30-minute slot will do it every week.
Patterns
No-shows and late cancels per customer over time, so a policy decision is based on a pattern rather than on the last annoying Tuesday.
Reminders
Push and email before the appointment. Most no-shows are forgetting, not defiance, and a reminder is the cheapest fix available.

User types

Two apps, one diary.

One side is booking time and the other is selling it. Deliberately generic: the same mechanics run a dental chair, a salon station and a consulting room, and the vocabulary is set during a fitted build.

User
2 of 5 screens
The customer
Sees genuine availability, books, and can reschedule inside your rules. No account needed to look at a price or a free slot.
Preview as the user
- Browse availability without signing up
- Book against a real diary, not a request form
- Deposits where you require them
- Reschedule and cancel inside your window
- Reminders that reduce no-shows
Owner
3 of 5 screens
Whoever runs it
A dentist, a salon owner, a garage, a consultant. Sets services, durations, availability and rules, and sees the day and the no-show pattern.
Preview as the owner
- Services with real durations, not 30-minute blocks
- Availability by person and by resource
- Deposit and cancellation rules that hold
- The day at a glance, workable mid-shift
- No-show and late-cancel patterns per customer

The limits

What this is not.

The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.

It carries no audience
It replaces the booking layer, not the marketing. A marketplace takes commission partly because it brings customers.
We do not process payments
Deposits and payments run through your own provider account, which is what keeps the commission at zero.
It is deliberately generic
Anything trade-specific, colour formulas, clinical notes, vehicle records, is a fitted-build addition. If you need those on day one, one of the trade-specific templates is the better start.
Store approval is never guaranteed
We build to the published guidelines, submit from your developer accounts and fix what comes back. Nobody can promise an approval date.

Questions

Questions, answered plainly.

If yours is not here, ask it on the call rather than guessing from a pricing page.

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultant All questions

Which businesses is this for?

Any that sells time against a limited resource: dental practices, salons, garages, clinics, consultants, studios. The mechanics are the same; the vocabulary is configured in a fitted build.

How is it different from the trade-specific templates?

This is the booking layer alone. Salon and Beauty adds stylist skills and treatment history; Doctor Consultation adds clinical records and an access log. Start here if booking is genuinely the whole problem.

Does it take deposits?

It records what is owed and required, and enforces the rule. Collection runs through your own payment provider rather than through us.

Can customers see prices without signing up?

Yes, and they should. Forcing a signup before someone can see a price is the fastest way to lose the booking.

Do I get the source code?

Yes. Both apps, API, schema, migrations and deployment configuration transfer on delivery. No licence key and nothing that calls home.