A menu with add-ons and required choices
Product, category, photo, price, paid add-on, required option and sold-out flag. Changing a price edits a record; it does not republish the 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.
Delivery fee and coverage by area
Areas you serve, a fee and minimum per area, and counter pickup. The customer learns whether you deliver before building a cart, not at the end of it.
Payment in the app and at the door
Card and local methods through Stripe, Pagar.me or Mercado Pago, with the card fields drawn by a hosted vault. Cash is a recorded method, with change owed.
An order status the customer can watch
Received, preparing, out for delivery and delivered, each change sending a push. It is the screen that ends the phone calls asking where the order is.
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 delivery app for a burger place. A menu with categories; products with photo, price, paid add-ons and a required doneness choice; a cart; delivery areas each with their own fee and minimum order, plus counter pickup; payment by card in the app or on delivery, with change owed; opening hours per weekday that close the cart outside them; discount coupons; order tracking for the customer in four stages, with a push at every change; and an admin area only I can see, with the day's orders in a queue, revenue per day and the ten best-selling items.
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.