Linux doesn't have a stable, universal GUI stack. A cross‑platform app built for Windows/macOS expects a single windowing system, input model, compositor behavior, accessibility API, clipboard API, and one drag‑and‑drop API. Linux gives them 20+ permutations, with many being incompatible.
Apps like Discord, Slack, VS Code, Steam, Chrome, Spotify, etc. end up with broken screen sharing, window resizing, drag‑and‑drop, HiDPI scaling, input methods, accessibility, window shadows, titlebars and clipboard behavior. -Not because the apps are bad, but because Linux is not one platform.
Wayland is marketed as "the future," but it's not a single protocol. It provides a base with dozens of optional, distro‑dependent extensions. Cross‑platform apps need screen capture, window capture, global hotkeys, window positioning, drag‑and‑drop, clipboard management, cccessibility hooks, IME support, touchpad gestures, color management, HDR, and Fractional scaling. Wayland only provides up to ~3 of those, the rest are dependent on compositor specific applications that differ accross Gnme, Plasma, Sway, Hyprland, etc.
So, you're expecting cross‑platform apps to implement GNOME's extensions (which break on updates), Plasma extensions (which are buggy), wlroots extensions, and hope the distros don't patch them differently (they always do).
Zoom screen sharing breaks, OBS window capture breaks, Electron apps behave differently per DE, Chrome and Firefox have different Wayland feature sets, Steam's windowing is inconsistent, and games can't reliably capture input.
Wayland is not a platform; it's a protocol with stunted development.
Cross‑platform apps want a single runtime, packaging format, dependency model, and sandbox model. Linux gives them DEB, RPM, AppImage, Flatpak, Snap, Tarball, custom launchers. -And that's on top of distro-specific patches, library versions, and sandboxing rules.
Apps break because distros ship older libraries, newer libraries, sandboxing blocks system APIs, AppImage bundles conflict with system libs, Flatpak portals aren't implemented consistently, and Snap's confinement is too strict.
Cross‑platform apps end up shipping three different Linux builds, each with different bugs.
Cross‑platform apps would like one audio API, a single mixer, and one device model. Linux vomits ALSA, Pulse, PipeWire, JACK, per-distro configurations, pr-DE routing quirks, per-hardware quirks, and bluetooth codec roulette on them. (But it's NoT LiNuX FaUlT! /s)
Zoom audio devices disappear, Discord echo cancellation breaks, Steam voice chat breaks, Games randomly lose audio, and Electron apps can't enumerate devices reliably. You're not just supporting 'one other' OS by cross developing for Linux.
Cross‑platform apps want a single file picker, theme model, notification system, system tray, global menu model, and one window decoration model.
Linux vomits up Gnome and Plasma's fiel picker, XDG portals (at times), System tray (that's deprecated in Gnome), AppIndicators, CSD vs SSD wars, and per-DE theme engines, icon sets and dark mode toggles. If you've ever installed apps from different toolkits on Linux and tried to theme; you're already familiar with the struggle.
Electron apps have broken titlebars, Chrome's dark mode doesn't match the DE, Steam's tray icon disappears on GNOME, File pickers are inconsistent, and apps can't reliably detect dark mode, or system theme.
Cross‑platform apps end up looking like aliens on Linux.
Cross‑platform apps would like one OS, one set of system libraries, and one set of kernel configs. Linux throws a dozen distro specific patches, and endless custom kernels, Mesa versions, and drivers.
"Your fault; you chose the wrong distro" -could just be the luck of the draw of your app working on one distro and not the other (and that can quickly change)
Windows: ABI stable for decades. MacOS: ABI stable per major release. Linux: ABI breaks constantly. Cross-platform apps have to bundle everything, ship huge runtimes, and avoid system libraries, distro packages, kernel‑dependent features, and GPU‑dependent features.
This makes Electron apps massive. Steam has to bundle its own runtime. Chrome ships its own libraries, games ship their own lbistdc++, and apps avoid system GTK/QT versions.
Linux's ABI instability makes cross‑platform apps bloated.
A single graphics API, driver model, shader compiler, and GPU memory model would be nice. -But NO! Linux gives them Mesa, Proprietary NVIDIA and AMD, per-distro Mesa versions, per-kernel driver quirks, per-DE compositor quirks, and per-GPU Vulkan layer differences.
Chrome GPU acceleration breaks, Electron apps flicker, Steam UI stutters, games crash on one driver but not another, and HDR and color management is nonexistent. Cross‑platform apps cannot rely on GPU behavior on Linux.
Cross‑platform apps aren’t failing; they're drowning in fragmentation.