Web apps
One implementation that lives in the browser and in Telegram, talking to your inventory — not two native apps and an app-store cycle.
Typical timeline: Scoped from a written brief. A first channel, then the second on the same code.
Typical jobs: a catalog with a short checkout, a booking calendar, a dealer cabinet, a loyalty pass on the home screen. Telegram Mini App and PWA share one implementation. The front detects the container: messenger SDK, or a standalone icon without a browser chrome.
Authorisation can use Telegram init data in the Mini App and WebAuthn on the PWA. Cart state survives a closed chat. Offline cache is for shell and catalog, not for inventing stock.
For whom
Businesses that need a mobile surface without an app-store review loop
Teams whose visitors will open a chat or tap an icon, but will not download a 200 MB binary
Operators who already have inventory or ERP and will not accept a disconnected demo
What you get
- PWA and/or Telegram Mini App on one codebase
- Payments through Stripe or cards; Telegram Stars where they fit the product
- Push where the channel allows it
- Inventory or ERP hook named in the brief
How it goes
- 01
Written brief: the job in the messenger, the catalog, the payment path
- 02
Pilot one channel on live inventory
- 03
Add the second channel without a second product
- 04
Handover: payments, push, stop switch, named owner
What we do not do
We do not sell two native apps as the default. We do not route payments through a local instant-transfer scheme. We do not hide a second storefront that cannot share the catalog.
After launch
Server, backups, a one-hour incident SLA, and planned updates can be scoped in the same brief. That is not a separate service page.