Every screen is a block on the map. Drag an arrow from a list item or a button to the next screen, and the preview shows right away how a customer will move through it.
From an empty map to a button in your bot — four steps, all in the browser.
Headings, images, lists, input fields, a map, a timer, shop products — add elements to a screen and set them up on the right. Theme colors are set separately for light and dark mode.
Buttons and list items lead to other screens, conditions, HTTP requests or a bot scenario. You see the whole logic at once, just like in the bot builder.
The preview shows the app on iOS and Android, in Telegram or in a browser, and the debug panel shows the path through the blocks and the variable values.
Publish a version and add the app button to your bot’s keyboard. The next version can be prepared alongside without touching the one customers see.
Text, images, video, buttons and lists, cards and accordions, a countdown timer, a map with directions. Input fields — text, date, switch, slider, star rating — save answers to variables on their own.
Every element has a display condition: by variable, tags, link parameter or where the app was opened. On the same screen a newcomer sees a welcome, and a regular customer sees their bonuses.
Products and categories come from the Shop section: typo-tolerant search, filters by attributes, product variants and a cart with a counter.
Checkout follows your shop’s delivery and payment options, and customers see their orders and statuses in the same app. The order lands in your dashboard right away, and the bot can confirm it in the chat.
The customer picks a service, a specialist or “anyone available” and a time. Free slots are calculated from the schedule in the Booking section — taken times are never shown.
A booking can be moved or cancelled in the same app and added to the customer’s calendar. A reminder before the visit and a request to rate it arrive in the messenger.
Input fields make up a form, and the answers go to your project lists — the same ones your bots work with. The “Form from a list” button builds a form from the list columns for you.
The List records element shows data as rows, cards or tiles, with filters, sorting and a “mine only” mode. That is how you build a customer account with their request history.
The app opens from a button in your bot’s keyboard in Telegram and in the website chat. A person’s variables and tags are shared with their bot contact: the name they gave the bot is already in the form.
From the app you can send a message on behalf of the bot, start its scenario or add a tag — for example, confirm an order in the chat and ask the next day whether everything was fine.
Screens adapt to the customer’s device: lists, switches, transitions and fonts look like system apps.
Your own colors for each theme. The app switches to dark mode by itself when Telegram or the phone uses it.
Side menu, bottom sheet, dialog, action sheet and pop-up hints — no separate screen for every little thing.
A screen can become a tab bar, like in big apps: catalog, cart and profile — one tap away.
A display condition on any element, branching on the map and variables in texts: “Anna, your order is ready”.
Data from your CRM or another service right on the screen: the request runs on the server or on the device, and the response goes into variables.
An HTML element and an HTML screen in an isolated frame, a JavaScript block and app-wide code — for example, for an analytics counter.
Up to 50 versions per app: build the new one alongside, publish it with one click and roll back the same way.
Start from any block, choose the platform and theme, follow the path through blocks and variable values as you go.
A failed request or script lands in the log with a hint and a link to the block where it happened. Entries are kept for 14 days.
Who opened the app and from where, with their variables and tags; opens, new people and popular screens for 7, 30 or 90 days.
From the browser, the app can be installed on the home screen and opens like a regular app — without the address bar.
Typical tasks that a single mini app covers — built from the same elements shown above.
Menu sections with photos and prices, a cart and pickup checkout. Orders arrive in the Shop section.
A catalog with search and filters, product variants, delivery, payment and the customer’s order history.
Services, specialists and free time by schedule, rescheduling and cancelling, reminders in the messenger.
A countdown to the end of the offer, a promo code on tap and a separate screen when time is up.
Fields, date picker, star rating. Answers go to a project list, the notification comes from the bot.
My orders, my bookings, my requests: everyone sees only their own data.
Mini apps are part of the Pro plan, together with bots, broadcasts and payments. The first 7 days are free.
It is an app that opens right inside the messenger from a bot button: nothing to install from an app store and no jump to a website. Telegram calls them Mini Apps. The same app also opens in the website chat and in a regular browser.
No. Screens are built from elements, transitions are drawn with arrows, and data is saved to project lists without setting up a database. For special cases there is an HTML element, a JavaScript block and HTTP requests, but a shop, booking or form does not need them.
In Telegram, in your bot’s chat on your website and in any browser via a link. From the browser it can be installed on the phone’s home screen and opens as a separate app.
To open the app from a messenger — yes: it is launched from a button in the bot’s keyboard, and up to 20 bots can be linked to one app. Via a direct link in the browser, the app works without a bot too.
Mini apps are part of the Pro plan; there is no separate fee per app or per launch. A project can have up to 100 apps. New accounts get Pro free for 7 days.
From the Shop and Booking sections of the same project: the catalog, prices, stock, delivery and schedule are managed there, and the app shows them to the customer. Orders and bookings come back to the same sections.
Through the payment provider connected to your project. The customer places an order in the app and goes on to pay, and the money goes to your account with the payment provider.
Yes. Your edits go into a new version while customers keep seeing the published one. When everything is ready, you publish the new version with one click — and can roll back the same way.
Analytics shows opens, people, new users, actions and popular screens for 7, 30 or 90 days. The Users section shows who opened the app and from where, with their variables and tags.