<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: NgxViewBuilder</title>
    <description>The latest articles on DEV Community by NgxViewBuilder (@ngx_vb_5a114606ff9222c26a).</description>
    <link>https://dev.to/ngx_vb_5a114606ff9222c26a</link>
    <image>
      <url>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%2F4042115%2Fed29e1c6-03a4-405b-afc1-adcf8dd91a5f.png</url>
      <title>DEV Community: NgxViewBuilder</title>
      <link>https://dev.to/ngx_vb_5a114606ff9222c26a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ngx_vb_5a114606ff9222c26a"/>
    <language>en</language>
    <item>
      <title>An AI agent builds an Angular form over MCP</title>
      <dc:creator>NgxViewBuilder</dc:creator>
      <pubDate>Tue, 03 Nov 2026 18:45:20 +0000</pubDate>
      <link>https://dev.to/ngx_vb_5a114606ff9222c26a/an-ai-agent-builds-an-angular-form-over-mcp-p23</link>
      <guid>https://dev.to/ngx_vb_5a114606ff9222c26a/an-ai-agent-builds-an-angular-form-over-mcp-p23</guid>
      <description>&lt;p&gt;I connected an AI agent to NGX View Builder over MCP and gave it four short prompts. It built a form, changed a validation rule, added conditional logic and translated everything to Japan, while the canvas updated live.&lt;/p&gt;

&lt;p&gt;Try it on the demo: &lt;a href="https://demo.ngxviewbuilder.io/builder" rel="noopener noreferrer"&gt;demo.ngxviewbuilder.io/builder&lt;/a&gt;&lt;br&gt;
Docs: &lt;a href="https://ngxviewbuilder.io" rel="noopener noreferrer"&gt;ngxviewbuilder.io&lt;/a&gt;&lt;/p&gt;

</description>
      <category>angular</category>
      <category>ai</category>
      <category>mcp</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What if forms and screens lived in your database?</title>
      <dc:creator>NgxViewBuilder</dc:creator>
      <pubDate>Tue, 03 Nov 2026 13:14:24 +0000</pubDate>
      <link>https://dev.to/ngx_vb_5a114606ff9222c26a/what-if-forms-and-screens-lived-in-your-database-4pja</link>
      <guid>https://dev.to/ngx_vb_5a114606ff9222c26a/what-if-forms-and-screens-lived-in-your-database-4pja</guid>
      <description>&lt;p&gt;You build a form. A week later, someone needs another field. Then a different customer wants that field hidden. Then comes a calculation, an extra step, and a slightly different version for another team.&lt;br&gt;
Nothing particularly difficult. But someone still has to change the frontend, test it, and ship it.&lt;br&gt;
I keep thinking about how much of this actually needs to be hardcoded.&lt;br&gt;
What if an application loaded its forms and screens from JSON stored in a database? Fields, layout, validation, conditional visibility, calculated values. Your frontend components would still render everything, but the definition of each screen would be data.&lt;br&gt;
You could change a form without deploying the frontend. Different customers could have different versions of the same screen without adding more conditions to the component.&lt;br&gt;
Of course, you would still be shipping a change to users. Saving it in a database doesn’t remove the need for testing, permissions, versioning, or rollback.&lt;br&gt;
And once your JSON contains expressions, events, and conditions, have you just invented another programming language?&lt;br&gt;
That’s the part I find interesting. Where should configuration end and code begin?&lt;br&gt;
My current approach is to keep authentication, backend logic, and custom components in code, while letting the screen definition control layout and behavior within those boundaries.&lt;br&gt;
I’m building NGX View Builder around this idea for Angular, so I’m definitely biased. But I’d like to hear from people who have tried something similar, especially in applications with lots of forms or customer-specific workflows.&lt;br&gt;
Did it make changes easier? Or did maintaining the configuration eventually become harder than maintaining the code?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>discuss</category>
      <category>architecture</category>
      <category>angular</category>
    </item>
    <item>
      <title>NGX View Builder 1.0: build Angular screens visually, or let your AI do it</title>
      <dc:creator>NgxViewBuilder</dc:creator>
      <pubDate>Mon, 02 Nov 2026 08:28:15 +0000</pubDate>
      <link>https://dev.to/ngx_vb_5a114606ff9222c26a/ngx-view-builder-10-build-angular-screens-visually-or-let-your-ai-do-it-59g0</link>
      <guid>https://dev.to/ngx_vb_5a114606ff9222c26a/ngx-view-builder-10-build-angular-screens-visually-or-let-your-ai-do-it-59g0</guid>
      <description>&lt;p&gt;After a long beta, NGX View Builder 1.0 is out.&lt;/p&gt;

