Developer documentation
One firmware, three modes, your backend
QuickComm devices are a microphone, a speaker, a button and a MAC address. They hold no business logic, which is exactly why the same hardware serves a restaurant, a guard force, a warehouse or a clinic — you point them at your own server and every decision after the audio arrives is yours.
This documentation is the complete contract between your systems and the device: every byte it sends, every response it expects, every timer it runs, and working code for all of it. There is no platform to sign up for and no API key to request.
Which device speaks which protocol
Mode A — push-to-talk streaming
Earpiece, Bridge NodeThe device streams 16 kHz PCM over UDP while the button is held. Uplink only, cheapest to run, kindest to a shared access point.
Mode B — request and response
Earpiece, Bridge NodeFramed PCM over HTTPS with a downlink queue the device drains. Works anywhere, including through a proxy that will not pass UDP.
Mode C — full-duplex agent
Table TopPCM both ways over one WebSocket, with JSON control frames, button barge-in and an optional ESC/POS print bridge.
Everything in here
Start here
What the hardware is, what it guarantees, and a path from nothing to a live transcript.
Device & fleet
Provisioning, heartbeat, telemetry, remote commands and over-the-air updates.
- Provisioning a deviceThe QR payload, what the device stores, and the reachability trap that eats fleets.8 min read
- Heartbeat, telemetry and commandsThe plane every device speaks regardless of mode. If you implement one endpoint, implement the heartbeat.10 min read
- Firmware updates and OTAChecking, verifying, reporting and staging firmware across a fleet.6 min read
Protocols
The three transports, byte for byte, plus the print bridge.
- Mode A — push-to-talk streamingThe udp-v1 wire format, the server-side voice gate, and how to parse it yourself.11 min read
- Mode B — request and responseFramed PCM over HTTPS, with a downlink queue the device drains.8 min read
- Mode C — full-duplex agentA real two-way conversation over one socket, and the four rules that keep it stable.13 min read
- The print bridgeRendered receipts, claimed and acknowledged, printed from inside the customer's network.7 min read
Integration
Three ways to build on it, including running the whole backend yourself.
- Integrating with your systemsThe system you build around the hardware, and where your logic actually plugs in.7 min read
- The minimum serverThe smallest server the firmware is happy with, with a reference implementation you can lift.12 min read
- Building your business logicEight verticals on identical hardware, and the five things you genuinely cannot change.9 min read
Operations
Running a fleet, the constraints to design around, and how to prove you are done.
- Running a fleetBandwidth, reconnect storms, bulk provisioning, and what to alert on.7 min read
- Limits and constraintsThe honest list of what will bite you. Better read here than in a customer's building.9 min read
- Acceptance testsTwenty-seven pass/fail tests, and the seven numbers to measure on your own hardware.6 min read
Reference
Every endpoint, field, enum, default and error code.
Something missing, or a constraint that blocks you?
The Limits and constraints page is the honest list of what will bite you, and several items on it are small pieces of work we would rather do once, properly, than have every integrator work around separately. Raise it before you flash a fleet, not after.
17 pages. Schematics, bill of materials and firmware source are not part of this documentation and are not needed to integrate.