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. Persist and test cart state across a closed chat on the supported clients. Offline caching can retain the shell and selected catalog data; show its age and keep an offline draft distinct from an accepted order. See the PWA and Mini App comparison for platform and offline limits.
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 matched to platform rules: Telegram Stars for digital goods/services inside Telegram; supported providers for physical goods/services and web checkout
- 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. The payment method must fit the goods, market and platform rules. 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.