gora.
EN
EnglishРусскийLietuvių
telegram mini apps · react · remote

Telegram Mini App Developer

Gora is an independent full-stack developer who builds Telegram Mini Apps end to end: the React front end inside Telegram, sign-in through Telegram itself, the NestJS back end behind it and the bot that opens it. Three Mini Apps for customers, dispatchers and drivers run in production on one platform.

Discuss a Telegram Mini AppView relevant work ↓
  • 3 Telegram Mini Apps in one production platform
  • Telegram sign-in with HMAC-SHA-256 validation, no passwords
  • Real-time order and driver-location events

Each item below exists in a production system I built; the details are in the delivery-platform case study.

  • A store inside Telegram

    A catalogue the customer opens straight from the bot chat. The catalogue is open without registration, the cart lives in the browser's localStorage and sign-in is requested only at checkout.

  • Sign-in without passwords

    Users are recognised by Telegram's signed initData, validated on the server with HMAC-SHA-256. On first entry a minimal profile is created from the Telegram account, and a real phone number can be attached later.

  • Dispatcher workspace

    A mobile console with an order list, drivers, customers and a live map, where a dispatcher assigns a driver in a couple of taps.

  • Driver app

    Shift status, assigned orders with Picked up, On the way and Delivered transitions, navigation links, a proof-of-delivery photo and an earnings tab.

  • Real-time updates

    Order and driver events are pushed to the Mini Apps over Socket.IO from a NestJS WebSocket gateway, so dispatchers and drivers see changes without polling.

  • Payments in the Mini App

    The same checkout as on the web storefront in a mobile layout. The delivery platform accepts cash on delivery, an internal wallet and crypto (BTC, ETH, USDT, USDC, TRC-20) with blockchain confirmation tracking.

  • Loyalty and referrals

    A wallet, cashback and a referral program with personal promo codes and share links, shared right inside Telegram.

  • Bots that open the Mini App

    Python bots on aiogram 3 launch each Mini App and send notifications. They talk to the back end through Redis pub/sub, so the API never depends on Telegram messages.

One platform with three Mini Apps and one Telegram product with subscription tiers. Each links to the full case study.

Last-mile delivery platform — three Mini Apps

Customer, dispatcher and driver Mini Apps on one multi-tenant platform (client under NDA).

What was done
Three standalone Vite 7 + React 19 Mini Apps served by nginx, next to a Next.js storefront, a 50-page admin panel and a NestJS API. Sign-in by HMAC-SHA-256 validation of Telegram initData, real-time order and driver-location events over Socket.IO, and three aiogram 3 bots connected through Redis pub/sub.
Problem solved
Give customers, dispatchers and drivers each a fast mobile surface inside Telegram, without coupling the back end to Telegram's message handling.
Technology
  • Vite 7 + React 19
  • Telegram WebApp HMAC
  • NestJS
  • Socket.IO
  • Redis pub/sub
  • aiogram 3
  • Docker
In numbers
  • 3 Telegram Mini Apps and 3 Python bots in one monorepo of 11 apps
  • Mini App sign-in by HMAC-SHA-256 validation of Telegram initData
  • The catalogue opens without registration; sign-in is requested at checkout

Read the case study →

GoraBot — Telegram product with subscription tiers

A Telegram assistant with Free, Basic and Pro plans and access to 12 models from four AI providers.

What was done
Plan limits enforced in the database, voice replies, project contexts with their own history and request logs for analytics, running as a single systemd service without extra infrastructure.
Problem solved
Run a paid Telegram product for a small audience without the weight of a platform: limits, billing logic and history in one place.
Technology
  • python-telegram-bot 21
  • SQLite
  • FastAPI
  • systemd
In numbers
  • Free, Basic and Pro tiers with limits enforced in the database
  • 56 users and 1,783 generations in the production database on the publication date
  • 14 active project contexts, each with its own conversation history

Read the case study →

