Community

ivue is built in the open, extracted from production, and maintained by a real person who reads everything below.

Get help, talk shop

Each channel has a job — picking the right one gets you answered fastest:

GitHub

Source Code

Browse ivue, its tests, examples, and benchmarks.

Discussions

"Is this the right pattern?" questions, ideas, and show-and-tell.

Issues

Bugs and defects. A minimal reproduction turns a report into a fix.

Community

Discord

Live chat — quick questions, work-in-progress, and community help.

Socials

Follow on X

Updates from Evgeny: releases, benchmarks, examples, and new ideas.

Connect on LinkedIn

Professional background, writing, and work beyond ivue.

Feedback

The best feedback is public — others can +1 it, refine it, and watch it become a change:

If something in the docs is wrong, unclear, or missing — that's a bug too. Every page's source is available in the v2 docs on GitHub.

Start a GitHub discussion →Anonymous feedback form →

Follow the work

New releases, benchmark runs, and examples land on X and in GitHub Releases.

Who's behind ivue

Built from productionEvgeny KalashnikovLead Software Engineer @ Blackline, Adhoc Studio

XGitHubLinkedIn

ivue was not designed in theory. It was reduced out of a production application — where deep class graphs, fields, grids, and stores had to stay coherent under real load. The examples are descendants of that system. v2 carries the same conclusion in its smallest form: plain classes, full reactivity, one kilobyte.