&lt;p&gt;It's a visual builder for Angular. You put forms, tables and dashboards together in the browser, the result is saved as JSON, and a runtime renders it in your app with signals. Changing a screen means changing JSON, not shipping a new build.&lt;/p&gt;

&lt;p&gt;What you get:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;drag and drop builder with rules like "show this field when that one is ticked"&lt;/li&gt;
&lt;li&gt;data sources, so screens can load and send real data&lt;/li&gt;
&lt;li&gt;an MCP server, so Claude, Codex or another AI assistant can build screens in the editor while you watch&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I made it because I got tired of writing the same admin screens by hand.&lt;/p&gt;

&lt;p&gt;Live demo: &lt;a href="https://ngxviewbuilder.io" rel="noopener noreferrer"&gt;https://ngxviewbuilder.io&lt;/a&gt;&lt;br&gt;
Short video: &lt;a href="https://youtu.be/-Qox3psSiMs" rel="noopener noreferrer"&gt;https://youtu.be/-Qox3psSiMs&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The runtime is free, the builder is paid. Feedback is very welcome, especially on what feels confusing.&lt;/p&gt;

</description>
      <category>angular</category>
      <category>showdev</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Building a JSON-driven UI Builder for Angular</title>
      <dc:creator>NgxViewBuilder</dc:creator>
      <pubDate>Wed, 05 Aug 2026 18:47:08 +0000</pubDate>
      <link>https://dev.to/ngx_vb_5a114606ff9222c26a/building-a-json-driven-ui-builder-for-angular-2hk4</link>
      <guid>https://dev.to/ngx_vb_5a114606ff9222c26a/building-a-json-driven-ui-builder-for-angular-2hk4</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fooqltimidj853ika8pf1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fooqltimidj853ika8pf1.png" alt=" " width="800" height="366"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After 2.5 years of building in my free time, I'm excited to share the beta of NGX View Builder.&lt;/p&gt;

&lt;p&gt;The idea started while working on a project that needed dynamic JSON based forms with a drag and drop editor. We ended up using an existing solution, but the experience made me wonder if I could build something similar with a different approach.&lt;/p&gt;

&lt;p&gt;Since early 2024, I've been working on NGX View Builder after work and on weekends. I rewrote it three times before arriving at an architecture I was happy with.&lt;/p&gt;

&lt;p&gt;The goal isn't just another form builder. I wanted to create a flexible way to build and manage Angular application views using JSON, while making it easy to extend with custom components, plugins, themes, and integrations.&lt;/p&gt;

&lt;p&gt;The project is now available in beta, and I'd really appreciate any feedback or suggestions from the Angular community.&lt;/p&gt;

&lt;p&gt;🔗 &lt;a href="https://ngxviewbuilder.io/" rel="noopener noreferrer"&gt;https://ngxviewbuilder.io/&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  angular #typescript #webdev #lowcode
&lt;/h1&gt;

</description>
    </item>
    <item>
      <title>After 2.5 years of nights and weekends, I finally shipped my Angular view builder</title>
      <dc:creator>NgxViewBuilder</dc:creator>
      <pubDate>Wed, 22 Jul 2026 14:10:45 +0000</pubDate>
      <link>https://dev.to/ngx_vb_5a114606ff9222c26a/after-25-years-of-nights-and-weekends-i-finally-shipped-my-angular-view-builder-2gj9</link>
      <guid>https://dev.to/ngx_vb_5a114606ff9222c26a/after-25-years-of-nights-and-weekends-i-finally-shipped-my-angular-view-builder-2gj9</guid>
      <description>&lt;p&gt;I started building this on January 21st, 2024. After work, weekends, holidays whatever free time I could find. Two and a half years later, I finally decided to ship it as a beta.&lt;/p&gt;

&lt;p&gt;The idea is simple you drag components onto a canvas, watch the JSON update live, and what gets rendered isn't some black box abstraction it's real Angular components. The exact same ones that run at runtime. No wrappers, no half broken layer sitting on top of your component model.&lt;/p&gt;

&lt;p&gt;Since it's a beta, there are almost certainly bugs I haven't caught myself. So I'd genuinely appreciate it if you gave it a try and told me what you think what works, what doesn't, what's missing.&lt;/p&gt;

&lt;p&gt;A couple of technical notes if you're curious the landing page is built with VitePress. The documentation I wrote with some AI help not out of laziness, but because good docs need clear, fluent writing, and that's not my strongest suit.&lt;/p&gt;

&lt;p&gt;Thanks in advance to anyone who takes a few minutes to check it out. 🙏&lt;/p&gt;

&lt;p&gt;Link: &lt;a href="https://ngxviewbuilder.io" rel="noopener noreferrer"&gt;https://ngxviewbuilder.io&lt;/a&gt;&lt;/p&gt;

</description>
      <category>angular</category>
      <category>lowcode</category>
      <category>showdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
