Live demo

The demo runs the SDK’s own browser build — the same wasm module the WebAssembly package ships — drawing rendered map imagery on a WebGPU canvas with pan, zoom, bearing and pitch controls, in-page overlays, and offline routing over a compiled archive. It is static, keyless and served from this site’s /demo path.

What the demo needs in a browser

• WebGPU. Chromium-based browsers support it flag-free since 113; Safari ships it from version 26; Firefox ships it since 141, with desktop first. MDN’s WebGPU page carries the live compatibility table.
• A secure context. The browser resolves WebGPU only over HTTPS or localhost.
• Keyless by default. The demo renders recorded fixture imagery and answers routes over a committed archive. The Provider credentials panel can take a provider key at runtime for live geocoding, routing and tile probes (MapQuest today; the provider registry is designed for more); the key stays in the page’s memory and is never persisted.

Running the same loop locally

Every tutorial in the Guides group ships a WebAssembly tab with the same surface the demo shows, so you can run the stack yourself from the wasm package: install it once and the Your first map tutorial covers the whole loop. The browser harness the demo is built from — and the fixture routes it serves — is described in How the demo loop runs.