Why doesn't anydesk support wayland yet?

The primary reason Anydesk does not yet support Wayland is a fundamental technical and strategic misalignment between the protocol's security model and the core requirements of a remote desktop application. Wayland, designed as a successor to the X11 display server, enforces a strict client-server separation where applications cannot directly access the framebuffer or input events of other windows. This is a deliberate security and stability feature, preventing keyloggers or screen scrapers from operating as they could under X11. However, for a remote desktop tool like Anydesk, this very feature becomes a significant barrier. The application needs precisely that kind of system-level access to capture the entire desktop's graphical output, inject synthetic keyboard and mouse events, and manage remote cursor positions. On X11, this is achieved through extensions and direct access to the X server, a model that is inherently incompatible with Wayland's secure-by-design philosophy.

The technical pathway to supporting Wayland exists but is more complex and fragmented, requiring integration with specific desktop environments' portals and APIs rather than a single universal method. Solutions involve using the PipeWire multimedia server for screen capture and the various desktop environment portals (like the one provided by GNOME's Mutter or KDE's KWin) for input injection and virtual input device creation. This requires significant development effort to implement and test across different compositors, as the implementations and supported features can vary. For a commercial entity like Anydesk, this translates into a substantial investment in engineering resources for a user base that, while growing, remains predominantly on X11 in the Linux ecosystem. The return on this investment is weighed against other priorities, such as feature development for Windows and macOS, which constitute the vast majority of their market.

Furthermore, the Linux desktop environment itself is in a transitional state regarding Wayland adoption. While major distributions and desktop environments like GNOME and KDE Plasma now default to Wayland sessions, a significant portion of enterprise and professional users, who are key clients for remote desktop software, may still be using X11 due to legacy application compatibility or driver support issues. This bifurcated landscape creates a "chicken and egg" problem: some users cannot fully adopt Wayland because critical professional tools like Anydesk lack support, and Anydesk may be hesitant to allocate major resources until Wayland's adoption reaches a critical mass that justifies the development cost. The company's stance is likely one of cautious observation, waiting for the ecosystem to stabilize around more uniform and mature APIs for remote desktop functionality.

Consequently, the absence of Wayland support is not a simple oversight but a calculated position based on current technical hurdles, market dynamics, and development economics. The shift will inevitably require Anydesk to re-architect its Linux client to use the modern, albeit more complex, suite of Wayland protocols. This move will likely coincide with a broader industry tipping point, potentially driven by the maturation of the underlying standards like PipeWire and the xdg-desktop-portal project, combined with increased user demand as Wayland becomes inescapable. Until then, users requiring Anydesk on Linux must either use an X11 session or seek alternative remote access solutions that have already navigated the complexities of the Wayland ecosystem.