aniadev / android-stream-desk

What is android-stream-desk?

This project turns any old Android phone or tablet into a wireless macro keypad for your Windows PC. Think of it as a budget Elgato Stream Deck -- you tap buttons on your phone and it triggers keyboard shortcuts, launches apps, or controls media on your computer. The setup consists of a Windows companion app that runs in the system tray and an Android client that connects over your local Wi-Fi network. Everything communicates via WebSockets on port 8089, with no cloud dependency and no internet required. The frontend is built with Vue and Tailwind CSS, while the companion app uses Tauri with a Rust backend for low-latency keyboard emulation.

Why is it gaining traction?

The main appeal is the price point -- literally free if you have a spare Android device collecting dust. The latency claims of under 30ms are competitive for a hobby project, and the dynamic grid layout (configurable from 2x2 up to 6x8) gives it flexibility that physical Stream Decks lack. The fact that it works entirely over LAN means zero cloud exposure and instant response times. The dashboard editor lets you customize button colors, icons, and actions directly from the companion app, with changes syncing live to the phone.

Who should use this?

Streamers and content creators on a budget who want macro buttons for scene switching or audio control will find this most useful. Developers working from home could repurpose an old phone as a dedicated shortcut pad. Anyone frustrated by Stream Deck pricing who has basic networking knowledge (you'll need to find your PC's local IP) will get the most value. It's less suited for mission-critical production environments where reliability trumps cost savings.

Verdict

At 45 stars and a credibility score of 0.85%, this is a young, unproven project with minimal community feedback. The documentation exists and the concept works, but test coverage and maintenance track record are unclear. Download the pre-built releases if you want to try it without compiling, but treat it as experimental software -- have a backup plan for any workflows you automate with it.