Rendering is an architectural choice
Skia supplies cross-platform 2D graphics capabilities, and CanvasKit exposes Skia through WebAssembly. These building blocks help explain the opportunity for faithful presentation in a browser-delivered experience. They do not by themselves define remote execution security or application compatibility. Skia graphics architecture ↗CanvasKit and WebAssembly ↗
Test the work people actually do
A fast-loading demonstration page can conceal problems in a spreadsheet editor, an international input method, a keyboard-only workflow, or a multi-tab identity redirect. Evaluate a complete task and its data policies: copying approved text, blocking a prohibited download, printing a permitted document, and recovering a disconnected session.
Network Vector Rendering changes the presentation path. It does not repeal network propagation time. Separate local input feedback from a remote application response, and measure the tail of the interaction distribution under realistic jitter and loss. That is how an experience claim becomes an operational decision.
Build an experience contract
- Define representative tasks and the completion criteria.
- Test text, fonts, zoom, accessibility, keyboard, and IME behavior.
- Measure interaction latency by region and network condition.
- Apply upload, download, and clipboard policies during the same tasks.
- Correlate session issues with rendering, transport, and origin evidence.
Our RBI white paper connects these experience requirements to the NVR/Skia rendering path and the agentic auditor’s investigation context.