Platforms

The same game code builds for every platform. You don't write platform code: the engine owns the window, the GPU, input, audio, files and threads on each one, and your game is the same three functions everywhere.

PlatformBuild withGPUNotes
macOShz/hzbuild macosMetal
Windowshz/hzbuild windowsD3D12--vulkan for Vulkan
Linuxhz/hzbuild linuxVulkanWayland or X11
Webhz/hzbuild wasmWebGPUany browser with WebGPU
iOShz/hzbuild iosMetalruns on a connected device
Androidhz/hzbuild androidVulkanphones, Quest, Pico; Windows hosts
PC VRhz/hzbuild run --xrOpenXR, Windows and Linux

Your own machine's platform is the default, so most of the time it's just hz/hzbuild run.

The web

The web build runs the real engine: same renderer, same threads, same physics, compiled to WebAssembly and drawing with WebGPU. hz/hzbuild wasm run serves it to your browser.

Phones get a single-threaded build (hz/hzbuild wasm ios). Publishing makes both, and the page picks the right one for each player. If your game uses lanes the way these docs describe, it runs on both without changes.

Phones

Kaigen games run natively on iOS and Android, or in the mobile browser. Things to plan for:

Worth knowing