Mini Apps
Telegram WebApp API · HMAC-SHA-256 initData validation · Vite 7 + React 19 · Tailwind CSS · Leaflet maps
Bots
Python aiogram 3 · asyncpg · Redis pub/sub
Back end
NestJS · PostgreSQL · Redis · Socket.IO
Operations
Docker Compose · nginx · GitHub Actions

From the first scenario to a Mini App running inside Telegram, with one person accountable.

  1. 01 · First message

    Write to me on Telegram. In your own words, even if you don't know the technical terms. I care more about understanding what you want to build than what you call it.

  2. 02 · Reading between the lines

    Within a day or two I understand the task and give you an estimate of timeline and budget. If I see it isn't my case — I say so right away, no hedging.

  3. 03 · Lock-in

    Price and timeline — in writing. 50% upfront. After that things change only by mutual agreement, and rarely.

  4. 04 · Work

    I show interim results at my own pace. At the end — handover with documentation and access. First month of support is included by default.

  • Direct communication with the developer. No agency middle layer and no project manager relaying messages.
  • Front end, back end, bot and deployment from one person, so the Mini App, the bot that opens it and the API stay consistent.
  • Production experience: three Mini Apps for the customers, dispatchers and drivers of one live platform.
  • I know where a Mini App differs from a website: it runs inside Telegram's WebView, so it is a client-side app and server-side rendering gives nothing there.
  • I work with existing systems: the Mini App can sit on top of your current API or database.
  • Source code and credentials are yours from day one.

I work remotely and communicate in English and Russian over Telegram, email and video calls on request.

Payment flows are built against the provider that fits your market. The agreement and verification process with the provider stay on your side; I build the integration against its API and agree the scope before I quote.

There is no standard price: a single-screen Mini App and a three-app platform with real-time dispatch are very different projects. The cost depends on the number of screens and user roles, whether checkout and payments are included, the real-time requirements, an admin interface and how much of the back end already exists.

Send a short description of the scenario on Telegram or by email. I reply with a written estimate of timeline and budget, usually within a day or two, and fix both in writing with 50% upfront.

How much does a Telegram Mini App cost?
It depends on scope: the number of screens and roles, checkout, real-time features and the state of your back end. I do not publish a price list; I send a written estimate of timeline and budget within a day or two of your first message.
What is a Telegram Mini App?
A web app that opens inside Telegram. Users install nothing: it launches from a bot or a link, runs in Telegram's WebView and knows who the user is from Telegram itself.
How does sign-in work in a Mini App?
Telegram passes the user's data in a string signed with HMAC-SHA-256 using the bot secret. The server recomputes the signature and, if it matches, trusts the Telegram user id, so nobody creates a password. On first entry a minimal profile is created and can be linked to a real account later.
Can a Mini App take payments?
Yes, with the payment methods your market supports. In one production platform checkout supports cash on delivery, an internal wallet and cryptocurrency (BTC, ETH, USDT, USDC, TRC-20). A card provider can be integrated through its API where one is available.
Do I need a bot as well as the Mini App?
Usually yes: the bot is the entry point and sends notifications, the Mini App is the screen. In my architecture they are separate: bots talk to the back end through Redis pub/sub and the Mini App talks to the API, so either one can be replaced without touching the other.
Which stack do you use for Mini Apps?
Vite and React for the front end, built as a client-side single-page app served by nginx; NestJS and PostgreSQL for the back end; Python aiogram 3 for the bots. A Mini App runs inside Telegram's WebView, so server-side rendering has no benefit there.
Can data update in real time without polling?
Yes. A NestJS WebSocket gateway with Socket.IO pushes order status and driver-location events to the dispatcher and driver Mini Apps.
Who owns the code and where does it run?
You own the bot token, the code repository and the data. I usually deploy to a VPS with Docker behind nginx, or to your own infrastructure, and hand over documentation and access at the end. The first month of support is included.

Describe the task in your own words. I respond within 24 hours, usually the same day on weekdays.

Elsewhere: GitHub·Telegram channel·Reddit·X