android remote control app
Android remote control app support is now part of SimpleRemote. Alongside the Windows product, the Android host lets an authorized technician view a phone or tablet screen, guide the user with gesture control and move files during an attended session, without asking someone to describe a settings screen over the phone.
SimpleRemote
MediaProjection screen sharing, AccessibilityService gesture control, file transfer and relay transport for attended Android support.
Mobile support
Support teams have spent years asking a person to read out menu names on a phone they cannot see. An Android remote control app removes that guesswork by letting the technician look at the real screen and, when needed, guide the interaction directly. That matters for family tech support, small-business owners troubleshooting a company phone, and IT teams that already support Windows computers but have no equivalent workflow for the Android devices their staff carries.
Phones and tablets are not just smaller computers. Menus vary between manufacturers, apps behave differently across Android versions, and a person under stress often cannot describe what is on screen accurately. A remote support for Android devices session shortens that back-and-forth: the technician sees exactly what the user sees and can point to the right setting instead of guessing from a verbal description.
SimpleRemote added the Android host as a companion to its existing Windows remote control product. The workflow stays familiar: the same account, the same numeric device ID pattern, and the same idea of asking for permission before a session starts.
Mobile support
The Android host is built on two native Android capabilities rather than a workaround. Screen sharing uses Android's MediaProjection API, the same official mechanism used by screen recorders and casting apps. When a session starts, Android shows the user a system permission dialog and keeps a recording indicator visible for as long as the screen is being shared, so there is no hidden capture.
Gesture control uses Android's AccessibilityService framework to translate a technician's taps and swipes into real input on the device, the same category of API that powers accessibility tools for users with disabilities. Because both permissions are standard Android system features, the user can review, understand and revoke them from the device settings at any point.
The connection itself uses relay transport rather than a direct peer-to-peer link. That is a deliberate difference from the Windows product's P2P architecture, and it means an Android session can complete even when the phone is behind carrier-grade NAT or a mobile network that would block a direct connection.
Mobile support
On Windows, SimpleRemote supports both approval-based attended sessions and an authorized unattended password for owned or managed computers. The Android host currently covers attended support only: the person holding the phone opens the app and grants the screen-sharing and accessibility permissions for that session. There is no unattended Android access yet, which keeps the workflow closer to how people already expect phone support to work: someone is present, sees the request and agrees to it.
That distinction matters when planning a support process. If your team also manages Windows computers without a user present, the guide to unattended remote access software explains how that authorized-password model works on Windows. For Android, plan around a person being available to start the session, at least for now.
Mobile support
File transfer is one of the most requested parts of any remote support session, and the Android host includes it. A technician can send an installer, collect a screenshot or log file, or move a document between the phone and their own computer without asking the user to email attachments to themselves. This mirrors the dual-pane file transfer window already available in the SimpleRemote Windows app, covered in more detail in the guide to remote desktop with file transfer.
Keeping file movement inside the same authorized session, instead of a separate messaging app or personal cloud folder, reduces the number of places a support file ends up and makes it easier to confirm what was actually shared.
Mobile support
The person who needs support installs the SimpleRemote Android app on their phone or tablet and signs in or registers the device, which is assigned a numeric device ID, the same pattern used on Windows.
When a session request arrives, Android shows the native MediaProjection prompt for screen sharing. If gesture control is needed, the user also enables the AccessibilityService permission from the app, and Android keeps a visible indicator while sharing is active.
The technician enters the device ID and access details from their own SimpleRemote app, the same way they would connect to a Windows computer, and the session opens over the relay connection.
During the session the technician can see the screen, use gesture control to demonstrate steps, and send or collect files as needed. Either side can end the session, and Android's system indicator disappears as soon as screen sharing stops.
Mobile support
Because the Android host relies on Android's own MediaProjection and AccessibilityService permission models, the operating system itself enforces visibility: the user sees the permission request, sees the ongoing recording indicator, and can revoke either permission from system settings without needing to uninstall the app. That built-in transparency is one of the reasons attended-only support is a reasonable starting point for a mobile device that a person usually carries at all times.
For a broader view of mobile device risk beyond any single app, the NIST guidelines for managing the security of mobile devices and the official Android accessibility service documentation are useful neutral references. They reinforce the same principle SimpleRemote follows on Windows: keep permissions visible, limit them to what the session needs, and make it easy for the user to see and end an active connection.
Product fit
SimpleRemote is not positioned as a full mobile device management suite. It is a remote control product for companies, IT support teams and personal use, and the Android host extends that same focus to phones and tablets: attended screen sharing, gesture control, file transfer and a relay connection that works on carrier networks. For a broader comparison of what a support workflow should cover across devices, see the guide to remote support software.
Android remote control uses the same SimpleRemote account and pricing model as the Windows app. Personal or light use can start free with fair-use limits, and the business plan, from 1 EUR per user per month, adds users, address books, administration and billing when support becomes a recurring, managed task rather than an occasional favor.
FAQ
It is an Android host app that lets an authorized technician view an Android phone or tablet screen, use gesture control and transfer files during a support session, in addition to SimpleRemote's existing Windows remote control.
The Android host currently supports attended support only. The device owner starts the session and grants screen sharing, so there is no authorized unattended password option like on Windows yet.
It uses Android's MediaProjection API for screen sharing, which shows a system recording indicator, and an AccessibilityService permission for gesture control such as taps and swipes. Both permissions can be revoked at any time from the device.
Yes. The Android host includes file transfer, so a technician can send or collect files during an attended session, similar to the file transfer window on the Windows app.
Yes. Android sessions use relay transport, so the connection can complete even when the phone is on carrier NAT or a network where a direct connection is not possible.
Yes. Android remote control works with the same SimpleRemote account and pricing model as the Windows app, so personal or light use can start free and companies can add users and management from 1 EUR per user per month.
