The Next Version of Flatpak to Depend on systemd, Sparks Debate in Linux Desktop Community

The Day Flatpak Abandons Its “Compatible with All Distributions”

Banner Flatpak, an application distribution and runtime platform for Linux desktops, has long touted its ability to “build one app for all distributions” as its greatest strength. This advantage is even highlighted prominently on its official website. However, this cornerstone of Flatpak’s identity may soon be called into question. In the roadmap for its next major version—referred to as “Flatpak Next” or “Flatpak 2.0”—the developers have proposed introducing a dependency on systemd. This marks a significant and potentially far-reaching shift for the entire Linux ecosystem.

Future Vision Shared at the Linux App Summit At the Linux App Summit held in May 2026, Flatpak developers Arian Vovk and Sebastian Wick delivered a detailed presentation on the future direction of Flatpak. Their presentation outlined a comprehensive overhaul of the existing Flatpak 1.x design, essentially amounting to a complete rewrite. While the current version of Flatpak has seen continuous improvements over the years, its fundamental design, which dates back more than a decade, is increasingly showing its limitations. Vovk and Wick envision a new architecture that leverages modern technologies and ideas that have become mainstream since the initial design of Flatpak.

A New Service Layer: systemd-appd At the heart of the plan is the idea of decoupling permission management from the core Flatpak application and migrating it to a service layer. Specifically, a new service called systemd-appd is set to be introduced. Systemd-appd will handle the assignment of unique identifiers to applications and the storage of their permission data. This data will then be accessible to other system components. According to the developers, this new design will enable features that are currently difficult to implement in Flatpak, such as nested sandboxing for enhanced security. However, the introduction of systemd-appd inherently creates a dependency on systemd, making it a prerequisite for using Flatpak.

Impact on Non-systemd Distributions Currently, Flatpak officially supports non-systemd distributions like Void Linux, Guix, and Alpine. These distributions have deliberately chosen not to adopt systemd due to their differing philosophies and design principles. Many of their user communities rely on Flatpak as a crucial means of application distribution. If the dependency on systemd becomes a reality, these distributions will face a significant dilemma: abandon Flatpak, port parts of systemd, or seek alternative solutions. Maintaining the status quo is unlikely to be feasible.

Learning from the elogind Precedent It’s worth noting that similar situations have occurred in the past. For instance, systemd-logind, originally part of systemd, was later separated into an independent daemon called elogind. This allowed distributions that don’t use systemd to still benefit from desktop environments dependent on systemd-logind. According to Vovk, the Flatpak team intends to “pay significant attention” to users and distributions that don’t use systemd. This suggests that they may consider a similar approach to elogind—separating out systemd-appd as an independent daemon to make it usable in non-systemd environments. However, as the elogind case has shown, such separations are technically challenging and carry significant maintenance burdens. There’s also no guarantee that all features will be available at the same quality level.

Key Point to Note: It’s Still in the Planning Stage The most important thing to remember is that the proposals discussed in Vovk and Wick’s presentation are still in the planning phase. Not a single line of code has been written yet. As such, all elements of the plan are subject to change, and the final outcome could differ significantly depending on the progress of development over the coming years. In open-source projects, there is often a substantial gap between planning and implementation. Community feedback, technical feasibility, and coordination with other projects will all play a role in shaping the final design.

Ripple Effects on the Linux Ecosystem Currently, systemd is the init system of choice for the vast majority of major Linux distributions. Its influence extends beyond just initialization to include components like logging, network management, and user management. Flatpak’s dependency on systemd would extend its influence further into the realm of application distribution and execution platforms. While this could be seen as a natural extension of the systemd ecosystem, it also risks reigniting long-standing debates over whether systemd exerts too much control over the Linux ecosystem.

Reactions from the Developer Community This announcement has sparked intense debate within the Linux community. Proponents of systemd praise the convenience and consistency that a unified service layer could bring. On the other hand, stakeholders from non-systemd distributions and advocates of the Unix philosophy, which emphasizes doing one thing well, have voiced concerns. At the very least, the Flatpak development team’s stated commitment to “consideration”

should be seen as an acknowledgment of their intention not to abandon non-systemd users entirely.

Future Prospects The development of Flatpak Next is expected to unfold over the next few years, with numerous challenges to address. These include designing systemd-appd, ensuring compatibility with existing Flatpak 1.x applications, and finding solutions for non-systemd environments. It’s worth noting that Flatpak is not the only player in the Linux application distribution space. Competitors like Snap and AppImage offer alternative solutions, each with its own design philosophy and strengths. How this move toward systemd dependency will influence user choices remains to be seen. What’s certain for now is that the role and impact of init systems in the Linux ecosystem will once again become a hotly debated topic.