A QR-code menu that changes instantly
Every table has its own link. Marking a dish unavailable removes it from the menu that second, with nothing to reprint.
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.
Ordering at the table, with the table attached
The customer orders from their phone, the order lands on a kitchen screen already carrying the table number, and the waiter tracks what is out and what is not.
Reservations with confirmation and reminder
Tables by time and size, confirmation by email and a reminder the day before, which is what brings down no-shows.
Loyalty and repeat visits
Registered customers with a spending history, a stamp per visit, and a coupon for anyone who has not come back in thirty days. It is the customer list the marketplace never handed over.
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 restaurant. A menu with categories, dishes with photo, price, description, a sold-out flag and add-ons; each table has a QR code that opens the menu already knowing its number; the customer builds an order and sends it, and the order appears on a kitchen screen in arrival order with the table number and a ready button; the waiter sees open tables and each one's bill; table reservations by time and party size, with email confirmation and a reminder the day before; customer records with history and a stamp per visit; and an admin area only I can see, with revenue per day, average ticket, best-selling dishes and peak hours.
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.