Start paths
Which environment do you build in? Each environment has a start page with the same order: installation, a first connection, what differs there, build guides, examples, and what to do when stuck. Shared concepts such as tags and delivery types are in core concepts in five minutes.
| Developer | First success | Start page |
|---|---|---|
| Arduino (C/C++) | A D1 mini or ESP32-C3 board and the web exchange signals on one channel | Get started with Arduino |
| Web front end | The same message appears in two browser tabs | Get started in the browser |
| Node.js | A receiver in a terminal gets the sender's message | Get started with Node.js |
| Games | Two windows play one quiz, and a forged scoreboard is dropped | Get started with games |
| Server operations | Two clients exchange messages through your own server | Get started with a server |
If you have not decided yet, send any tag in the web lab without installing anything. The five-minute quickstart is the shortest way to see the principle in a few lines of code.
Browser chat
Open the single HTML file from Get started in the browser in two tabs and send a message on room#chat from one. When it appears in the other tab, it works.
Connect an Arduino board
After library installation, upload D1 mini and ESP32-C3 channel messaging and enter Wi-Fi. When signals go between the board and the web or CLI on the same router on one channel, it works. Continue with Get started with Arduino.
Run your own server
Start a server with Run a server and check delivery with the receiver and sender of the five-minute quickstart. Other devices and opening it to the internet continue in Get started with a server.
Build a game the server judges
Run the Host Quiz example with npm ci and npm start, and open http://localhost:5181 in two windows. When the scoreboards change together and the example's cheating panel shows forgeries being dropped, it works. Continue with Get started with games.
Stuck? Go through install and run diagnosis, connection diagnosis, delivery diagnosis and device diagnosis in order.