Skip to main content

Glossary

Remote control

Remote control means an IT technician taking input on a user's device from a support console, as opposed to screen sharing, where the technician only watches what the user does. On mobile the distinction is not a feature tier, it is a platform limit: Android can allow real control depending on the manufacturer, while on iOS and iPadOS Apple permits screen viewing only, with the user's explicit consent.

How it works

On Android, a support session starts with a small agent on the device. What that agent can do depends on who signed it. With the privileged add-ons that manufacturers publish (Samsung Knox, Zebra, Honeywell, Lenovo and others), the agent gets OEM APIs for injecting touch and key events, so the technician can tap, type and swipe as if holding the phone. On a device with no vendor support, the same agent usually falls back to an accessibility service and screen capture, which gives a live view and limited interaction. Unattended control, with no one present to accept, is realistic on dedicated and kiosk devices where the vendor hooks exist and the MDM has provisioned the permissions in advance.

iOS and iPadOS are a different story. Apple exposes no API for a third party to drive another device, and there is no MDM command that turns it on. What you can get is a screen broadcast: the user starts it from the Control Center recording button, picks the support app, and the technician watches. The user has to act, every session, and they can stop it at any moment. Any vendor promising silent remote control of a standard iPhone is describing something that does not exist. macOS is more permissive, with Screen Sharing and Apple Remote Desktop.

So the honest split: guided support on iOS, real control on Android when the hardware cooperates.

Why it matters for a fleet

A warehouse scanner that stops reading barcodes at 6 a.m. is a production problem, and walking a temp worker through five settings screens by phone takes twenty minutes. Taking control takes two. For field technicians, delivery drivers and retail staff, remote support is usually the difference between a same-shift fix and a device shipped back to head office.

The governance side deserves more attention than it normally gets. A tool that can watch an employee's screen is employee monitoring under GDPR, whatever you call it internally. Run it on consent at session start, log who connected to which device and when, keep the retention short, and write it into the record of processing. In France and Germany, tell the works council before you deploy, not after someone complains. On BYOD devices, be stricter still: a personal phone should never be viewable without a prompt the user accepts.

How Appaloosa handles it

Appaloosa provides TeamViewer-based remote support from the same console used for enrollment, app distribution and policies, so a technician opens a session on an enrolled device without asking the user to install anything extra. Platform rules still apply: full control where Android and the manufacturer allow it, consented screen sharing on iOS and iPadOS. See the remote support page for what a session looks like in practice.

Explore

See the full platform

Enrollment, apps, security, remote support: all in one place.

Explore Appaloosa →

See Appaloosa run on your fleet Book a demo

Frequently asked questions

Can we remotely control an iPhone from the support console?
No. Apple provides no API for a third party to inject input into iOS or iPadOS, and no MDM command enables it. You can get a live view of the screen if the user starts a broadcast and chooses the support app, which is enough to guide them, and they can end it whenever they want. Treat anything described as silent iPhone control with suspicion.
Does remote control work without the user accepting?
On Android, yes in some cases: dedicated and kiosk devices with manufacturer support can be taken over unattended, which is what you want for an unstaffed terminal. On a phone carried by a person, prompt for consent anyway. On iOS it is never possible, because the user has to start the screen broadcast each time.
What do we need to document for GDPR before rolling this out?
Treat remote support as employee monitoring. Name the purpose and the legal basis, list it in your record of processing, log every session with operator, device and timestamp, and set a short retention on those logs. Inform employees, and in France or Germany consult the works council before deployment rather than afterwards.