Work39

The brief

A purchase request moves through several roles and approval stages. The UI preserves drafts, exposes permitted actions, and guides users through long forms.

My work

As one of two frontend engineers, built forms, role-based access, stage transitions, and change history. Moved the module build to Vite end to end; integrated Orval from OpenAPI and Keycloak SSO.

Outcome

• Consolidated procurement approval into one predictable interface
• The module build moved to Vite, with code splitting applied to long workflows
• Orval removed manual type updates when backend contracts changed

The brief

The ticketing service needed its own seats.io-like venue editor and seat picker widget that could be embedded into event sites without external SaaS.

My work

Canvas hall-layout editor, embeddable seat picker, events and bookings. Storefront, checkout, and Mini App on the same API.

Outcome

• Organizers create venue layouts and connect seat selection without custom work per venue
• Embeddable seat-picker widget works on the storefront and in Telegram Mini App
• Hall, seat, and purchase data stay inside the product infrastructure

The brief

Streamers accept tips in Telegram, configure alerts in a dashboard, and show them in OBS — three clients, one sendonate backend.

My work

Built the streamer dashboard, Telegram Mini App, and OBS overlay with React/Vite. Extended the Python/Django REST API for streamer collections and reset history, currencies, donation processing, and moderation. Added alert queueing and WebSocket reconnection.

Outcome

• Three clients share one API — tips are not lost between Mini App, dashboard, and stream
• Extended and tested the Python/Django REST API for currencies, streamer collections, and donation processing
• OBS overlay queues alerts during donation bursts

The brief

Users need to choose a specialist, place an order, move to chat, and hold an audio or video consultation in one service.

My work

Built the catalog, account area, and chats on Next.js. Implemented WebRTC signaling through Socket.io with ICE candidate queueing. Extended the NestJS API, generated the client through Orval, and covered core flows with Playwright.

Outcome

• Users complete the journey from catalog to paid consultation in one product
• Video calls run on WebRTC with ICE candidate queueing before connection setup
• Orval generates the TypeScript client from the OpenAPI contract

The brief

Candidates and founders need different registration, profile, and vacancy flows within one responsive interface.

My work

Developing the Vue 3 / Nuxt 4 frontend: responsive Figma implementation, candidate onboarding and platform tour, vacancy and profile interfaces. Connecting the UI to existing APIs, handling role and status states, and checking flows on mobile and desktop.

Outcome

• Implemented responsive candidate welcome and platform tour screens for mobile and desktop
• Vacancy and profile interfaces reflect user roles and onboarding stages
• User flows are checked with automated tests and Playwright

The brief

Clients and specialists need quick actions and reminders in Telegram alongside the web cabinet.

My work

Built a NestJS bot that links Telegram to the user's account, provides separate client and specialist menus, and sends consultation, review, earnings, and profile-view notifications. Buttons open the relevant website section.

Outcome

• Client and specialist get a reminder one hour before a consultation
• Specialists get digests: reviews, weekly earnings, profile views
• Duplicate pushes are blocked by dedup records in PostgreSQL

The brief

Admins and moderators need to react quickly to specialist applications, support tickets, and reviews from Telegram.

My work

Built a separate NestJS bot for admins and moderators with role-based notifications, application approval and rejection, ticket and review actions, and an audit log.

Outcome

• Admins and moderators receive notifications based on their roles and permissions
• Applications, tickets, and review moderation can be handled in Telegram
• Every action is written to an audit log

The brief

The sales team needed a light CRM for specialists: contacts, pipeline stages, tasks, and stats — without a heavy external system.

My work

Built a self-hosted CRM with Express, Grammy, and PostgreSQL: admin/manager/viewer roles, specialist database import, Telegram bot, Mini App with tasks and statistics, and scheduled reminders.

Outcome

• Specialist database and pipeline are available from the bot and Mini App
• Tasks get morning reminders on an MSK schedule
• Deployed via Docker / Coolify on own infrastructure

The brief

Blast furnace operators recorded cast iron releases manually: data was hard to filter by shift, and plant network connectivity was unreliable.

