objectui

What Object UI is and where it sits

Object UI is the view layer of the ObjectStack ecosystem. The README describes it as a standalone, schema driven renderer that turns a JSON schema, or ObjectStack metadata, into production grade React user interface. You can use it on its own with any backend, in the same way you might use a tool such as Amis or Formily, or you can let it render ObjectStack applications end to end. The README lays out three roles in the wider project. Describe maps to ObjectStack, which is the open source protocol, toolkit, and production runtime. Render maps to Object UI, which is this repository and handles JSON or metadata to React UI. Operate maps to ObjectOS, which is the commercial runtime environment for cloud and enterprise use. The schema driven approach is what the README says makes the UI AI writable. An agent that would otherwise hand write React across many screens can instead emit and refactor compact schemas, and every screen stays consistent by construction. That property matters when a single agent generates a large number of views, because the schema acts as one shared contract between the agent and the renderer. The README presents the engine as the render step in a three part flow alongside ObjectStack and the commercial ObjectOS runtime.

What the renderer can draw

The project's short description lists the kinds of interfaces Object UI can render from a schema. These include grids, kanban boards, dashboards, Gantt charts, and visual designers. The README shows a hero screenshot where a kanban JSON schema on the left renders into a live kanban view on the right, which illustrates the core loop of writing schema and seeing a working component. Because the rendering is driven by JSON rather than hand written components, the same schema can be reused and edited by an agent without touching React source. The README points to a documentation site at objectui.org, a Quick Start section, a Changelog file, and a Roadmap file as places to learn more. The badge set in the README advertises TypeScript 5.0 or newer, React 18 or newer, and Tailwind CSS 3.0 or newer, which tells you the runtime expectations before you adopt it. The project also shows continuous integration and CodeQL security scan badges, which signal that builds and security checks run on each change. For a team evaluating the engine, the combination of a schema contract and a fixed component set is the main selling point. The hero screenshot pairs a kanban schema with its rendered board to show the schema to UI loop in one view.

How the schema driven model helps agents

The README explains that schema driven rendering is what makes the UI writable by an AI agent. The reasoning is practical. An agent that must hand write React across fifty screens faces a large and error prone task. If that same agent instead emits compact schemas, it can create and refactor many screens while keeping them consistent by construction. The schema is small and structured, so the agent can reason about it more easily than about a pile of component code. Object UI then renders that schema into real React, so the human sees a working interface without writing the view layer by hand. This also helps when a screen needs to change, because editing a schema is a smaller operation than rewriting a component tree. The README frames Object UI as usable either standalone with any backend or as the renderer for full ObjectStack applications. That flexibility means a team can adopt it gradually, starting with one schema driven view and expanding as needed. The documentation and Quick Start are the entry points the project provides for learning the schema format and connecting a backend. By editing schema instead of components, an agent keeps every screen aligned with the same contract.

Editorial conclusion

Object UI is written in TypeScript and released under the MIT license, and it targets React 18 or newer with Tailwind CSS 3.0 or newer as shown by the badges in its README.