Demo Platform
Start with instant browser proofs, then move into hybrid SDK and hardware flows built on shared channels and canonical payload contracts.
Tracked demo experiences
Platforms in the gallery taxonomy
Payload types covered in the contract model
The fastest proof that Data Network works live in the browser.
A new user can connect in the browser, publish structured or plain-text payloads, and watch live events move instantly across tabs.
View demo details →A browser-native p5 sketch proves visual pub/sub without leaving the web app.
The same demo channel can drive a visual p5 surface in-browser, not just a text console, which makes the platform feel much closer to artist and installation workflows.
View demo details →Run DataNet from browser coding sandboxes like p5.js Web Editor, CodePen, and JSFiddle.
Creative coders and frontend developers can paste the hosted DataNet SDK into an online editor, configure a browser key for that editor's runtime preview origin, and subscribe or publish without a local server.
View demo details →Shows the same channel and payload contract working from a Node script into the browser.
A scriptable backend or utility runtime can publish the same canonical payloads that the browser demo receives without translation.
View demo details →Pairs scripting-friendly publishing with artist-friendly visualization.
Scalar telemetry from Python can drive a p5 sketch using the same sensor schema and channel naming that hardware demos will share.
View demo details →Creates one coherent creative-coding story across two familiar environments.
Processing and p5 can participate in the same visual workflow when they share one array-oriented scenario and channel contract.
View demo details →Any Arduino — even a classic Uno with no WiFi — can feed live sensor data to the browser via a USB serial bridge.
A non-networked Arduino (Uno, Mega, Nano, Leonardo) participates in DataNet flows when a local bridge script reads its USB serial output and publishes canonical telemetry. Three bridge paths are provided: Node.js, Python, and browser-native Web Serial API.
View demo details →WiFi-capable microcontrollers connect directly to DataNet — no bridge computer needed.
An ESP32 or ESP8266 can authenticate via HTTPS, open a secure WebSocket, and pub/sub canonical telemetry channels completely autonomously once flashed. This is the right path for standalone IoT devices and wireless installations.
View demo details →Proves remote fixture control by sending binary Art-Net or DMX frames through Data Network.
The platform can carry raw lighting-control payloads from a web or script publisher into a hardware or bridge receiver, which is one of the strongest demonstrations of remote control and binary transport in real installation workflows.
View demo details →Placeholder for a first-class TouchDesigner package, not just a one-off example.
This placeholder keeps the demo architecture honest about a future polished TouchDesigner integration with install docs, packaged components, and a canonical control workflow.
View demo details →Placeholder for a polished React integration that feels native to app teams.
This keeps React visible as a first-class framework path where canonical state payloads can drive UI updates, forms, and realtime view state without forcing teams down to raw browser snippets.
View demo details →Placeholder for a Vue-first integration that mirrors the core browser story in a familiar app framework.
This reserves a clean path for Vue teams to adopt Data Network with canonical payloads, lightweight composables, and demo-ready reactive state patterns.
View demo details →Placeholder for a mobile-native realtime app story built on shared channels.
This keeps React Native in the roadmap as the clearest way to show the platform moving from browser demos into handheld app experiences with the same payload contracts.
View demo details →Placeholder for a richer 3D browser surface driven by canonical realtime payloads.
This reserves room for a more spatial and visually compelling browser demo where scene state, positions, or sample trails are controlled over the same network the simpler demos already use.
View demo details →Placeholder for a first-class Apple-native integration path.
This keeps Swift visible as a future native app workflow so Data Network can be demonstrated outside the browser and JavaScript runtimes with the same structured payload story.
View demo details →Placeholder for an artist-facing openFrameworks integration.
This reserves an installation and creative-coding workflow where openFrameworks participates alongside browser and script demos using the same array and state contracts.
View demo details →Placeholder for a design-tool integration that turns live channels into fresh visual assets and synced layer state.
This keeps a Figma plugin experiment visible as a possible ecosystem and visibility play where selected layers, tokens, or visual properties respond to canonical state updates in realtime while the plugin session is active.
View demo details →TBD roadmap placeholder for driving Rive Web runtime state machines from Data Network channels.
This reserves a web-native motion demo where realtime channel state updates Rive inputs, animations, and interactive UI states using the official Web JS runtime.
View demo details →TBD roadmap placeholder for connecting Nodes visual patches to Data Network channels.
This keeps visual patching and generative browser graphics visible as first-class creative-coding workflows next to p5.js, Processing, Rive, and cables.gl.
View demo details →TBD roadmap placeholder for driving browser-native cables.gl patches from Data Network channels.
This reserves a strong WebGL and interactive-installation story where visual patch variables, triggers, and shader or scene parameters respond to shared realtime channels.
View demo details →TBD roadmap placeholder for a Blender Python addon or script that maps Data Network state into scene objects.
This keeps the content-pipeline side of realtime 3D visible, before assets move into Unity, Unreal, or browser runtimes.
View demo details →TBD roadmap placeholder for a Unity C# package that syncs scene objects and controller state through Data Network.
This reserves the installation, XR, and location-based entertainment path where Unity scenes consume the same channels as browser, hardware, and script demos.
View demo details →TBD roadmap placeholder for an Unreal plugin, Blueprint bridge, or C++ sample that syncs scene state through Data Network.
This keeps virtual production, high-end realtime 3D, broadcast, and enterprise XR visible in the demo roadmap.
View demo details →Placeholder for MIDI note and CC flows mapped onto canonical realtime channels.
This keeps MIDI visible as a future bridge layer for control-heavy installations and performance workflows.
View demo details →TBD roadmap placeholder for Ableton Live workflows, which need DAW-aware routing rather than only browser JavaScript MIDI.
This separates generic MIDI transport from Ableton-specific integration work: Max for Live devices, clip/session state, tempo, track routing, note events, and CC mapping.
View demo details →TBD roadmap placeholder for standalone Max/MSP patches, separate from Ableton-specific Max for Live workflows.
This keeps a core media-art and performance patching environment visible for OSC, MIDI, sensor, audio-reactive, and installation control flows.
View demo details →TBD roadmap placeholder for Pure Data patches and open-source sound-art installation workflows.
This reserves a lower-friction, open-source patching path for artists who use Pd for sound, sensors, control messages, and local installation glue.
View demo details →Placeholder for OSC-driven control and installation workflows.
This reserves room for OSC as a first-class bridge path so installations can translate between familiar control protocols and Data Network channels.
View demo details →