Get Started
Peyara has two parts: a lightweight desktop server (Rust) and the mobile app. Both devices need to be on the same Wi-Fi network.
- Server: ayonshafiul/peyara-rust-server — Windows, macOS, Linux
- App: ayonshafiul/peyara-mouse — Google Play · App Store
1. Install and run the server
Install the server for your OS (Windows · macOS · Linux) and launch it.
The server window shows a QR code with its network address. Keep it open. On Linux with a Wayland session (e.g. Ubuntu 24), approve the one-time "remote interaction" system prompt so the phone can control the desktop.
2. Install the mobile app
Install the Peyara app on your phone from Google Play, the App Store, or the GitHub releases. Connect your phone to the same Wi-Fi network as your computer.
3. Pair with the QR code
Open the app, tap the Plus (+) button to add a server, and scan the QR code shown on the desktop window. The app verifies the code and saves the server — you only do this once. Saved servers stay in the list, so reconnecting later is a single tap.
4. Connect and control
Tap the saved server in the app list and press Connect. You can now:
- Move the cursor, click, right-click, drag, and scroll from the touchpad
- Switch between landscape and portrait touchpad layouts, with a side scroll wheel
- Type with your phone keyboard, including arrow and function keys
- Use play, pause, volume, and track controls
- Send text to the PC clipboard or pull text back to the phone
- Tune touchpad sensitivity, scroll sensitivity and response rate in Settings
To switch computers later, add another server the same way and tap to switch.
5. Open the Deck
From the connected touchpad, tap the Deck icon. Peyara shows a shortcut deck for the desktop app in focus — for example Photoshop keys while Photoshop is active, or browser shortcuts when your browser is in front. Tap a key to fire it on your PC.
The Deck ships with hundreds of presets. You can search actions, build your own layout, and add more presets from the open peyara-actions library.
If anything fails, see Troubleshooting.