The latest articles on DEV Community by Yuri Palienko (@yuri_palienko). https://dev.to/yuri_palienko https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4036527%2Fd3b6f3e8-4399-4c25-9453-c81cb9520198.jpg https://dev.to/yuri_palienko en Yuri Palienko Sun, 19 Jul 2026 12:52:16 +0000 https://dev.to/yuri_palienko/palistor-is-here-the-ai-friendly-mvvm-framework-for-react-experimental-5162 https://dev.to/yuri_palienko/palistor-is-here-the-ai-friendly-mvvm-framework-for-react-experimental-5162 <p><strong>Palistor just landed on npm.</strong> <code>npm install palistor</code> — and your React screens stop being a tangle of <code>useEffect</code>.</p> <blockquote> <p>⚠️ <strong>Heads up:</strong> Palistor is still an <em>experimental</em> technology. Kick the tires, break it, tell us what hurts.</p> </blockquote> <h2> The one idea </h2> <p>AI is bad at architecture — but it's <em>great</em> at filling declarative slots.</p> <p>So Palistor removes the architecture task entirely. It splits your frontend into three clean layers:</p> <ul> <li> <strong>View</strong> — pure JSX. So primitive there's nowhere to make a mistake.</li> <li> <strong>ViewModel</strong> — one flat config object with behavior (validation, conditional fields, cross-field rules).</li> <li> <strong>Model</strong> — any data source you plug in via <code>resolve</code>. Palistor defines the interface, not the implementation.</li> </ul> <h2> 🤖 Why it's AI-friendly </h2> <p>Here's the punchline: <strong>generated code can't fall apart, because there's nowhere for it to go wrong.</strong></p> <p>Reviewing an AI-written screen becomes reviewing <em>one flat object</em> instead of a tree of <code>useEffect</code>s, custom hooks and contexts. You keep control — even when you don't read every line the model wrote. That's the path toward generating real enterprise frontends without losing the plot.</p> <h2> What you get </h2> <ul> <li>⚡ <strong>Granular re-renders</strong> — a component subscribes only to the fields it read</li> <li>🧮 <strong>Computed field state</strong> — <code>isVisible</code>, <code>isRequired</code>, labels, errors recomputed from the config</li> <li>🔌 <strong>Async resolvers</strong> — auto-tracked deps, retry, optimistic updates, Suspense</li> <li>📋 <strong>Lists &amp; entities</strong> — normalized registry, list proxy, per-entity templates</li> <li>🪜 <strong>Flows</strong> — step wizards with branching and per-step validation</li> <li>💾 <strong>Persist, i18n, field mapping</strong> — batteries included </li> </ul> <div class="highlight js-code-highlight"> <pre class="highlight shell"><code>npm <span class="nb">install </span>palistor <span class="c"># peer: react ^19</span> </code></pre> </div> <p>Live playground with every example: <strong>projectint.github.io/palistor</strong><br> Source &amp; README: <strong>github.com/ProjectINT/palistor</strong></p> <p>Built by <strong>Yuri Palienko</strong>. MIT licensed.</p> <p>It's early, it's experimental, and it's fun. Go break it. 🔨</p> ai architecture react showdev