Mango Wayland Compositor hits v0.16.0 with native touch support and XWayland fixes
Mango Wayland Compositor (MangoWM) has reached version 0.16.0, and it's continuing to chip away at the "dwm but wayland" niche with features that matter. The release adds native touch input, fixes XWayland scaling blur, and implements the xdg_activation_v1 protocol to stop windows from stealing focus. If you've been tracking the project's rapid rise to roughly 3,456 stars since its February 2025 launch, this feels like a solid step toward daily-driver maturity.
The compositor, maintained by DreamMaoMao, builds on wlroots and scenefx while keeping the minimalist philosophy of dwl. It started where dwl left off, adding practical features for actual desktop use. This includes tags with independent layouts, a scroller/dindle/master-stack/grid layout engine, and scratchpad support. The v0.16.0 update focuses on stability and usability, addressing some of the gaps that usually prevent a dwl fork from being a primary desktop environment.
What's actually new in v0.16.0
Native touch support is the headline here. MangoWM now handles touch input directly, which is a big deal for 2-in-1 convertible laptops and touchscreen monitors. You no longer need workarounds to make touch gestures work. On top of that, XWayland applications can now render without that unwanted blur at non-integer scales. The new xwayland_ignore_scale config option lets you set explicit DPI values, like 144, to match your monitor's native resolution.
The window-switching experience has also been redesigned. The Alt+Tab switcher now flows more smoothly, and the Hycov-style overview updates in real time. Windows appear, move, and close instantly rather than lagging behind your actions.
For power users, Mango adds a force_render window rule. This prevents frame rate drops to zero when a window is hidden, ensuring animations stay smooth even for non-visible clients. The overview jump mode now supports user-defined hit labels, and input bindings for mouse, axis, and gestures can be gated by keymode. Keep in mind that the configuration loader now scans for input binding conflicts at startup, so you'll see problems before they cause runtime issues.
Breaking changes and configuration tweaks
There's one breaking change to be aware of. The ov_no_resize option has been removed. The behavior it controlled is now the default, so no migration path is needed. You can just delete that line from your config.
Tag management got more flexible too. Users can now configure the total number of tags instead of being stuck with a hardcoded default. The * wildcard character works in tag rules for matching any ID, making wildcard-based window-to-tag assignments much easier. If you're scripting your setup, two new IPC commands have arrived: tag_num to query the number of tags, and hide_clients to programmatically hide clients.
The v0.16.0 release also includes some critical bug fixes. Mango now fixes a crash after system suspend on certain monitors, which is essential for a daily driver. The max buffer size increased to 1 MiB to stop crashes in some XWayland clients. There's also a fix for a potential integer overflow in scrolling and dwindle layout calculations, plus pointer constraint activation on layer-shell surfaces that was causing errors with lan-mouse.
Community and ecosystem
The project has a growing ecosystem of extensions. Users have shared layout scripts like mangolay, dotfile repos, and a custom bar called mangobar built with Fabric. Community forks are already porting features like dwindle layout from Hyprland.
Mango competes directly with Sway, Hyprland, and dwl forks. Sway is heavier with feature-complete IPC, while Hyprland is GPU-heavy with eye-catching animations. Mango sits in the middle, retaining dwl's simplicity but adding features that make it practical. The vision emphasizes stability and practicality over novelty.
The release received strong engagement from the community, with 13 unique reactors giving thumbs-up, hooray, and rocket emojis. For comparison, the previous major release saw 33 reactors. This suggests sustained interest, even if this release is more maintenance-focused than feature-dense.
MangoWM is available across multiple distributions. Arch users can grab it via yay -S mangowm-git. NixOS users can use the provided flake. Fedora, Gentoo, Guix, openSUSE, and PikaOS also have packages. You can find the full changelog, documentation, and Discord server on the project's GitHub and website.
If you're running a dwl-based setup and want touch support or better XWayland handling, MangoWM v0.16.0 is worth a try.
