The app itself is free to run all day. What it rides on — your mobile connection — is not always free, fast or present. Here is the honest arithmetic of admin work on mobile data.
Not all app work is equal. Reading numbers off a server is a whisper of data. Watching a live remote desktop is a shout. Admins who know the difference work comfortably on any connection; admins who do not learn it from a dead plan or a frozen screen. Figures below are honest working estimates, not lab measurements — your mileage will vary with screen size, content and connection quality, which is rather the point of the page.
Most of the app's day is featherweight. Fleet health, computer lists, inventory details, patch counts, approvals, agent progress, firing a restart or a Wake on LAN — these are small structured requests and short answers. You could do the entire monitoring-and-approvals routine on a weak connection, all month, and the data would barely register. The same is nearly true of the command prompt tool: text in, text out. This is the quiet superpower of the app — the work you do most often is the work that costs least, which is why phone admin survives perfectly well on ordinary plans and ordinary signals.
A remote control session sends you a living picture of someone's desktop, refreshed continuously. That behaves like streaming video because it is streaming video: a busy session can use data at a rate comparable to watching a video call — think in terms of hundreds of megabytes per hour for active screen work, less for a still desktop, more for motion and large monitors. Two practical consequences follow. On a capped plan, save long remote sessions for Wi-Fi or accept them as the plan's main expense. And on a weak signal, expect the session to feel it first — lag, soft picture, delayed clicks — while the light work keeps sailing through the same connection without complaint.
The other honest reality: the app's usability outside the office is set by your route, not the app. A phone on office Wi-Fi talking straight to the server is instant. The same phone reaching the server through a VPN adds a small toll to every action — usually unnoticeable for light work, occasionally felt in remote sessions. Congested evening networks and moving vehicles degrade remote control long before they degrade approvals. The working habit this produces is simple: match the job to the connection you actually have. Approvals and fixes-by-command-prompt from anywhere; long screen sessions from somewhere with decent signal; fleet marathons from the desk.
The full video shows monitoring, approvals and remote control in action — judge the experience for yourself.
▶️ Watch Full VideoThe daily routine — health checks, approvals, quick actions — is very light and will not trouble a normal plan. Remote control sessions are the heavy item; treat long ones as video streaming and prefer Wi-Fi for them.
Distance and route. Outside, your session travels through the mobile network and possibly a VPN before reaching the server, and a live desktop picture exposes every delay. Light app work hides the same delay completely.
Yes. It is text-based, so it stays light and responsive on connections where the full screen struggles. Many quick fixes — a service restart, a network check — are two commands and done.