Use cases · It started with my family

Why I built
RemotePocket.

I wanted to help my elderly parents manage and configure their phones, even when I wasn't there.

I didn't want them to have to open an app, read out a code or approve a connection every time they needed help. Getting access shouldn't be another task for them to work through.

The idea is simple: set it up together once, with their permission, then connect from my browser when they need a hand. I can see the screen and make changes directly, instead of trying to explain every tap over the phone.

Set up once. No new access approval for each session.

After pairing and enabling the required permissions, RemotePocket does not ask the person holding the phone to accept each connection. You sign in to your console and use the device password.

The Android phone must still be online, unlocked and running the accessibility service, with control enabled. If it locks or Android stops the service, someone may need to help on the device. The person using the phone can pause access or remove the pairing at any time.

Beyond family support

Other ways it can help.

These examples adapt common remote-support uses to RemotePocket's current Android features. The linked articles and case studies describe the wider use cases.

  1. Reach your own phone or tablet

    You may keep a second Android device at home or in another room. Open an app or check a setting from your computer, as long as the device is ready for remote access.

    For example: check the app on a spare tablet without going back to pick it up.

    Background: Splashtop's guide to remote Android access.

  2. Help a colleague get back to work

    When a work app behaves unexpectedly, see the problem on the employee's phone and work through the settings together. This can avoid a long exchange of screenshots and instructions.

    For example: check a notification setting that is hiding new job alerts.

    Background: TeamViewer's mobile device support brief (PDF).

  3. Support customers after setup

    A technician or small support business can help with devices already paired with the customer's permission. Look at an app's settings and explain a fix without arranging another visit.

    For example: help a customer finish configuring an app you installed for them.

    Background: TeamViewer's mobile support for customers and service providers (PDF).

  4. Help people working away from the office

    Drivers, field technicians and staff at another branch may need help while their support person is elsewhere. A remote view makes it easier to understand what is blocking them.

    For example: help a technician, while they are safely stopped, find the right screen in a job app.

    Background: TeamViewer's distributed support and logistics examples (PDF).

  5. Check tablets in shops and public spaces

    Android tablets can serve as menus, check-in screens, information kiosks or displays. Check what is on screen and adjust app settings from another location.

    For example: return a reception tablet to its welcome screen. Compatibility depends on the device and its kiosk restrictions.

    Background: TeamViewer's kiosk, retail and digital signage examples (PDF).

  6. Keep learning devices ready

    A school or training centre may have tablets used in different rooms or lent to learners. Help resolve a problem on an agreed, paired device without moving it to the IT office.

    For example: check a learning app's settings before the next lesson.

    Background: Splashtop's education and school IT examples.

  7. Support volunteers in different places

    In an association, one person may help several volunteers with their phones. Remote support can make that practical even when everyone works from a different place.

    For example: help a volunteer find and configure the app used to organise shifts.

    Background: TeamViewer's volunteer organisation example (PDF).

  8. Try an app on a real device

    Developers and testers can inspect an app on a paired Android phone at another desk or location. Use the browser to repeat taps and check what the user sees.

    For example: manually reproduce a layout problem on a particular phone model.

    Background: DeviceFarmer STF's browser-based device testing.

What these examples cover

RemotePocket currently provides screen viewing and manual control on Android: taps, swipes, navigation and text entry in supported fields. Screen viewing requires Android 11 or newer. App and device restrictions still apply.

Fleet-wide app deployment, automatic updates, test automation and dedicated kiosk management are not included. The examples above describe individual support sessions; they do not imply those extra features.

The public service is coming soon. Registration and sign-in are not open yet; you can already download the code and run it on your own server.

Contact

Have a similar
situation?

Tell me who you want to help and what you need to do on their device.

RemotePocket is open source under the GNU GPL v3 or later. You can run it on your own server.