My work

Built a React SPA with TanStack Table for large datasets, React Query caching, and Sentry monitoring. Integrated Keycloak authentication.

Outcome

• Core shop-floor operations moved into one web interface
• Filtered, sortable tables handle large datasets without UX degradation
• Production errors are collected in Sentry

The brief

The production service has dozens of entities, roles, and API contracts: operators need one predictable interface instead of scattered screens.

My work

Building the React application for sites, pools, warehouses, workshops, and staff, including RBAC, Yandex Maps, and charts. Orval generates the API client and TypeScript types from OpenAPI.

Outcome

• Forms and lists are separated into production modules using an FSD structure
• RBAC limits screens and actions for each role
• Effect-TS keeps API errors and asynchronous operations typed
• Orval generates the API client and TypeScript types from OpenAPI

The brief

Farm operators needed a phone client on the same API as the web ERP: sites, warehouses, map, sales, and RBAC — plus an iOS build.

My work

Building the React Native / Expo app: Django REST auth, RBAC, sites and Yandex Maps, goods and sales, and an SSE assistant. Set up OpenAPI codegen, EAS Build, and iOS shipping.

Outcome

• Staff sign in on iPhone and see only their sites and roles
• Map and production objects are available on the phone, not only in the web ERP
• iOS builds go through EAS; the API client is generated from OpenAPI

The brief

A major e-commerce site migrated catalog and homepage from legacy PHP/Symfony to Next.js while keeping filters, SSR, and microservice alignment.

My work

Contributed to online store migration: Next.js SSR, filters, sort, URL-state pagination, REST API with backend teams. Code review, Jest.

Outcome

• Online store catalog on Next.js with SEO preserved
• URL-synced filters for wholesale and retail flows
• REST contracts aligned with backend and microservices

The brief

Security analysts needed entity graphs, filters over large datasets, and configurable dashboards in one product.

My work

Built threat categories, a GraphQL/Apollo relationship detail form, part of a D3.js entity graph, and virtualization for long lists.

Outcome

• Analysts explore entity relationships in an interactive graph
• Dynamic reports connect to the same data model as core workflows
• Virtualization keeps heavy lists responsive in the browser

The brief

The ticketing service needed matching purchase flows in the browser and Telegram, plus analytics for organizers.

My work

Built the Next.js storefront with an Orval API client, TanStack Query caching, React Hook Form and Zod forms, localization, a Telegram Mini App, and sales charts.

Outcome

• Ticket purchase works on web and Mini App with shared logic
• Organizers get basic sales analytics
• Localization covers core user flows

The brief

An NDA client needed the full user journey from catalog to checkout with localization and observability.

My work

Built the Next.js 14 app: Orval, TailwindCSS, React Hook Form + Zod, next-intl, Storybook, Playwright e2e, and Sentry in production.

Outcome

• User flow from catalog to checkout lives in one application
• OpenAPI client is generated automatically — fewer integration bugs
• Playwright and Storybook guard UI regressions

The brief

The startup needed an MVP: respondent search, surveys, roles, reports, and a marketing site — from zero to production.

My work

Built the platform on React + Redux Toolkit and REST API, marketing on Gatsby + Contentful, Firebase Auth with 2FA and PWA.

Outcome

• MVP shipped to production with roles and survey-based matching
• PWA and 2FA met baseline enterprise client requirements
• Marketing site and app evolved in parallel

The brief

The enterprise system needed configurable process templates without code changes for each new workflow.

My work

Template module on React + Redux Toolkit, REST via OpenAPI. Task breakdown, code review, memoization on heavy screens.

Outcome

• Process templates configurable without developer involvement
• OpenAPI contract kept frontend and backend aligned
• Team worked in Scrum with regular code review

The brief

An internal corporate knowledge base needed independent sections, a shared UI Kit, and stable user flows for teams maintaining documentation and work materials.

My work

Built new React features, improved UI Kit components, and integrated application parts into a micro frontend architecture via Module Federation. Wrote automated tests for user flows, including Playwright e2e tests.

