Tether · Case study
adb.Without the text file.
Every Android developer keeps a text file of adb commands. Tether replaces it with one quiet, keyboard-first window that talks to the adb server directly.
0released
macOSvia a Homebrew tap
Rustcore on Tauri
⌘Keverything one shortcut away
How it fits together
- 01React UI
- 02Tauri IPC
- 03Rust core
- 04adb protocol
- 05Device
01
Talking to adb, not around it
Most adb GUIs shell out to the CLI and parse its text. Tether speaks the adb server's own protocol from Rust, so it gets structured answers, streams and many devices at once without guessing at output formats.
02
Everything in one window
- Screen mirroring through scrcpy-server, with audio and recording.
- A file manager, and APK installs to several devices in one go.
- Logcat that spots crashes, and a shell with tabs.
- Wi-Fi pairing by QR code, performance graphs, developer toggles, OTA sideload.
03
Keyboard first
A ⌘K palette reaches every action. Spring animations, light and dark themes, Russian and English.
04
Shipping it
Signed over-the-air updates, distributed through my own Homebrew tap.
05
Stack
Tauri and Rust underneath; React, TypeScript, Tailwind and shadcn/ui on top.