FOR WEB DEVELOPERS

One file. The same pixels everywhere.

One WebAssembly file draws your whole interface, frame for frame the same as Aster's desktop build, and it imports nothing from your page.

Two line charts and a bar chart, drawn by Aster.Drawn by Aster

Check the claims

Every number here names where it came from.

The same picture, every frame

Aster's web build and its desktop build draw identical frames, and we compare a fingerprint of every one. This compares Aster with itself, not with a browser's own drawing.

976 of 976 frames identical: Aster's native build vs its WebAssembly build, run under Node.

One download, nothing else

The renderer, the controls and the fonts come in one file. It needs no JavaScript glue.

About 2.6 MB brotli over the wire.

No special headers

A 2D canvas is enough. There's a plain build for engines without SIMD.

No WebGL, no WebGPU, no cross-origin isolation.

Quiet when nothing moves

The module reports which rectangles changed, so a browser host can present just those.

One scripted step of the night-sky scene: about 0.2 ms (WebAssembly under Node).

How your code talks to it

  • In the browser, your script calls the module with plain numbers and reads finished frames straight from its memory.
  • Today a browser app is written in Rust and compiled into the module.
  • The same file runs in Node with no browser, so a test can render a frame and compare it with ours.
  • For desktop apps, one Node package drives the native runtime: describe the screen as data, get events back.

That package runs in Node, not in the browser.

The Northwind dashboard in its tablet layout, drawn by Aster.Drawn by Aster

Example scenarios (illustrative)

Read 2 short examples

Golden images that agree

A team renders its screens in Node in CI and in the page in the browser. One golden image serves both, because the frames match.

Animation you can replay

A team steps the clock itself and saves every frame. The same steps give the same frames, ready for a video or a test.

Good to know

  • Mouse, wheel and keyboard only for now. No touch or pinch, and text arrives already composed.
  • There's no JavaScript or JSON way to build screens in the browser. You write the screen in Rust.
4 more to know
  • Some browsers interpret WebAssembly instead of compiling it. There, the first picture can take seconds. Show a still first.
  • Memory grows with the size of what it draws. Budget for it on phones.
  • Aster is before 1.0, so names can change.
  • Screen readers and the web: see Accessibility.