Booking for first visits and follow-ups
First visit and follow-up with different durations, in person or online, with confirmation on booking and a reminder the day before.
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 record with intake and measurements
Details, history, goal and the measurements from each visit, such as weight, circumferences and body fat percentage, with progress charted over the months.
A meal plan the client opens
Meals by time of day, foods with quantities and a list of swaps, put together by you and read on the client's phone. A new plan replaces the old one without resending a file.
A food diary with photos
The client logs a meal with a photo and a note, and you open the week's diary before the follow-up.
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 nutrition practice. A calendar with one-hour first visits and forty-minute follow-ups, in person or online, with hours per weekday, an email confirmation on booking and a reminder the day before; a client record with contact details, date of birth, goal, intake history, restrictions and allergies, and measurements logged at each visit with weight, height, circumferences and body fat percentage, shown on a progress chart; a meal plan put together by me with meals by time of day, foods, quantities, notes and swaps for each item, with only the current plan visible to the client; the client signs in, sees their own plan, logs meals in the diary with a photo and sends the week's weight; PDF materials such as recipes and shopping lists; payment for a single visit or a package of visits by card; and an admin dashboard only I can see, with the month's visits, active clients, follow-ups to schedule and revenue.
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.