A window with real prices and stock
A product with a photo, variants, a price and a quantity. When stock hits zero the item leaves the window, and nobody buys what is not there.
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.
The order written out in the chat
The customer builds a cart and the app opens WhatsApp with the message already written: items, quantities, total and a note. You just check it.
A link and a QR code for your profile
A link for the Instagram bio and a QR code to print. It is what replaces the screenshot of a price list going round out of date.
What gets asked about and what sells
Most-viewed and most-ordered products, so you restock before running out rather than after.
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 digital catalogue for a clothing shop that sells through WhatsApp. Products with a photo, name, description, price, category, size and colour variants and a stock quantity per variant, leaving the window when the quantity hits zero; a public window with search and a filter by category, each product with its own page written to be found by search engines; the customer builds a cart and, on finishing, the app opens WhatsApp with the message already written containing items, variants, quantities, total and a notes field; a page with the link and a printable QR code for the shop; and an admin area only I can see, to add products, adjust stock and view the most-viewed and most-ordered products of the month.
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.