Skip to content
All work
WebBots2026 · ~2 min read

A trainer's and their clients' workspace inside Telegram

The trainer uploads a programme as a file and sees who is keeping to it. The client opens today's session, ticks off exercises, logs weight and food and sends a video report — all inside Telegram, with nothing to install.

An exercise is closed with a button and turns to done, the day closes behind it, and logged food moves the day's figures. The client's name and logo are cropped out.

# The problem

The client is a personal trainer working with people remotely. Other trainers were to come later, so the system was built for several from the start rather than for one. This normally lives in a chat thread. The programme goes out as a file or a picture, the report comes back as a message, the trainee writes down weight and food however they please, and the trainer pieces it together by eye. With one client that works. With ten there is no telling who is on which week, or who is training at all. Hence the requirements. The client needs one place showing today's session. The trainer needs a picture of each person without scrolling a conversation. And nothing to install: nobody sets up a separate app for three buttons.

# The solution

The whole thing lives inside Telegram as a web app. The client opens it from the bot and lands straight in their own workspace: nothing to install, no sign-up, they are already identified. The trainer uploads the programme as a file — weeks, days, exercises. The system unfolds it into a schedule, so the client sees only today's session instead of hunting for their day in a shared table. Completion is ticked off as it happens, right in the exercise list. Data comes back the other way: weight and sets for each exercise, a food diary with calories and macros, daily activity. And a video report — the client films the work, the trainer watches and leaves a note attached to the exercise. The trainer has an interface of their own: the client's card, their programme, their diary, their reports. The programme is corrected from here, and the starting week is set here too. The layouts and the design are the client's. What I answered for is how it works.

# The outcome

The system is running. I have no metrics: there is database access and users are being created in it, but who among them is how active I never went through — that is the client's data. Development took a month. There were no hard parts here and I am not going to pretend otherwise: a clear brief and a familiar stack. Not every project has to be a challenge — part of the job is doing the straightforward thing quickly and without surprises.

# How it works

  1. TrainerUploads the programme as a file, watches the reports and leaves notes against exercises. The system allows for several trainers, though one works it today.
  2. ClientSees today's session, ticks off finished exercises, enters weight, food and activity, and sends a video report.
  3. Telegram botThe way in for both of them, and the authentication too: the messenger has already identified the person, so there is no separate sign-up.
  4. Web appThe workspace opens inside Telegram. Nothing to install — for an audience that will not set up a separate app for three buttons, that decides it.
  5. API · RESTUnfolds the uploaded programme into a schedule of weeks and days, and takes back completion marks, weight, food and reports.
  6. PostgreSQLProgrammes, exercises, the history of what was done, the food diary and activity for every client.

Dashed: not my work — platforms and the client’s own systems

Next project

A tutor's online platform: lessons, homework, schedule

Need something similar?

Discuss the task