Playground
A little Xu. An immediate result.
No installation. Runs on your device.
Pan mode: drag to explore; turn off to interact.
640 × 360
Run a UI example to display its canvas here.
Run a UI example
Choose a UI example from the project library, then use Run Code to view and try its controls.
Run your code. The result will appear here.
WebAssembly · On-device execution · 10s per program; 30s for Widgets examples
Start with the entry function and standard output. Edit the message and run again.
What can I run here?
On phones, switch between Files, Editor, Preview and Output without losing code or widget state. UI examples open Preview; ordinary programs open Output. Select a template to view its details, and use Back to retain your search. Fit shows the whole canvas; 100% with Pan lets you drag a large view. Disable Pan to interact with controls. Expand is also available on desktop.
Run basic types, strings, control flow, recursion, structs, enums, borrow diagnostics and cooperative chan communication. Xu source files in the root directory run together. Use folders to organize files; cross-directory imports require the local SDK. Learn about coroutines and chan.
All 46 component experiences execute editable Xu/WASM examples, alongside a three-page control gallery. ComboBox offers a candidate menu, MultiSelect toggles individual checkboxes, Popover saves or cancels preferences, Modal manages dialog focus, and ColorPicker supports channel dragging with color output. Some experiences use composed or bounded implementations; each template describes its scope. WebView is a placeholder, while native windows and system services require the SDK.
Examples keep a fixed XUUI theme while the preview panel follows the site theme. Focus uses one cinnabar boundary and control labels align vertically. Click controls, use Tab / Shift+Tab to move focus, Enter / Space to activate and arrows to adjust. Escape closes menus or overlays first, as handled by each control. Browser input uses bounded replay and text layout uses estimated metrics; native shaping, text selection, clipboard, IME and individual widget screen-reader semantics remain unavailable.
Reading documentation or opening the homepage does not preload WASM. Running code or opening an explicit example loads it on demand, so the first run can take longer; retry after a failed initialization. Linear memory starts at 32 MiB and can grow to 256 MiB. Ordinary programs have a 10-second execution budget; Widgets examples have 30 seconds. Stop is available while running. See the browser UI guide.