web dev//UI//schema-driven UI

A schema-driven UI is a GUI generated from metadata definitions rather than built from hand-coded components. A schema describes fields, types, validation rules and layout hints, and the runtime interprets it and renders the appropriate widgets.

A schema-driven UI is a GUI generated from metadata definitions rather than built from hand-coded components. A schema describes fields, types, validation rules and layout hints, and the runtime interprets it and renders the appropriate widgets.

The schema is the single source of truth: adding a field to the definition updates the form, the table and the API at once, and most such UIs generate their CRUD screens this way, the schema defining what they operate on. The approach trades per-screen polish for scalability, since one rendering engine serves hundreds of entity types, and it is common in CRMs (Salesforce), issue trackers (Jira) and low-code platforms (Retool, Airtable).

The spectrum runs from a config object that picks from a component library to a full DSL with conditionals and computed fields. When the schema grows expressive enough, configuring the UI has become programming in a DSL.