KDE Connect: Enabling communication between all your devices

Original Article ↗ Hacker News Discussion ↗

Cross‑platform scope and desktop environments

  • Works on Linux/Plasma, other Linux DEs (via KDE Connect package, GSConnect, Valent), Windows, macOS, Steam Deck, even some VR devices; no KDE desktop required.
  • Branding confuses people into thinking it’s KDE‑only; several say it runs fine on i3, XFCE, GNOME, etc.
  • Some distros preinstall it with KDE; others don’t, which frustrates people expecting out‑of‑the‑box availability.

Networking model, discovery, and VPNs

  • Primarily designed for local‑network use; also supports Bluetooth.
  • Uses multicast/broadcast (described as its own mDNS‑like mechanism) for discovery, so:
    • Breaks across subnets, many VPNs (WireGuard, Tailscale), and “AP isolation” Wi‑Fi setups unless you configure routing or manually add IPs.
    • Some report WireGuard / multi‑interface bugs tracked in KDE’s bug tracker.
  • WAN use is possible only with VPNs or manual port forwarding + static IPs; no relay/coordination server exists, though some wish for a self‑hosted one.

Reliability: split opinions

  • Many describe it as “rock solid” for years between multiple Linux machines and Android phones, especially on simple single‑subnet home networks.
  • Others see it as unreliable or regressed:
    • Devices on same Wi‑Fi often don’t see each other, require manual refresh, unpair/repair, or even watchdog scripts restarting the daemon.
    • File transfers fail mid‑way; desktop–desktop and Windows setups are singled out as especially flaky.
    • Some compare it unfavorably to LocalSend/AirDrop for pure file transfer.

Platform‑specific behavior

  • Android: generally best experience; deep integration (notifications, media control, remote input, clipboard). Some battery impact from aggressive keep‑alives was reported and later patched.
  • iOS: heavily constrained. App must be foregrounded; background notifications, SMS integration, and iMessage‑style workflows effectively don’t work. Several users call it “basically non‑functional.”
  • Windows: works for some, but others report frequent discovery/connectivity problems and give up on daily use.
  • macOS: exists and can work (e.g., with Steam Deck), but not as polished as Linux/Android.

Features people value

  • Shared clipboard between phone and desktop, including passwords and long messages.
  • Fast local file transfers and mounting phone storage.
  • Notification mirroring, SMS texting from desktop (where supported), media playback control (including pausing videos on calls), “ping” and device‑find, remote keyboard/mouse/gyro‑mouse, and Steam Deck integration.
  • Viewed by many as an open‑source analogue to Apple’s Continuity/AirDrop/Universal Clipboard.

Alternatives and complementary tools

  • For ongoing sync / large hierarchies: commenters recommend Syncthing or rsync/SSH instead of KDE Connect.
  • For simple cross‑device file transfer: LocalSend, PairDrop, SSHFS, Samba, and various mobile file‑transfer apps are mentioned.
  • Some combine KDE Connect with VPNs (WireGuard, Tailscale, Zerotier) for remote operation, with varying success.

Usability, UX, and resource issues

  • Common annoyances:
    • Phone sometimes not auto‑connecting; user must open the app to re‑establish the link.
    • SMS UI on desktop is laggy, slow to sync history/contacts, visually rough, and missing image display.
    • One‑directional behavior (e.g., only phone→PC works), silent file transfers on Android, and surprising filename changes (.tif→.tiff) in at least one case.
  • Android “quit” semantics cause confusion; some want a clear way to fully exit, others note that’s against typical Android design.

Security and configuration concerns

  • One commenter claims default configuration enables sidestepping 2FA and sideloading apps without permission but doesn’t provide details; others ask for elaboration.
  • Discovery’s dependence on multicast/broadcast raises worries about information leakage on complex or shared networks.
  • Firewalls, Wi‑Fi isolation, and buggy Wi‑Fi drivers frequently interfere; users stress the need to adjust firewall profiles (e.g., Windows “public” vs “private” network) and understand local networking to get reliable behavior.