How the Runtime Works

Brewser runs as a homebrew application on a custom-firmware Nintendo Switch (via Atmosphère). It is not a port of an existing browser. It's a purpose-built web runtime, evolved from the nx.js project.

Launch flow

1. You open Brewser from the Homebrew Menu.
2. The catalogue loads from play.brewser.io.
3. Selecting an app fetches its bundle and boots it in a fresh, isolated JavaScript context.
4. The app renders through the GPU-accelerated graphics stack and gets access to input, audio, and any hardware APIs its manifest declares.

Each app runs in its own context. Leaving an app fully tears down its graphics state, audio nodes and event listeners, so apps can't leak into each other.

What this section covers

• Architecture: the engine stack under the hood
• Web platform support: which standards work
• Engine status: an HTML/CSS/DOM coverage map
• Graphics: Canvas 2D, WebGL 1 and WebGL 2
• Input & sensors: gamepad, touch, motion
• Hardware APIs: serial, Bluetooth, MIDI, NFC