push.tt / Industries
Shipping now

Dispatch to driver, however far out they are

A radio stops at the edge of its coverage. A driver two states away is on the same channel as the yard, with no repeater in between and nothing to licence.

The current push.tt app running on a handset in a vehicle

No range limit, because there is no radio

Coverage is wherever there is cellular or Wi-Fi. Adding a depot is adding people to a channel, not installing hardware on a tower.

  • No tower leases, repeater maintenance or spectrum coordination
  • Voice frames are small and the client tolerates loss, so it holds up on a weak connection
  • A signal indicator warns the driver before they key the mic, not after

Built to be used without looking at it

The control is a ring roughly two thirds of the screen wide, because the person pressing it is driving, wearing gloves, or holding something else.

  • Every state is distinguishable at arm's length — transmitting, receiving, requesting, busy
  • Transmitting and receiving differ by hue and direction of travel, so they read apart without colour vision
  • A hardware push-to-talk button on a rugged handset works the same as the on-screen one

The part a scanner cannot do

Fleet radio traffic is clear in the air. Anyone within range with equipment costing less than a handset can listen to your dispatch, your routes and your customer names.

  • Private and org channels are encrypted on member devices; push.tt relays ciphertext
  • Load details, addresses and customer names are not broadcast to whoever is listening

Honest limit: v1 has no forward secrecy, so a channel key that is later compromised would open past traffic captured on that channel. It is on the roadmap and it is on the security page.

Put one route on it

One dispatcher and a handful of drivers is enough to tell.