It is a tool,
not a phone.
Mobility manages the Android handsets and tablets your business owns. Lock each one to the job you bought it for, push apps without a cable, fix it without a site visit, and prove all of it afterwards.
- Android only
- Nothing to install on a server
- Verified at 100,000 devices
A fleet of shared devices goes wrong in three ways.
Nobody knows which devices are working.
Fifty handsets across three sites and no list of which are online, which are flat, and which walked out of the building in March.
One screen showing every device and its state.
Staff change the setup and the job stops.
Games get installed, settings get changed, the scanner app gets removed, and the shift loses an hour to a device that used to work.
Lock each device to only the apps it needs.
Fixing one device means driving to it.
A setting is wrong on a terminal ninety miles away, so somebody spends half a day in a van to tap four things on a screen.
Take over the screen and fix it from the console.
Enrol once. Configure the group. Run the fleet.
Nothing is configured per device. Everything is set on a device group and inherited, which is the difference between managing fifty devices and five thousand.
Enrol
Create a device group in the console and it gives you an enrolment code. Scan it from a factory-reset device, or plug the device into our desktop enrolment app and let it provision over ADB. Either way the device installs the Mobility agent and registers itself into that group.
No per-device typing either way.
Configure
Set a policy for what the device is allowed to do, and an agent config for what its home screen offers. Both are set on the group, so a new device inherits everything the moment it joins.
Around 70 controls, versioned, inherited down the group tree.
Run
The console shows the fleet live. Alerts arrive when something goes wrong. Sixty reports answer the questions. Remote control handles what is left.
Live fleet, alerts, reports, remote support.
Four things worth the licence on their own.
The rest of the console is table stakes. These four are what a fleet owner actually notices.
Lock a device to its job
No settings, no browser, no app store, no games. The staff member sees a home screen with three icons on it because those are the three things they need. This is what stops a company handset becoming somebody's personal phone.
Kiosk and lockingFix it without going there
Support staff see the device's screen and control it, stream its logs, and browse its files, from the console, wherever the device is. Consent prompts and on-screen banners are configurable. This is the feature that saves the most money, because the alternative is a site visit.
Remote controlKnow where everything is
Live position for every device and full location history showing where it has been. Draw zones on a map and get an alert when a device leaves where it should be or enters where it should not. Dwell reporting shows how long devices actually spend on site.
Zones and locationProve it afterwards
Who took remote control and when. Who moved which devices between groups. Every restart, every unenrol, every zone crossing, every kiosk sign-in. Recorded, and exportable to CSV. Auditors ask for this and most competitors answer it thinly.
ReportingReports that tell you what to do.
Most fleet reporting hands you a number and leaves you to work out what it means. Several of ours lead with the finding instead.
Sixty reports across fifteen categories, every one exportable to CSV, and every one honest about what it could not answer.
See what reporting covers46 alerts, 44 of them Low battery, which is capped at once every 2 hours. This is one threshold set too tight, not a bad handset.
31 alerts, all Zone exit, all between 06:40 and 07:10. The depot zone boundary is inside the car park, not around it.
Enrol a device today and see the fleet by lunchtime.
The free plan needs no card. Bring one handset, scan a QR code, and look around the console with a real device in it.