A calendar that crosses practitioner and room
Each practitioner has hours and each room has occupancy. A procedure needing both only opens when both are free.
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.
A patient record with history
Details, contact, insurance, attachments and what was done at each visit, by whom and when. The history is in your database, exportable.
Insurance and private in one place
A procedure with a private price and a price per insurer, so the monthly report separates reimbursement from cash.
Confirmation, reminder and recall
Confirmation on booking, a reminder the day before, and a recall notice after whatever interval you set, by email or push.
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 an app for a clinic with four practitioners and two procedure rooms. Each practitioner has working hours per weekday and their own list of procedures with durations; procedures that use a room can only be booked when the practitioner and the room are free at the same time; patients have a record with contact details, insurance, attachments and a visit history; each procedure has a private price and a price per insurer; reception books, reschedules and cancels, a practitioner sees only their own day and marks a patient as seen or a no-show; an email confirmation goes out on booking and a reminder the day before; and the owner sees revenue per practitioner, per insurer and per month, plus 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.