Cost

What a Telegram Mini App costs

A Mini App is a second interface, not a screen. Expect twelve to twenty-two delivery days for a production one, roughly double the front-end work of the same product built in chat alone. The cost sits in state, theming and server-side validation of Telegram's signed init data.

What a Telegram Mini App costs: effort, cost and what moves it

Fixed price: $7,560 USD
Delivery: Awaiting sign-off

Effort: 18 delivery days
Biggest cost driver: Init data validation and the Mini App shell
Commercial basis: Fixed price agreed before work starts; scope changes quoted separately
Year one, beyond the build: Support retainer, Managed hosting, plus media and asset storage, payment processing fees

As of 2025-10-01, Telegram Bot API 13.4

Why this costs what it costs

Mini Apps get quoted badly because they look like web pages, and web pages are a commodity. The framing that produces a sane estimate is different: a Mini App is a web application that runs inside somebody else's client, inherits its theme, authenticates through a signature rather than a login, and has to work on a mid-range Android phone on hotel wifi in a country you have never tested from.

The authentication alone is a line item people forget. Telegram hands your web view a block of init data signed with a key derived from your bot token, and validating that signature on the server is the only thing standing between your Mini App and anyone who can construct an HTTP request. Init data also expires, so a session opened and left overnight has to fail cleanly rather than silently act on a stale identity. Every Mini App we have been asked to review that was built cheaply had this wrong, usually by trusting the user id the client sent.

Then there is the theme. Telegram exposes its palette as CSS variables and users genuinely run every combination — light, dark, and a handful of custom themes. A Mini App that hardcodes colours looks broken for a meaningful share of your audience, and a Mini App that looks broken inside Telegram reads as untrustworthy at exactly the moment you are asking for payment. Getting this right is not difficult, but it is a real half-day of work and it is never in a cheap quote.

The honest counterweight to all of this: many products that ask for a Mini App do not need one. If the interaction is a sequence of questions with one answer each, chat handles it with less code, less latency and better completion rates. A web view earns its cost when the user needs to see many things at once and choose between them — a catalogue, a seat map, a basket, a chart. If your flow does not have that shape, the cheapest Mini App is the one you do not build.

The breakdown

Work	Days	Cost	What it covers
Interface scope	1	$420	Deciding which screens genuinely need a web view and which stay in chat. Usually removes work rather than adding it, which is why it is first.
Mini App shell	2	$840	The web view itself: viewport handling, Telegram theme variables, safe areas, the back button, and haptics where they belong.
Init data validation	1	$420	Server-side HMAC verification of Telegram's signed init data, expiry handling, and a session model that never trusts a user id sent by the client.
Screens and state	5	$2,100	The actual application: listing, detail, selection, basket or form, confirmation. State that survives a backgrounded phone and a dropped connection.
Backend and data	3	$1,260	The API behind the screens, with validation at the boundary and pagination sized for a phone rather than for a desktop table.
Chat integration	2	$840	The bot side: deep links into specific Mini App states, results posted back into the conversation, and a chat fallback for anything the web view cannot do.
Device testing and hardening	3	$1,260	Mid-range Android, older iOS, both themes, a slow connection and a small screen. This is where Mini Apps built without it fall over.
Deployment and handover	1	$420	Menu button and direct link registration, content security policy, monitoring, and a walkthrough with whoever operates it.
Total	18	$7,560	Fixed on signature. Scope changes are quoted separately, never absorbed silently.

What moves the number

Init data expires, and expiry must be enforced server-side on every request.

A Mini App cannot treat the first validation as a permanent login. Session refresh and clean re-authentication are part of the build, not an afterthought, and skipping them is the most common security defect in cheap Mini Apps.

Telegram exposes its theme as CSS variables and users run every combination.

Both light and dark are mandatory test targets, not a nice-to-have. Budget for a half-day of theme work and treat any quote without it as incomplete.

Payment inside a Mini App follows the same rules as payment in chat.

Stars remain restricted to digital goods and a card gateway still requires underwriting. A web view does not create a route around a provider that will not accept your category.

