Why forms are the new APIs

For decades, internal tools teams have reinvented the form. CRUD screens, onboarding wizards, approval workflows — all the same DOM primitives, welded together slightly differently each time.

Formfyl exists because there is a better abstraction hiding in plain sight: a JSON schema that describes every human-facing data pull, validated against a typed spec, rendered by a shared engine.

When forms become APIs, they get superpowers. Versioning. Diff-able schemas. Programmatic creation. And — most importantly — observability, which is the one thing mature APIs have that most forms still lack.