Outcome

• New functionality shipped inside one Confluence-like product without a separate app
• UI Kit kept the interface consistent across knowledge-base sections
• Playwright tests covered key user flows

The brief

OpenSearch Dashboards had to integrate with Vault and rotate TLS certificates without manual ops.

My work

Small improvements around Dashboards–Vault integration in Node.js, GitLab CI certificate rotation, and Jest tests in pipeline.

Outcome

• Certificates rotate via CI without manual steps
• Jest covers critical integration steps
• Visualization module wired into corporate environment

The brief

SmartFish retail needed a tablet POS: open a shift, build a cart, take cash and card, and talk to the in-store POS terminal.

My work

Building a tablet POS with React Native and Expo: cashier authentication, shifts, catalog, cart, and cash, card, or QR payments. Added cashier and manager roles, Expo Router navigation, Zustand, and EAS Build.

Outcome

• Cashiers run shifts and sales from a tablet in the store
• Card payments go to the POS terminal over LAN with receipt printing
• Role split: cashier on a shift, admin/manager in view mode without opening a shift

The brief

Brigade leads submit Excel files in different layouts. Feeding, mortality, and stocking need to match database operations without rewriting the report by hand.

My work

Built a Flask web service: Excel upload, Random Forest layout parsing, deterministic PostgreSQL matching by pool and date, two Excel reports out. Packaged with Docker Compose.

Outcome

• Different Excel layouts parse without manually remapping columns
• Summary and per-pool balance export as separate files
• The service reads PostgreSQL only and does not change production data

The brief

Public storefront, B2B cabinet, and Aquaprom share one API — orders, cart, RBAC, and payments in one backend.

My work

Extending a NestJS API for orders, cart, payments, promocodes, bonuses, administration, and RBAC. Working with TypeORM, PostgreSQL, webhook handlers, and WebSocket.

Outcome

• The B2B cabinet and retail storefront use the same NestJS API
• Admin covers catalog, users, promocodes, and bonus flows
• The retail storefront and B2B cabinet consume the same OpenAPI contract

The brief

Marketing site and online shop on one domain (akvaprom.kg): catalog, checkout, profile, bonuses, and promocodes separate from the ERP client.

My work

Storefront on Next.js: homepage with carousels and categories, shop, checkout, profile, bonuses, promocodes, Yandex Metrika, Framer Motion.

Outcome

• Shoppers go from homepage to checkout without opening the ERP
• Bonuses and promocodes are part of the online-store user flows
• akvaprom.kg storefront reached the first page of Yandex for its target direction

The brief

The shop domain had no company mail. Work inboxes needed to send and receive without putting a heavy mailcow stack on a small VPS.

My work

Designed and brought up mail on the same VPS as the site: Stalwart in Docker, DNS for mail.akvaprom.kg, SMTP/IMAP, and memory limits so the storefront and API stay healthy.

Outcome

• Work inboxes live on akvaprom.kg instead of a third-party host
• Mail runs in Docker beside the storefront, without mailcow
• DNS points mail.akvaprom.kg at the same server as the site

The brief

B2B managers need morning/noon order summaries in Telegram; retail needs instant alerts on new orders.

My work

Built Telegram automation on NestJS: scheduled B2B reports with XLSX attachments, reminders, a webhook bot, and retail-order notifications.

Outcome

• Scheduled B2B report posts to chat with XLSX attachment
• New retail order triggers a Telegram message
• Bot subscribers and commands stored in PostgreSQL

The brief

Traders needed a web UI to compose strategies and view live quotes.

My work

Built screens on React + Vite, Firebase integration, TradingView lightweight-charts and Recharts, REST via axios.

Outcome

• Users compose and review strategies in one interface
• Quote charts sync with REST data
• Firebase covers auth and basic settings storage

The brief

The exchange needed a fast trading UI with a live quote stream and Solana wallet integration.

My work

Built the UI on Lit, market stream via socket.io, web3.js and wallet adapters, esbuild pipeline.

