WebRTC Remote Desktop Build
Budget: $250 – $750 USD
I want to take LiteDesk from concept to a working Windows build that feels every bit as smooth as AnyDesk but is powered entirely by modern web tech. The core is already mapped out: WebRTC will handle the low-latency P2P screen stream, each machine keeps a persistent unique ID, and an easy name-based handshake starts every session.
Here is what I need put in place:
• Viewing modes – both Full Control and View-Only must be implemented with equal polish. The remote side can approve, refuse, or downgrade a request at any moment.
• Security – beyond the base name authentication, every session generates a dynamic, single-use PIN that must be entered before the stream begins.
• UX – keep the interface minimalistic and clean. One click should be enough to start sharing; anything more belongs in a discreet “advanced” panel.
• Build – the final output has to be a self-contained Windows executable, ideally produced with Electron or a comparable framework so future cross-platform ports stay open.
Acceptance criteria
1. Two Windows clients connect directly over WebRTC without relaying once STUN/TURN discovery is complete.
2. Latency when moving a window on a 1080p desktop stays under 120 ms on a typical broadband connection.
3. Dynamic PIN displays on the host side and is validated on the guest side before streaming starts.
4. Switching between Full Control and View-Only is possible mid-session without restarting.
5. A first-run experience: launch the .exe, receive/see my unique ID, share it and the PIN, and connect—no extra setup.
Source code, build scripts, and concise setup notes must be included so I can reproduce the build on my end. If you have previous WebRTC or remote-desktop work, let me know; it will help me gauge the best path forward.
Here is what I need put in place:
• Viewing modes – both Full Control and View-Only must be implemented with equal polish. The remote side can approve, refuse, or downgrade a request at any moment.
• Security – beyond the base name authentication, every session generates a dynamic, single-use PIN that must be entered before the stream begins.
• UX – keep the interface minimalistic and clean. One click should be enough to start sharing; anything more belongs in a discreet “advanced” panel.
• Build – the final output has to be a self-contained Windows executable, ideally produced with Electron or a comparable framework so future cross-platform ports stay open.
Acceptance criteria
1. Two Windows clients connect directly over WebRTC without relaying once STUN/TURN discovery is complete.
2. Latency when moving a window on a 1080p desktop stays under 120 ms on a typical broadband connection.
3. Dynamic PIN displays on the host side and is validated on the guest side before streaming starts.
4. Switching between Full Control and View-Only is possible mid-session without restarting.
5. A first-run experience: launch the .exe, receive/see my unique ID, share it and the PIN, and connect—no extra setup.
Source code, build scripts, and concise setup notes must be included so I can reproduce the build on my end. If you have previous WebRTC or remote-desktop work, let me know; it will help me gauge the best path forward.