Good question. At the moment Objo Studio’s Linux build uses Avalonia’s current X11 desktop backend. On Wayland desktops the expected compatibility path is XWayland, so it should still run on most modern Wayland-based distributions, but it is not native Wayland yet.
This is mainly an Avalonia roadmap item rather than a .NET runtime item. .NET does not provide the Linux desktop windowing backend; Avalonia does. Avalonia has Wayland work underway: Avalonia 12 lays the groundwork, and their current public messaging describes native Wayland as being in private preview / testing rather than something I would treat as fully general-purpose production support today.
My strategy is to keep Objo working on X11/XWayland for now, avoid taking dependencies on X11-specific behaviour where possible, and move to Avalonia’s native Wayland backend once it is generally available and has been tested against real Objo Studio workflows on GNOME/KDE Wayland. So yes, it is on the internal roadmap, but I do not want to overpromise native Wayland support before the underlying Avalonia backend is ready.