Two packaging formats, two governance philosophies, and a Linux desktop that still cannot agree on how software should arrive.
The Fork in the Aisle
Flatpak and Snap both emerged around 2015–2016 to solve the same problem: Linux distributions ship applications at their own pace, and users and developers wanted a single package that would run across distros without waiting for Debian or Fedora's release cycle to catch up. The solutions they reached are technically similar enough to confuse newcomers and politically different enough to have never converged.
Flatpak is maintained under the Freedesktop.org umbrella with significant engineering from Red Hat. Its distribution hub, Flathub, is governed as an independent community project with no single corporate owner controlling what gets listed. Snap is designed and controlled by Canonical, the company behind Ubuntu; the Snap Store is a Canonical-operated service, and the snapd daemon that manages packages remains under Canonical's governance with a licence that has drawn scrutiny from Freedesktop contributors. That asymmetry — one community hub, one corporate store — is the sharpest governance distinction between the two.
The sandboxing models differ in ways that matter to security-conscious maintainers. Both use bubblewrap or similar kernel namespacing to isolate applications, but Flatpak's portal system, built on XDG Desktop Portals, lets a sandboxed application request access to host resources through a defined, user-mediated API. Critics of Snap have noted that certain system snaps — including snapd itself — run with elevated or unsandboxed permissions, a trade-off Canonical argues is necessary for deep desktop integration.
Update behaviour is another genuine fault line. Snap can apply updates silently and automatically without the user's consent mid-session; Canonical has acknowledged feedback on this and added deferral options, but the default remains more aggressive than Flatpak's opt-in approach. For a developer shipping an application where a mid-run update could break a running process, the difference is not cosmetic.
Neither format has won. Flathub crossed one billion downloads in 2023, and Snap remains the default packaging mechanism for several Ubuntu server and IoT use cases. Major distributions — Fedora, Linux Mint, elementaryOS — have aligned with Flatpak; Ubuntu ships Snap as default. The result is that application developers who want broad coverage must consider both, and the duplication cost is real.
The argument will not settle because it is not purely technical. It is a question of whether a commercial Linux vendor should own the primary channel through which software reaches its users, and no amount of portal API documentation resolves that.