Flatpak

Applications using Flatpak need permissions to have access to resources such as Bluetooth, sound (with PulseAudio), network, and files. These permissions are defined by the maintainer of the Flatpak and can be added or removed by users on their system.[7][8]

Another key feature of Flatpak is that it allows application developers to directly provide updates to users without going through distributions, and without having to package and test the application separately for each distribution.[9]

Flathub, a repository (or remote source in the Flatpak terminology) located at flathub.org, has become the de facto standard for getting applications packaged with Flatpak.[10] Packages are added to it by both the Flathub administrators and the developers of the programs themselves (though the admins have stated their preference for developer-submitted apps).[11] Although Flathub is the de facto source for applications packaged with Flatpak, Flatpak can work independently of Flathub;[12] it is possible to host a Flatpak repository that is completely independent of Flathub.[13][14]

Theoretically, Flatpak apps can be installed on any existing Linux distribution. Among the first Linux distributions which added support to Flatpak apps out-of-the-box were Endless OS,[15] Linux Mint,[16] Elementary OS,[17] Fedora Silverblue,[18][19] Zorin OS,[20] and Pop! OS.[21] Flatpak is also available for other distributions, including Ubuntu,[22] Red Hat Enterprise Linux,[23] OpenSUSE,[24] Arch Linux,[25] Debian,[26] CentOS,[27] Gentoo Linux,[28] Kubuntu,[29] Solus,[30] Alpine Linux,[31] Mageia,[32] Raspberry Pi OS,[33] Void Linux,[34] NixOS,[35] Pardus,[36] KaOS,[37] Zenwalk,[38] OpenMandriva Lx,[39] MX Linux,[40][41] PCLinuxOS,[42] KDE_neon,[43] EndeavourOS,[44] Deepin,[45] Manjaro,[46] and PureOS[47] It can also be used on Linux kernel-based systems like Chrome OS.[48]

• AppImage
• Snap
• Zero Install