GolemUI: A Declarative JSON-Driven Form Engine

GolemUI is an open-source declarative form engine designed to generate dynamic user interfaces from JSON definitions. By decoupling the form structure from the rendering logic, GolemUI allows developers to store, version, and generate form schemas in databases or via Large Language Models (LLMs) while maintaining a consistent UI across different frontend frameworks.

Core Architecture and Features

GolemUI utilizes a JSON-driven approach to form generation, which enables the form's state and structure to be governed by a data definition rather than hard-coded components.

JSON Engine and Cross-Framework Support

The core engine processes JSON definitions to render UI components. This architecture allows a single form definition to be rendered across multiple environments, including:

• React
• Angular
• Vue
• Lit
• Vanilla JavaScript

Headless Components and Styling

GolemUI provides 28 headless components that can be styled using CSS variables. To ensure flexibility, the library provides APIs that allow developers to integrate third-party component libraries such as Material UI, Shoelace, or custom-built components.

Typed Authoring Layer

To avoid the manual effort of writing raw JSON, GolemUI includes a typed authoring layer. This programmatic interface allows developers to build forms using a typed API that then generates the underlying JSON definition, improving the developer experience (DX) and reducing syntax errors.

LLM Integration via MCP

GolemUI includes a deterministic Model Context Protocol (MCP) implementation. This toolset is designed to help LLMs generate valid JSON form definitions and code, providing validation tools to ensure that the output returned by the AI is compliant with the engine's schema.

Community Feedback and Technical Considerations

Following its release, the GolemUI community has raised several technical questions and concerns regarding the implementation and long-term maintenance of the library.

Type Safety and Field Relationships

Some users have noted that field relationships within the JSON definitions are expressed as strings. This has led to concerns regarding the lack of build-time syntax checking or auto-complete for these relationships, which could potentially complicate maintenance in larger forms.

Schema Evolution and Migrations

Questions have been raised regarding how GolemUI handles schema migrations. Specifically, for users storing thousands of JSON definitions in a database, the community has asked for clarification on whether a built-in versioning system or migration strategy exists to handle changes in the component API.

Comparison to Existing Solutions

Industry veterans have pointed out that the "data structures to forms" concept is not new, citing existing projects like JSONForms. This has led to a debate on whether GolemUI provides a unique enough value proposition to the market compared to established alternatives.

Reported Issues

Early adopters have reported specific functional bugs, such as the date range picker not functioning as expected and the absence of a file input type in the initial component set.

"All the field relationships seem to be expressed in strings. This suggests that you might not be able to use auto-complete or build-time syntax or type checking on them."

"How do you handle schema migrations? If someone has thousands of JSON JSON form definitions stored in a database and the component API changes, is there a migration strategy or versioning system built in?"