Service

UI components in Vue — accessible, fast, no reinventing the wheel

I build complex components you won't find in off-the-shelf libraries: virtualization, schema-driven forms, a command palette. They work from the keyboard, don't slow the app down, and don't need fixing up afterward.

Discuss components What's included

Who it's for

When off-the-shelf
isn't enough.

Подходит

You need a complex component that no ready-made library offers
Your current components are slow or not keyboard-accessible
You want a unified design system with tokens
You need Storybook with documentation for the team

Не подходит

You need a basic component — Vuetify or Headless UI will handle it
Your stack isn't Vue 3
There are no design references or requirements yet — start with an interface audit

01 — When it fits

Off-the-shelf libraries didn't fit?

Virtualization, schema-driven forms, notifications, a command palette — this is my public open source. You can read the code before you hire me.

You need a complex component that Vuetify, Ant, or Headless UI don't offer.

Every section has its own buttons and its own colors — it's time to bring order.

Components are slow or not keyboard-accessible — and fixing them costs more than rewriting.

The team is stuck on the UI part — you need reinforcement on a complex piece.

02 — What's included

From component
to design system.

I build individual complex components or put together a whole system — accessible, typed, and fast.

Complex components

List virtualization, schema-driven forms, a command palette, notifications — what you won't find out of the box.

virtualformsa11y

Design system

A single set of tokens and components instead of disjointed solutions in every section.

tokensDSStorybook

Accessibility

Keyboard, screen readers, contrast — WCAG 2.1 AA as the baseline by default.

WCAGkeyboardARIA

Performance

Lightweight, fast components with no extra dependencies or re-renders.

perfbundle

03 — What you get

Components that
save you time.

A reusable base that speeds up development and makes the interface consistent.

01
A consistent interface
One set of components — the same behavior and look in every section.
02
Accessibility out of the box
Work with the keyboard and screen readers — no fixing up afterward.
03
Faster development
The team assembles screens from ready-made blocks instead of reinventing them each time.
04
Documentation and examples
Storybook or an equivalent: how to use a component is clear at a glance.

04 — How the work goes

Discussed, built, delivered.
In iterations.

We talk

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

~ 1 hr

I estimate

Timeline, scope, risks, and cost — before we start.

1–2 days

I work in iterations

Regular demos and clear progress at every step.

from 1 week

I deliver with the code

I hand over the code and documentation. The project stays yours.

~ 1 hr

05 — Why me

Open source —
direct proof.

✓
Packages on exactly this topic. Virtualization, schema-driven forms, notifications, a command palette — all published on npm.
✓
Accessibility, not just talk. a11y is part of the work by default, not a paid add-on.
✓
A design foundation. I understand both the engineering and the visual side of a component at once.
✓
Clean, typed code. Components that are a pleasure to reuse and extend.

06 — Вопросы

FAQ

Yes. A common request is to build one specific complex component: a virtualized table, an editor, a command palette. A design system comes into play when you need scale.

Accessibility is built in by default: keyboard support, correct ARIA attributes, contrast. The benchmark is WCAG 2.1 AA.

Yes. I can work within your existing system and tokens, or help bring order to it if it's grown organically and gotten messy.

Yes — Storybook or an equivalent with live examples, so the team can use the components without asking questions.

Open code