ABOUT UVERSE
Uverse brings the editor, play mode, and project workflow into the browser while keeping standalone web builds and compiled native players as first-class release targets.
Uverse is browser-first, not browser-only. Authoring happens in a browser-based editor, and the engine keeps scene data, runtime systems, and build targets aligned around one project rather than separate web and native projects.
The current implementation covers 2D, 3D, and hybrid scenes. Its engine systems include component-based scene data, rendering, materials, physics, animation, terrain, VFX, asset delivery, and diagnostics.
The same project data feeds browser play mode, standalone web builds, and dedicated native players. This reduces target-specific project drift while leaving room for each platform backend to do platform-specific work.
WebGPU gives the browser editor and web player a modern GPU API for compute and rendering work. Uverse uses that path directly rather than treating the browser as a remote control for a separate installed editor.
Native exports use dedicated players and platform graphics backends rather than embedded browser wrappers. Web, Windows, macOS, Linux, iOS, and Android are implemented targets while distribution polish continues.
Uverse is preparing for its first external developer alpha. C#, U#, and typed Visual Scripting are functional authoring options and continue to be refined.
Shared browser workspaces and hosted build links remain in development. Web, macOS, Windows, Linux, iOS, and Android are implemented delivery targets, while external-alpha packaging and distribution polish continue.