push.tt / Enterprise
In beta

The phone you issued should do the job you issued it for

Company handsets, locked to their purpose. Suspend WhatsApp, the browser, social media and every app nobody needs on a work device — or replace the home screen entirely and leave one app on it. Enrol once; the fleet stays that way.

In beta. Android is built and in beta, on company-owned handsets enrolled as Device Owner. iOS is not built. The engineering detail, the platform limits and what is still missing are set out in full on the device management page — this page is the short version.

What comes off the handset

You author the list in the console. The handset applies it and reports back what it actually managed to apply — so a device that could not comply says so, rather than appearing in a green column while an advert plays on it.

  • Consumer messaging. WhatsApp, Telegram, Messenger. The icon goes, the app will not launch, and it stays that way across reboots
  • The browser. Suspend Chrome and the OEM browser and the open internet is off the device — or keep one and block the others
  • Social media and games. Same mechanism, whatever your list is
  • The bloat that has no uninstall button. Theme stores, game centres and the advertising apps preloaded on cheap rugged hardware, which are usually the ones a fleet complains about most because nothing else can shift them
  • Everything, if you want. Kiosk mode replaces the launcher: one home screen, the apps you placed on it, nothing else reachable

Who this is for

The common thread is that somebody else owns the phone and it was bought to do one job. If the handset is a personal device, this is the wrong product for it and the section below says so plainly.

  • Fleets of shared handsets that pass between shifts and come back needing to be in the same state they left in
  • Field and site crews on rugged hardware, where the preloaded OEM apps are the problem rather than anything the crew installed
  • Anywhere the phone is equipment — a scanner, a radio, a terminal — and a second use for it is a distraction, a data bill, or a support call

Before you buy: two limits worth knowing

Both are Android's, not ours, and both are easier to hear now than after a purchase order. The full version of this reasoning is on the device management page.

  • It needs a company-owned device. Locking a handset down means holding Device Owner, which is granted only during setup on a factory-reset phone. A personal device enrolled as BYOD gets a work profile instead: push.tt controls what is inside that profile and cannot touch WhatsApp in somebody's personal space — which is the correct behaviour, and worth being certain about before you plan a rollout
  • This is not staff monitoring. Deciding which apps run on a company phone says nothing about reading what anybody types in them. push.tt refuses a fixed list of policy keys outright, so device management cannot be turned into message interception by an administrator who fancies trying

And the radio is already in it

Device management here is not a separate product bolted to a PTT app — it is the same platform. The console that locks the handset down is the console that runs the channels, the fleet map and the dispatch queue, so a handset gets its policy and its radio from one place and one bill.

  • Push apps and updates to the fleet, including push.tt itself, verified by hash before anything installs
  • Place the home screen: which apps, in which cells, on every handset
  • Wipe a device that walks out of the depot
  • The engineering detail, the iOS position and the open gaps are all on the device management page