Dish vs Remote Gamepad and other phone-as-controller apps: a fair comparison

If you’ve searched for “use my phone as a wireless controller for PC” in the last few years, you’ve almost certainly come across one of these:

• Remote Gamepad (a few different apps go by this name; the most popular has ~5M Play Store installs)
• Monect PC Remote (~10M Play Store installs)
• PC Remote Receiver by Monect
• Mobile Gamepad (~1M installs)
• DroidJoy Gamepad Joystick
• Gamepad: Xbox360, PS3 Emulator (yes, that’s the name)

They’ve all built variations on the same core idea: an Android app with on-screen buttons that talks to a Windows companion app over the LAN. They’ve collectively introduced millions of people to the concept of phone-as-controller, which is great.

Less great: most of them are free with ads, harvest telemetry, use TCP for input (which is slower), and have no encryption. Some of the most popular options have permission lists that include “view network connections,” “read your contacts,” and “see device location,” which is wildly more access than a controller app should ever need.

This is the apples-to-apples comparison between Dish and the existing phone-as-controller app landscape.

The headline numbers

The biggest difference is the transport. Most “Remote Gamepad”-style apps use TCP because it’s easy to write and works through home routers without configuration. The trade-off is that TCP retransmits lost packets, which is great for HTTP and terrible for real-time input. A single 100 ms TCP retransmit during a fight stick combo and your character missed a frame-perfect input.

Dish uses UDP because lost input packets are old input packets. The next packet (always at most 2 seconds away at the heartbeat interval, or instant on the next button press) supersedes them. Dish handles its own ordering and replay protection, which is cheap and tuned for input traffic, instead of inheriting TCP’s general-purpose ordering, which is expensive.

Why “Remote Gamepad” apps feel laggy

Latency in these apps comes from a few stacked sources:

1. TCP retransmits and head-of-line blocking. A single dropped packet stalls the whole stream.
2. 30 to 60 Hz polling. Many of these apps sample your touchscreen every 16 to 33 ms because they were originally designed as media remotes, not gamepads.
3. JSON or XML over HTTP. Yes, some of them really do encode each button press as a JSON object. That’s hundreds of bytes for what should be 12 bytes of binary.
4. No QoS marking. The input packets share queueing priority with everyone else’s TikTok stream on the LAN.
5. GC pauses. Apps written without careful attention to allocation will hit a 30 to 100 ms GC pause once a minute, and you’ll feel each one as a stick-frozen moment.

Dish’s hot path is: input event → 12-byte struct → ChaCha20-Poly1305 seal → sendto → done. No queue, no JSON, no async runtime, no GC pause (the path is allocation-free). That’s why the latency budget is single digits.

Why “Remote Gamepad” apps are bad for your privacy

Let’s be specific. Looking at the top three “Remote Gamepad” / “PC Remote” results on the Play Store as of early 2026, the typical permission list includes:

• Internet: ok, it’s a network app.
• Network state: ok.
• Read device storage: why?
• Read phone state and identity: for ads ID tracking.
• Approximate location: for ad targeting.
• Wake lock: keeps the screen on, fine.

Most of these apps embed at least one analytics SDK (Firebase, AppsFlyer, Adjust, or similar), and the free tier includes interstitial ads from Google AdMob or Unity Ads. Each ad impression sends a request that includes your device fingerprint and a probabilistic user ID.

Dish’s permission list:

• Internet. Sends UDP to your gaming PC.

That’s it. No analytics, no ads SDK, no location, no contacts, no phone-state, no advertising ID. The full source is on GitHub. You can audit it yourself.

Why “Remote Gamepad” apps are bad for your security

Most of these apps either (1) trust any device that knows the gaming PC’s name on the LAN, or (2) have a static “password” you set up once and which is sent in the clear over the wire.

That’s fine on a home Wi-Fi where you trust everyone on the network. It is not fine in a coffee shop, a hotel, a college dorm, or a friend’s house. A trivial Wireshark capture reveals the password, and on most of these apps the input stream itself is unencrypted, so anyone on the LAN can sniff what you’re playing and how you’re playing it.

Dish uses a real PIN-based PAKE during pairing to derive a long-term shared secret, which is then used to derive per-session keys for ChaCha20-Poly1305 AEAD on every packet. There is no plaintext fallback. If verification fails, the packet is silently dropped. Read the security page for the threat model in detail.

Where the existing apps still have edges

Honest comparison.

1. They have iOS apps right now

Several “Remote Gamepad” apps have iOS clients today. Dish’s iOS client is in development but not yet released. If you need an iPhone to be the controller this week, the existing apps are an option.

2. They have larger built-in button libraries

Some of these apps include hundreds of pre-set “control schemes” that include keyboard mapping, mouse mapping, presentation remotes, media keys. Dish is a gamepad. It focuses on emulating a virtual Xbox 360 pad and lets you map your own touch overlay, but it doesn’t try to be a generic remote desktop tool.

3. They work over the internet (sort of)

Some of these apps have a paid “remote access” feature where you can use them from anywhere through their cloud relay. Dish is LAN-only by design. That’s how it hits single-digit-millisecond latency. If you need internet-distance phone-as-controller, those apps may fit better, at the cost of latency, privacy, and a subscription fee.

Who should switch

You should switch from a “Remote Gamepad” / Monect / PC Remote-style app to Dish if:

• You’re tired of full-screen ads while you’re trying to play.
• You don’t want analytics SDKs phoning home about your gaming habits.
• You can feel the latency, especially in fast-paced games.
• You want couch co-op (most of these apps are single-controller).
• You care about whether your inputs are encrypted on a shared Wi-Fi.

You might keep your existing app if:

• You need iOS today.
• You use it as a generic remote control, keyboard, mouse, not just a gamepad.
• You need internet-distance control via the app’s relay service.

How to switch

1. Uninstall the old app. (Optional but recommended. It removes whatever telemetry SDK it had.)
2. Install Dish for Android on your phone. (Windows, macOS, and Linux clients are in development for later releases.)
3. Install Satellite for Windows on your gaming PC.
4. Pair once with a 4-digit PIN.
5. Press a button. Your game responds.

Total time: 5 minutes. Zero dollars. No ads, no analytics, no compromise on latency.

What to read next

• Use your phone as a wireless controller for your PC
• Why Wi-Fi UDP beats Bluetooth for gamepad streaming
• Connecting a controller to a PC from another room, the right way
• PC gamepads compared: 15 wireless controllers and virtual gamepad apps, ranked by latency

If switching to Dish improved your phone-as-controller setup, donations keep the project alive. We don’t run ads. We don’t sell anything. The project survives entirely on donations.

Methodology

Latency comparison performed by side-by-side install of the top three “PC Remote” / “Remote Gamepad” apps on a Pixel 8 plus Windows 11 gaming PC, both on the same TP-Link Wi-Fi 6E AP. Measured with a high-speed camera (240 fps) recording finger-press to on-screen response over 50 trials per app. Median values reported.

Permission and SDK observations made via APK static analysis of the most-downloaded “Remote Gamepad” / “PC Remote” / “Mobile Gamepad” apps on the Play Store as of January 2026. Specific app names omitted to avoid singling any one project out. The patterns are consistent across the category.

Numbers should be re-verified against your specific hardware and the specific app you’re comparing before being quoted authoritatively.

Gostou do que está lendo?

Dish e Satellite são gratuitos e de código aberto. As doações garantem que continuem assim.

Doar Baixar Dish