Outcome

• Orders and order book update over WebSocket without page reload
• Solana wallet connected to trading flows
• esbuild enables fast UI development iterations

The brief

A cosmetics store needed a responsive catalog, filters, and cart within 1C-Bitrix and Symfony.

My work

Extended 1C-Bitrix components and templates: catalog, product pages, filters, cart. HTML5, CSS3/SCSS, jQuery, JavaScript, Webpack, Git. PHP/Symfony backend integration.

Outcome

• Responsive catalog and product pages across breakpoints
• Filters and cart integrated with the PHP/Symfony backend
• Commercial team delivery with Git and code review

The brief

Bitrix e-commerce with a large catalog needed stable filters and a fast product page.

My work

Extended catalog, filters, and product cards; optimized frontend for mobile traffic.

Outcome

• Catalog, filters, and product pages extended in 1C-Bitrix
• Product pages adapted for mobile

The brief

An electricity accounting service for energy retail companies relied on heavy postback forms; users needed a responsive UI for forms and reports.

My work

Migrated forms and tables to AJAX, extended UI on Symfony + Bitrix.

Outcome

• Forms and reports work without full page reload
• Forms and reports update through AJAX without a full page reload

The brief

A building supplies store needed catalog and cart on a modern frontend stack.

My work

Built catalog and cart UI on Next.js, responsive layout and backend API integration.

Outcome

• Catalog and cart work on mobile and desktop
• Catalog and cart integrated with the backend API

The brief

The corporate site needed frontend maintenance and growth on legacy Bitrix.

My work

Maintained and extended site sections, built new blocks on Bitrix + jQuery.

Outcome

• New sections shipped on schedule within CMS
• Shared SCSS stack across pages

The brief

Energy retail companies needed a web UI for electricity accounting: forms, tables, and reports.

My work

Built the client side of the service: AJAX forms and tables, integration with Symfony/Bitrix backend.

Outcome

• Client UI stable in production
• Forms synced with backend

The brief

Fans needed to pick a seat on an interactive stadium map and complete checkout.

My work

Stadium map rendering on Canvas, integration with ticket sales backend.

Outcome

• Interactive seat selection on arena map
• Map synced with seat availability

The brief

The mobile app needed an embedded web client with WebView constraints.

My work

Adapted React UI for WebView: viewport, navigation, native bridge.

Outcome

• UI works in iOS and Android WebView
• Navigation aligned with native shell

The brief

The Telegram game needed new onboarding and attack mechanics without hurting performance on low-end devices.

My work

Moved game logic into Redux-Saga, optimized Vite builds and WebP conversion, covered key flows with Vitest.

Outcome

• New onboarding and attack mechanics shipped in the Telegram Mini App
• WebP and chunking reduced asset weight on mobile clients
• Vitest guards game-flow releases

The brief

The game had to run in Telegram WebApp: sockets, TON wallet, animations, and analytics in one client.

My work

Built UI on React + MobX, real-time via socket.io, TonConnect, Orval for REST, Framer Motion and Lottie for motion.

Outcome

• Playable Mini App with TON payments
• Socket.io events are handled in a dedicated MobX state layer
• Telegram analytics wired for product decisions

The brief

A lightweight game MVP inside Telegram needed persistent progress between sessions.

My work

Built the game on Next.js App Router, Zustand, Radix UI, Supabase SSR for profile and progress, WebApp viewport adaptation.

Outcome

• Playable MVP inside Telegram without a separate install
• Progress persists in Supabase between sessions
• UI adapted to WebApp constraints

The brief

The browser prototype needed a maintainable mobile game architecture with responsive controls and core gameplay mechanics.

My work

Migrated the monolithic HTML prototype to a modular TypeScript and Vite architecture. Implemented the game loop, pseudo-3D road perspective, touch and keyboard controls, jumps, collisions, obstacles, and collectibles.

Outcome

• The monolithic prototype became a maintainable modular codebase
• Gameplay and collision/interaction logic run on Canvas 2D
• Controls support both mobile gestures and keyboard input