Frontend · Vue 3 / Nuxt / TypeScript

Vue · Nuxt · TypeScript — architecture you won't have to rewrite

I build and clean up applications on Vue 3 and Nuxt. I take on what's slow, falling apart, or built wrong. Performance from the first commit, an honest estimate before we start.

02 — Three ways to work together

Find yourself here —
and get straight to it.

Three typical situations. For each — what comes in, and what the client gets out.

01

The project is slow
or falling apart.

The project works — but every sprint it gets harder. Vue 2, Options API, Vuex, no TypeScript. The team is afraid to touch the code, CWV is red, the bundle is bloated. I start with an audit: find the real causes and set priorities. Then — iterative refactoring that doesn't stop production or rewrite everything from scratch.

What you have now
  • Vue 2, Options API, or an outdated Nuxt
  • Red CWV, a bloated bundle
  • Code that's scary to change
  • Tech debt slows down every new feature
What you get in the end
  • Vue 3 + Composition API + Pinia
  • TypeScript with real types
  • CWV in the green zone
  • An architecture the team understands
02

Building a new
product from scratch.

You have an idea or a design — you need an engineer who builds it right from the first commit. Not "launch now, figure it out later," but architecture built for growth, TypeScript, SSR where it's needed. I run the project from the first call to deployment: design, development, quality, launch. At the end — code, documentation, and a configured deployment. The project stays yours.

Where we start
  • An idea or ready-made Figma mockups
  • You need a stack, architecture, deployment
  • SSR and SEO matter from day one
  • No team, or you need an outside engineer
What we launch
  • A launched app on Vue 3 / Nuxt
  • Clean, typed code
  • A configured deployment and documentation
  • A foundation the team keeps building on
03

Need help
with a specific task.

You don't need a whole project — just one problem solved. An API with no contracts, chaotic UI, an SPA that Google won't index, a complex component that doesn't exist in any library. Each of these is its own service. I take on focused work, give an honest estimate, and don't push anything extra.

What hurts
  • An undocumented API with unstable contracts
  • Disjointed UI or missing components
  • An SPA that isn't indexed, rankings aren't growing
  • The team is stuck on one specific piece
What we fix
  • Predictable contracts and documentation
  • A component or design system
  • Visibility in Google, green CWV
  • The task closed without paying for extras
05 — How the work goes

We work step by step —
you see it all.

01

We talk

I look into the task and context for free. If it's not something I do, I'll say so honestly and won't take it on.

02

I estimate

Timeline, scope, risks, and cost — before we start, in writing. No vague wording and no price changes at the end.

03

I work in iterations

Regular demos and visible progress. You see what's happening at every step.

04

I deliver with the code

Code, documentation, deployment. The project stays yours and keeps evolving without me.

06 — How I work

Principles, not
promises.

Not because it's customary, but because expensive rewrites are a real story. Every principle shows up in the result: in speed, in clean code, in how easily the team develops the project after me.

Architecture

Architecture

A foundation that holds up under growth — not "just make it work by the deadline." It pays off with every following sprint.

Performance

Performance

Speed isn't "optimize it later." It's a requirement from the first commit. CWV green from day one.

Clean code

Clean code

Typed and understandable — so the team can develop the project without me and without fear of breaking something.

Minimal dependencies

Minimal dependencies

I don't drag in extras. Every dependency is a risk and a maintenance burden. I only take what's truly necessary.

20+years building interfaces
8years in the airline domain
17open-source packages
RU·ENmultilingual projects
07 — What clients say

Not my words —
theirs.

Заказал аудит — ожидал список из сотни пунктов. Получил чёткий приоритет: три критичных тормоза, которые мы поправили за две недели. Скорость выросла, а команда перестала гадать, с чего начать. Рентабельность вложений поняли сразу.

Алексей П.CTO, маркетплейс для путешественников

Строили SPA с нуля: Nuxt 3, сложные маршруты и роли. Опасались, что через полгода придётся переписывать. Архитектура получилась чёткой — наш джун разобрался за день. До этого сменили две команды.

Олег Н.Основатель, образовательная платформа

Три года копили техдолг на Vue 2. Мигрировали постепенно, без остановки продакшна. Главное: ни одного инцидента за всё время. А после перехода на Pinia и Composition API код стало реально читать.

Екатерина В.Lead Frontend, product-компания

Наш API был нестабильным и недокументированным. Данил спроектировал чёткие контракты и написал документацию. Теперь фронтенд перестал делать костыли, а время интеграции сократилось вдвое. BFF-слой убрал лишние запросы.

Марина К.Product Manager, fintech-стартап

Готовых таблиц не хватало. Заказал сложный компонент с виртуализацией, фильтрами и вложенными строками. Реализовал с нуля на TypeScript, с историей и документацией. Теперь это часть нашей дизайн-системы.

Дмитрий Л.Team Lead, B2B SaaS-платформа

SPA вообще не индексировалась. После аудита и внедрения SSR с мета-разметкой через три месяца мы вошли в топ-10 по ключевым запросам. Органический трафик вырос в 4 раза, а позиции перестали прыгать.

Наталья С.CMO, e-commerce проект
Next step

Have a task? Let's break it down for free.

Describe what's going on — I'll answer honestly: whether it's a fit for me, how long it'll take, and how much it'll cost. If it's not my thing, I'll say so directly and won't charge for the conversation. Work under NDA.

Discuss a project See case studiesI reply within one business day