Playground / Runs in your browser
Build a widget in your browser
Write it here, watch it run, download the folder. Hardware sensors are simulated and the audio spectrum comes from a real analyser, so monitor and visualizer widgets actually do something. No install required.
1
1
Manifest check
These are the same rules Widgey applies every time a widget loads, not just at publish time. Passing here means it will appear in the catalog.
Preview
Sized from the same 240×180 grid cell the dashboard uses, so this is the real shape your widget will be.
Hardware sensors
feeding simulated values
These numbers are invented. A web page can't read your CPU temperature, so the playground generates a bounded random walk. Values arrive as integer strings, exactly as the real bridge returns them.
Audio spectrum
silent, so getBands() returns zeros
This part is real. A loop is synthesized with Web Audio and run through
an actual analyser, so getBands() returns genuine FFT output. Same 64
log-spaced bands the app provides. Nothing is uploaded; a file you choose stays in your browser.
Saved settings
nothing stored yet
Whatever your widget writes with widgey.settings.set() shows up
here, and persists across reloads, the same way it would per-widget in the app.
Console
Errors and console.log from inside the widget, so you don't need
devtools open to see why something is blank.
networkHosts, and everything else gets a 403. Test
that in the app before publishing. Widgets are also sandboxed differently: here the preview is an
iframe, in Widgey it's a WebView2 container with its own isolated profile.
Read the permission model.
Ready to run it for real?
Download the folder, drop it into %APPDATA%\WidgetDashboard\UserWidgets\, and Widgey
picks it up immediately, and reloads every time you save.