DUST Go demo
This page is itself a DUST Go integration. Open it inside DUST Go to scan with your device and see exactly what @dustid/dust-go-connect hands a web page. In any other browser the scanner controls stay disabled.
Open this page in DUST Go
This browser has no DUST Go bridge, so the scanner is unavailable. Install DUST Go, then open this page in the app to try a scan.
- Connector
- Not detected
- Host
- Unknown
- App
- Unknown
Last scan
No scan yet.
Capabilities
None reported
Event log
- No events yet.
What the demo shows
Section titled “What the demo shows”- Connector, Host, and App. Whether the bridge was detected, which host is running the page, and the DUST Go version and app id from the User-Agent.
- Last scan. The payload type and data. A DUST capture is shown as the image your backend would receive; its metadata is listed below it.
- Capabilities. The capture capabilities the host announced. “None reported” means the host has not announced any. That is not a statement about the hardware: until an announcement arrives, the connector falls back to single captures with nothing adjustable.
- Event log. Every connector event as it arrives, newest first. Long strings, such as the base64 image of a DUST capture, are shortened.
Scan once calls scanAsync(). Open scanner and Close scanner call connector.showScanner() and connector.hideScanner(); captures made while the scanner is open arrive as scan events.
The demo only displays what it receives. It does not send captures anywhere: resolving a capture against APID is your backend’s job (see Resolve the scan against APID).
Related
Section titled “Related”- Integrate with DUST Go — the integration walkthrough this demo exercises.
- DUST Go — download the app and check hardware requirements.
- Supported devices — the hardware DUST capture requires.
