A mini app from a description: AI builds the screens, tables and links
You write: “a coffee shop — a catalogue of beans filtered by roast, a product page, a cart and checkout with delivery”. About twenty seconds later the editor opens an app: six screens, a product table with real names and prices, a cart visitors write into, and the links from the shelf to checkout. From there it is an ordinary project — edited with the mouse and published to Telegram and MAX.
How it goes
- 1
Describe it in words
The ✨ button in the editor opens a conversation. Write the way you would explain it to a person: what you sell, which screens you need, what a visitor does on them. The more detail, the closer it lands.
- 2
Read the plan
The plan arrives first, within seconds: which screens, which tables, which variables. It tells you whether you were understood before a single screen is built.
- 3
Check the preview
The screens appear as phones right in the conversation, and you can swipe through them. Not right — say what to change in the next line and build again.
- 4
Open it in the editor
From there it is your project: texts, prices, colours and blocks are edited with the mouse like anywhere else. Publishing and the bot work exactly as for an app built by hand.
What lands in the editor
- four to seven screens with the links between them
- a bottom menu and a header that navigate
- tables with fields and sample rows from your trade
- variables for search, filters and the selected row
- forms that send a request to the owner or write a row
- an accent colour and an icon that fit the trade
It builds a whole app, not a single screen
A screen with no way in does not exist inside a messenger: screens have no addresses, and the only way to reach one is a link. So the build checks that itself — every screen must be reachable by a button, a bottom-menu item or a header icon — and whatever is missing is filled in before the app reaches you.
In a shop that means: the shelf leads to the product page, the product to the cart, the cart to checkout, checkout to the order status. The same path you would wire by hand, in twenty seconds.
Tables arrive filled in
An app with no data is a mockup. So the tables come with real rows from your trade: beans with a roast and a price for a coffee shop, classes with an instructor and a time for a yoga studio — not “Item 1” and “Service 2”. They are samples: replace them in the data panel or connect a Google Sheet.
Tables a visitor writes into — cart, requests, bookings — arrive empty and private to each visitor. Nobody should see somebody else’s order in their own app.
The request can be about one screen
Whether it is an app or a screen is decided by the request itself, not by the section you came from. “I want a coffee shop” builds a whole app. “Add a reviews screen” adds one screen to the open project — one that knows its tables and variables and can link to them. Nothing is erased.
How this differs from a website generator
A mini app is not a website. It opens inside Telegram and MAX, knows who opened it without a single password, and lives as a button in your bot’s menu. So it is built out of screens, tables and actions — add to cart, leave a request, book a time, pay — rather than out of pages.
And the result is not text you paste somewhere: it is a real project in the builder, with a block tree, properties, data and publishing. Not happy with it — edit it with the mouse instead of rewriting the prompt.
The limits, stated plainly
- How many builds a month comes with the plan: 2 on the free trial, then 12, 40 and 120 as the plan grows. What is left is shown in the panel’s header and the count resets on the first of the month.
- Editing what is already built by talking to it is not possible yet: “make the button blue” will not be understood. Build again with a different description, add a screen, or edit with the mouse.
- Pictures in a built app are links to a free photo stock. Your own are uploaded in the editor.
- The build does not lay screens out for the desktop: on a monitor it stays a phone-width column until you do it yourself.
Questions people ask
- Do I need to know how to code?
- No. You describe the app in words and adjust it with the mouse — dragging blocks and filling property fields. There is no code at any step and no server to run.
- How long does a build take?
- About twenty seconds for a six-screen app, measured on the production server. The plan arrives within seconds, then every screen is built at once rather than one after another.
- How many builds does a plan include?
- Two a month on the free trial; 12, 40 and 120 on the paid plans as they grow. One build is a whole app or one added screen. What is left is written in the panel’s header.
- Can I change everything afterwards?
- Yes. What is built is an ordinary project: screens, blocks, tables and actions are edited by hand exactly as in an app built from scratch or from a template.
- Will the app work in Telegram and MAX?
- Yes, publishing is the same. In Telegram the bot’s menu button is set automatically; in MAX the address is pasted into the partner dashboard by hand, because they have no API method for it yet.
- Does the data stay mine?
- Yes. The app’s tables live in your project: you can see them in the data panel, edit them, export them and connect a Google Sheet.
Build an app from a description
Three days free, no card. Enough to build it, publish it and show it to people.
Open the builder