Web
The standalone web build path is functional and packages the WebAssembly and WebGPU runtime with the project's cooked assets.
ENGINE FEATURE
Native Export in Uverse
A Uverse native build is a compiled application running in a dedicated player, not a website packaged inside an embedded browser window.
Compiled Players, Not Embedded Browser Wrappers
Browser-first describes where a project is opened and authored. It does not restrict where the finished game runs. Uverse keeps the project format shared while producing target-specific build artifacts.
The native players use platform graphics backends and platform packaging rather than shipping the editor or relying on a hidden web view.
macOS, Windows, and Linux
The desktop targets produce dedicated native players through platform-specific build and graphics paths. Distribution, signing, packaging, and release polish continue around those implemented targets.
iOS and Android
The mobile targets are implemented build destinations with platform-specific renderer, architecture, signing, and store-delivery profiles.
One Workflow, Different Delivery Targets
A browser link is useful for immediate review, while native downloads are useful for platform-specific testing and distribution. Uverse is designed so those outcomes come from one project instead of separate hand-maintained copies.