A calendar per professional, not per salon
Each professional has working hours, days off and their own list of services. The client picks who they want and only sees what that person does.
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.
Services with a real duration
A thirty-minute cut and a three-hour colour do not take the same space. Duration belongs to the service, so the grid of available times adjusts itself.
A deposit taken at booking
Card at the time of booking, with an amount per service. It is the one thing that genuinely moves the no-show rate, and it lands as a line in your takings.
A reminder the day before, and client history
Automatic email or push before the appointment, and a record for each client with what they have had done, with whom and when.
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.
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 barbershop with four barbers. Each barber has working hours per weekday, days off, and their own list of services with duration and price; the client picks a service, a barber and a free slot, pays a deposit by card and gets an email confirmation plus a reminder the day before; availability prevents two bookings in the same slot; each barber signs into their own account and sees only their own day, marking a client as served or a no-show; each client has a record with their appointment history; and the owner sees every calendar, revenue per barber and per month, and the no-show rate.
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.
Questions
Frequently asked questions
Describe it. See it running. Publish it to the store.
Free to start, no credit card. You subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.