A schema-driven Angular library — proof of how we cut repetitive work without cutting quality. Declare a form as data; the renderer produces the Material UI, validation, and accessibility for every field.
Every enterprise Angular app rebuilds the same forms by hand — controls, validation, error messages, layout, and accessibility — for each screen. It's repetitive, inconsistent across teams, and expensive to change.
A form is defined as data — fields, types, and validators. The renderer turns that into consistent Material UI with validation messages and accessibility built in. Change behavior in one place, not per form.
A representative nine-field project-inquiry form (text, email, phone, dropdowns, textarea, checkbox — with validation), built both ways:
Across roughly ten forms in a real application, that's about a thousand
fewer lines to write and maintain — and one place to fix a validation rule
instead of ten. The comparison is reproducible; the numbers come from
building the same form both ways. Shipping today as
@aventis-innovations/form-generator on npm (v0.2.0), with the
data-grid features split into an optional /grid entry point so
form-only apps don't bundle ag-grid.
We build internal platforms and customer portals where forms like these are everywhere. Tell us about your project →