Atlas · DS256 · Future / AI: Architecture

Model-Driven UI

Generation of forms, states and components from data models.

• Status in 2026: Emerging. Appearing in practice, not yet settled.
• Trend 2027 to 2030: Rising (an editorial projection, not a forecast).
• The term: Known technical term or standard.

Definition

Generation of forms, states and components from data models.

Traits

• schemas
• forms
• rules

Typical settings: ERP, Internal platforms.

When to use it, and when not

Consider it when the task and motivation match: vertical application engineers. Typical settings: erp, internal platforms.

Be careful when the risk below would hurt the main task: generated UI becomes generic and inflexible.

UX risk and how to reduce it

Risk: Generated UI becomes generic and inflexible.

Mitigation and accessibility: Overrides and testing with users.

How to check: Test with realistic scenarios: task success, accuracy, reversal, auditability, understanding of what the system does on its own, and a human's ability to step in.

Evidence

Emerging: exploratory work, with no causal validation for this style.

The sources below support the principles that apply to this term. None of them shows that this style works better or is preferred.

• Aljabri 2026 (Supported): Adaptive UI generated with AI and model-driven development.
• Romero 2026 (Preliminary): UX of AI-generated prototypes.

Heuristic scales

Relative editorial judgements from 1 to 5. They are not results of a study and not a measure of quality.

Visual complexity heuristic

2 / 5 (1 is few visual elements, 5 is many layered elements)

Expressiveness heuristic

2 / 5 (1 is restrained, neutral, 5 is highly expressive)

Information density heuristic

5 / 5 (1 is sparse, 5 is dense)

In our library

No design-style recipe in @codeatlasdev/ui implements this term yet. You can still build it from the --ca-* tokens: see Theming.

Prompt for your AI

Paste this into a coding agent. It carries the trade-offs, and asks for a baseline to compare against.

Design this interface in the "Model-Driven UI" direction (future / ai, architecture): Generation of forms, states and components from data models.
Visual and interaction traits to use: schemas, forms, rules.
Main UX risk: Generated UI becomes generic and inflexible. Mitigate it: Overrides and testing with users.
Keep it accessible to WCAG 2.2 AA: contrast, visible focus, keyboard operation, 24 px minimum targets, reflow at 320 CSS px and reduced motion.
Keep the content, hierarchy and behavior the same as a plain baseline so the two can be compared. Do not claim the style performs better; the choice should be validated with users.