Senior Front-End Engineer·Kyiv, Ukraine
Volodymyr Chornous
I turn product ambiguity into resilient React systems, sharp interaction models, and interfaces that feel expensive without becoming fragile.
Currently
Portfolio platform rebuild
Migrating the site to static Next.js, typed MDX, Pagefind, and interaction components that can survive real iteration.
Motion systems for product UI
Exploring restrained physics and spring motion patterns that clarify state instead of competing with content.
Drag the stack
ReactNext.jsTypeScriptDesign systemsMotionMDXPerformanceAccessibilityProduct architectureStatic searchBounded Matter.js field · reduced-motion safe
Featured project systems
Work organized around typed content, resilient UI contracts, and interaction patterns that can be reviewed instead of guessed.
Next.js portfolio system
A static-first personal site rebuilt around typed content, Pagefind, and interaction components that stay maintainable.
Motion interface lab
A compact interaction lab for testing spring states, route reveals, and physics-inspired UI without harming accessibility.
Writing for builders
Notes on React architecture, static content systems, and the craft details that keep product interfaces sharp.
React Native 0.85: animation backend changes deserve real QA
React Native 0.85 brings a new animation backend and Jest preset movement, which makes it a release for careful interaction testing.
Next.js adapters: the platform contract becomes explicit
Next.js 16.2's stable Adapter API and OpenNext collaboration make deployment behavior easier for platforms and teams to reason about.
Next.js 16.2 AI improvements: agents need observability, not magic
Next.js 16.2 adds agent-focused tooling that makes browser errors, project context, and diagnostics more available from the terminal.
Bring me into the part of the product where interface quality starts affecting velocity.
The contact path is intentionally static: no credentials, no backend dependency, no hidden form failure. Email is the primary route.