I wanted a simple way to lend someone access to a physical Android phone remotely for a short session, without asking them to install anything or exposing ADB directly to the internet. I’ve put together an early Windows prototype with: - An Android phone connected to a PC over USB/ADB - A browser page for viewing and controlling the phone - An admin page that creates a timed invite link (1–240 minutes) - The first browser to open the invite claims the session; the server closes the stream when the timer expires - Cloudflare Tunnel Quick Tunnel for a temporary `trycloudflare.com` URL, so there’s no router port forwarding - ADB shell, file browsing, and devtools disabled in the web build The part I’m still working through is reliable end-to-end streaming on the target Android/ADB setup. I’ve hit ADB startup and scrcpy port-conflict issues, so I’m treating this as a prototype and don’t have a public live demo to share yet. I’d especially appreciate feedback on a few design questions: Would you expect the invite to be bound to the first browser, or should reconnecting from another browser be possible? What safeguards would you want before trusting a remote-control session like this? Is there a more reliable approach for streaming and controlling a USB-connected Android device from a browser? The invite is a bearer link, so anyone who gets it first can claim the session. I’m not treating this as production-ready while the streaming and security model are still being validated.   submitted by   /u/Ok_Voice4169 [link]   [comments]