MorphScreen vs others

Generative UI libraries share a goal: a model's answer that the reader can use, not just read. They differ in what the model writes, who checks it, and what happens when it's wrong.

#What MorphScreen does differently

• The model writes Markdown with a few tags. Models already write both, so the format needs a short prompt (about 1,400 tokens with the core components, 2,900 with every pack), and half an answer is always a valid start of the whole one. Nothing waits for a closing bracket or a root statement.
• Every line is checked as it streams. The core reads each line against the components your app allows, so what reaches your page is already validated, and a mistake is tied to the line it's on.
• Only broken lines are repaired. When a line breaks a rule, the API asks the same model to rewrite that line, not the whole answer.
• Any model. The model included in every plan, or any model on OpenRouter with your own key.
• Nothing a model wrote ever runs. No script, no style, no address you didn't allow (see Security).

#Against OpenUI, measured

We measure ourselves against OpenUI on the benchmark thesysdev publishes for it: the same 46 briefs, the same models and the same rules for what counts as valid. The benchmark page has the method, every raw answer and the rows where OpenUI is ahead with why; every row is on its own page.

#The others

Comparisons with the last three need runs of their own on the same briefs; they go on this page, with their raw answers, once we have them.