Help centre

Getting started

What you are building — A mini app opens inside Telegram and MAX — not in a browser. Almost everything else follows from that.
Your first app in one sitting — The short road from a blank canvas to a button in your bot — seven steps.
How the editor is laid out — Four areas: the screen strip, the left panel, the canvas and the properties on the right.
Templates: apps and screens — An app template replaces the whole project; a screen template adds one screen to what you already have.
Build an app from a description — Describe what you need in words — the screens, tables and links are built for you. After that it edits like any project.
Checking your work: preview and phone — Preview behaves for real: navigation, forms, cart. Check on a phone — that is where the app will be opened.
Where your project lives — The project saves itself. The published app only updates when you press the button.
Your password and phone number — Both change from the account menu. A new number is confirmed in the messenger, the way it was at sign-up.
Where each setting lives — There are about forty settings, scattered across several places. You do not have to remember the map: there is one, and a search.

Screens and navigation

Screens and the start screen — An app is a set of screens. One of them is the start screen: that is where everything opens.
The “No way in” badge — In the editor you open a screen from the strip. In Telegram there is no strip — the screen needs a way in.
Moving between screens — Navigate to screen with a transition, Back — and the difference between “over” and “replace”.
The shell: header and bottom menu — Pinned to the shell, the header and the menu show on every screen and stay put during transitions.

Blocks on a screen

Components: placing and selecting — Drag from the panel, nest, use layers, right-click for the rest.
Layout: containers, grid, spacing — Container and section to group, grid and columns for rows, spacing for air.
Text, images, icons — Heading, paragraph, caption, badge; images with aspect ratio and cropping; avatar, carousel, audio, video, QR.
Editing text on the canvas — Double-click edits the text right in the block; on a phone, a second tap does. A strip above it does bold, italic and a link inside the text.
Inputs and the form — A form binds fields into one submission. Every field has a name — that is the name the answer arrives under.
List from a table: showing records — One card, any number of rows. Design it once, it renders them all.
Filtering and searching a list — Chips or an input remember a value, and the list filters by it.
Commerce components — Product card, price, quantity stepper, option select, total, cart badge.
Choosing an option: highlight the tap — A tap remembers the choice, and what is remembered highlights what was chosen — a master, a date, a time, a seat category.
Tabs on a single screen — A strip at the top switches the content while the screen stays the same.
Workout timer — Intervals with rounds, and a stopwatch: the block runs the session itself and remembers the result.
Address and directions — Where you are, opening hours and a “Get directions” button.
Seating chart — A seating chart the visitor taps to pick seats: cinema, theatre, venue.
Sectors: a stadium — Stand tiles with a price and what is left; seats come from the hall inside a sector.
Map — A place on a map — by address, by coordinates or by a Yandex Maps link.
Telegram components — The main button at the bottom and the popup — Telegram draws these itself.
My components and blocks — A component is edited once and changes everywhere. A block is just a saved snippet.
Flexible block: one instead of eight — For when a ready-made block almost fits and one property is missing.
Record counter — How many table rows match a condition — as a number on screen and in the app memory.
Chat — A one-to-one conversation inside the app: the visitor writes to the author, the author answers, and the bot notifies both.

Look and feel

Project styles: colours and fonts — One set of colours and fonts for the whole app, edited in one place.
Styling a single element — The Style tab: colours, text, border, radius, shadow, opacity.
Messenger theme and dark mode — Unset colours come from the client’s theme. The ones you set stay yours.
How the app looks on a computer — A separate layout for wide screens; what you built for the phone stays untouched.

Data

Tables: columns and rows — Products, services, events — filled in the editor and shipped with the app.
Column types — Text, number, yes/no, image, file, date, time, random code, relation, select, multi-select, hall layout.
Tables: a step-by-step guide — What a table is, how to create one, link it to another, fill it in and show it in the app — from scratch, no coding.
Relations between tables — An event points at a venue — and the event card prints its address.
App memory — The app’s memory for the session: the chosen category, the tapped card, the cart.
Substitutions {{…}} — How to put data into text: a row field, something the app remembered, the user’s name, the time.
Visibility conditions — Show or hide a block depending on state: is it empty, equal, earlier.
Rows added from the app — Top up a catalog from your phone without opening the editor: add, edit, delete.
Rows written by visitors — Cart, favourites, order history, reviews — the things that survive closing the app.
Points and a loyalty programme — Points for every member: earned on payment automatically, adjusted by you, spent by the visitor.
A file from a visitor — A CV, a photo of the damage, a lab referral — attached right in the form.
Importing a table from a file — Your price list is already in Excel or Google Sheets — no need to retype it.
A live table as a source — Google, Yandex Disk or your own address: the table stays yours, the app refreshes itself.

Actions

Actions: when and what — What happens on tap, when a screen opens, or when a field changes.
Every action, listed — What an app can do: navigation, messages, data, payments, Telegram.
Cart and favorites — A list in the app memory: private to each visitor — a table cannot do this.
Submitting a form — Where a filled-in form goes and what the person sees afterwards.

Publishing

Publishing and the address — Publishing puts the project in the cloud and issues an HTTPS address to attach to your bot.
Connecting your bot — The mini app opens from your bot, and that same bot writes to your clients.
Two buttons in Telegram — The in-chat menu button attaches itself. The Open button on the bot’s profile is BotFather only.
Publishing to MAX — The same app runs in MAX too, but the address is pasted by hand in the partner console.
A custom domain — The app opens at your own address. No hosting needed, the certificate is issued for you.
The trial and what follows — Three days from your account’s first publish, covering everything it publishes.
The app as a site: signing in, search, installing — One app opens both in a messenger and from a link in a browser — with the same person inside.

Money

Selling access to video — Upload lessons to us, close them behind a subscription, and know what this protection cannot do.
Taking payments inside the app — Money goes to your own merchant account, not to us. YooKassa or T-Bank.
Platform plans — How Trial, Start, Pro and Studio differ.

After launch

Submissions — Everything filled in inside the published app. An archive for when a message does not arrive.
Automation: n8n, Make, your own server — App events go out to you as a webhook, and rows you send land in a table.
Statistics and goals — Opens, visitors, screens — and whatever you decided to count.
The app’s QR code — A code for your window, card or table — and a separate one for previewing on a phone.
Edit history and undo — ⌘Z undoes, ⌘⇧Z redoes, and the history lets you jump several steps back.
Keys and the command palette — ⌘K searches the whole editor, ⌘/ shows the keyboard cheatsheet.
Working from a phone — A phone is good for edits and publishing; building from scratch is better at a computer.
When something is broken — Feedback with a screenshot, a reply in Telegram, and separately “Suggest an idea”.

Walkthroughs

Case: an event listing with filters — A list of events, filtering by section, an event page and a Book button.
Case: a shop with a cart and payment — A catalog, a product page, a cart in the app memory, payment through your merchant account.
Case: booking a service — Services, staff, date and time, and a request to you in Telegram.
Case: topping up a catalog from a phone — A “+” button only you can see, and editing rows right inside the app.