A Mini App is not indexed by search engines.

Everything inside it is invisible to Google. Products that depend on organic discovery need a public web surface as well, which is a second build rather than a variant of this one.

Every additional screen with its own data shape adds roughly a day.

Screen count is the most reliable predictor of Mini App cost. Cutting two screens saves more than any framework choice, which is what the interface scope session is for.

Offline and reconnect behaviour must be designed, not inherited.

Phones background apps and drop connections mid-transaction. A Mini App that loses a half-filled basket on reconnect will be blamed for the lost sale, and the fix costs less before launch than after.

What year one actually costs

Running cost	Year one	Detail
Support retainer	$3,480/yr	Telegram ships client changes that affect web views — viewport behaviour, theme keys, new platform capabilities — several times a year, and a Mini App is the surface most exposed to them.
Managed hosting	$660/yr	A Mini App serves static assets and an API rather than just handling webhooks, so it carries slightly more infrastructure than a chat-only bot. The operational responsibility is the cost, not the bandwidth.
Media and asset storage	billed by the provider	Catalogue imagery and user uploads are billed by whichever object store you use, and are driven by how disciplined your image pipeline is rather than by traffic.
Payment processing fees	billed by the provider	Charged per transaction by your provider. Stars and a card gateway have materially different economics at low price points, which is worth modelling before choosing.

Buying the same thing elsewhere

Where you buy it	What the money buys	What you carry
A general web development shop	Competent React and a familiar delivery process at a rate below specialist pricing. The screens will be fine and the code will be readable.	Telegram-specific surface — init data validation, theme variables, viewport quirks, the back button contract — is learned on your budget, and the security-critical part is the part they have not done before.
A native mobile studio	Real product design instinct for small screens, and a team that understands mobile state and offline behaviour better than most web shops.	Native habits translate badly. Expect proposals for splash screens, custom navigation and onboarding flows that Telegram already provides and that users find intrusive inside a chat client.
A no-code Mini App builder	A storefront or form running in days for a monthly subscription, with no engineering at all. For validating whether anyone will use it, this is the right first step.	Your data lives in their account, the checkout is theirs, and the ceiling arrives the moment you need logic they did not anticipate. Plan the exit before you need it.

Questions about the money

Do we actually need a Mini App, or will chat do?

Chat wins when each step has one answer — pick a date, pick a time, confirm. A web view earns its cost when the user has to see several options at once and compare them, like a catalogue, a seat map or a basket. If you cannot name a screen where comparison happens, you probably do not need one.

Can a Mini App be added to a bot we already have?

Yes, and it is a common second phase. The chat bot keeps its flows and the Mini App takes over the screens that need one, sharing the same backend. Adding it later usually costs a little more than building both together, because some flows get rewritten rather than extended.

Does a Mini App work outside Telegram?

Not without changes. It authenticates through Telegram's signed init data, which does not exist in a normal browser session, so reaching non-Telegram users means adding a second authentication path and a public entry point. That is a real piece of work and should be decided at the start.

How does this compare to building a native app?

A Mini App removes the install step, the store review and the download funnel, which is where most Telegram-distributed products lose their audience. A native app buys real push notifications, device APIs and a home screen icon. The install funnel usually decides it, and the full argument is on the dedicated comparison page.

Who pays for the design?

Design is inside the screens-and-state line rather than billed separately, because a Mini App inherits its type, spacing and colour from Telegram. What is genuinely a design decision here is information hierarchy and flow order, which is engineering-adjacent work and is priced as such.

Can it be one screen inside an otherwise chat-based bot?

Yes, and that is often the cheapest good answer. A single web view for the one interaction that needs it — a seat map, a long form, a chart — keeps everything else in chat and keeps the build near the bottom of this range.

What breaks most often after launch?

Theme regressions and viewport changes after a Telegram client update, and stale init data on sessions left open overnight. Both are cheap to fix and cheap to catch, which is most of the argument for the support retainer on a Mini App specifically.