Use cases

Take bookings

Availability per professional, confirmation, reminders and check-in — the classic agenda, without the spreadsheet.

Booking apps are where a spreadsheet breaks first: two people take the same slot, the reminder is forgotten, and nobody knows who confirmed. Here the availability is a data model, the confirmation is an automation, and the reminder goes out by email or push without anyone remembering to send it.

People reach this page looking for

  • how to make an appointment booking app
  • online scheduling app for a salon or clinic
  • booking system with reminders and payment
  • replace a scheduling spreadsheet with an app

What gets built

Four things you could have working this week

Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.

01

Availability per professional or resource

Working hours, breaks, durations and blackout dates as data — so two people can never take the same slot.

02

Booking, confirmation and reminder

The customer books, gets a confirmation, and gets reminded by email or push without anyone remembering to send it.

03

Payment or deposit at the time of booking

Charge in full, take a deposit, or let people pay on arrival. No-shows stop being free.

04

The day's agenda for whoever works there

A screen per professional showing only their own bookings, plus check-in, rescheduling and a history that survives the month.

Included

The parts nobody wants to build twice

Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.

A real database, not a form dump

Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.

Login for your own users

Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.

Payments that land in your account

Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.

Web, installable, and in the stores

One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.

Found in search, and by the models

Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.

React code you can take with you

Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.

How it works

From a paragraph to a published app

Three steps, and the second one is the one people do not believe until they watch it.

Describe it in plain language

Say what the app does and what it has to remember. No diagram, no schema, no naming a single framework.

Watch it get built

Screens, data models, login and payments appear while you read. Anything you do not like, you say so and it changes.

Publish, then keep changing it

Live on your domain in seconds, with version history behind you. Tuesday's conversation is Tuesday's release.

Start here

A prompt you can paste right now

This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.

Build a booking app for a barber shop with four barbers. Each barber has their own working hours and services with different durations; a customer picks the service, the barber and an available slot, pays a deposit by card or Pix, and gets a confirmation and a reminder the day before. Each barber sees only their own agenda and can mark a customer as arrived or a no-show; the owner sees everyone, plus revenue and no-show rate per month.

Ready to start from

Templates in this category

A template is a working app with data already in it. Open one, make it yours, publish it under your own account.

Tessera

Booking

Class booking for a studio with a hard capacity: credits, a waiting list that moves itself, and a door roster that records who came.

15 screens

Serenity

Booking

A salon diary where every appointment reserves the turnaround, so a gap on the board is time that can really be sold — and an assistant that says which gaps are worth a call.

16 screens

Questions

Frequently asked questions

Yes, because availability is a model in the database and not a rendered calendar. The slot is taken when the record is written, so the second person's booking fails at the database, which is the only place that can decide it consistently.

Describe it. See it running. Publish it to the store.

Free to start, no credit card. You only pay when you want to publish under your own brand, and you take the code with you if you ever want to.

Build this app freeUse cases