{
  "id": 11954589,
  "title": "Flatpak from the CLI sucks",
  "url": "https://urgent.news/2026/10/04/flatpak-from-the-cli-sucks",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-04T15:21:34.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://kowalski7cc.xyz/blog/flatpak-from-the-cli-sucks/"
  },
  "original_language": "en",
  "account": "Flatpak, an innovative package manager, has transformed how Linux applications are distributed and installed. Unlike traditional package managers, Flatpak eliminates the need for users to manually download and install binaries and libraries, instead bundling all necessary dependencies within a single, layered package. This approach not only streamlines the installation process but also enhances security by isolating applications within a sandboxed environment.\n\nDespite its growing popularity, Flatpak has faced challenges, particularly regarding command-line interface usability. While applications such as flatpak-builder exist for building Flatpaks, developers often avoid packaging CLI-only tools due to perceived difficulties. When installed as a Flatpak, even basic commands become cumbersome, requiring longer syntax, the full app id, and disabling the filesystem sandbox.\n\nMoreover, the flatpak run command, intended to simplify application execution, presents its own set of complications. The addition of --file-forwarding, meant to permit file access within the sandbox, introduces another layer of complexity without resolving the overarching issue of command length. Furthermore, the command fails to accommodate directories or the creation of non-existent files.\n\nWindows, too, has grappled with similar challenges related to application distribution and sandboxing. In response, Microsoft introduced the Windows Store and AppContainer technologies, enabling developers to distribute software in a sandboxed format. While these advancements provided a means for distributing applications, the process was not without its complexities, notably for Win32 applications attempting to migrate to the new platform.\n\nTo address the usability issues surrounding application execution, Windows introduced the Desktop Bridge, allowing Win32 applications to be packaged in the APPX format and run more easily from the command line. However, developers must update their application manifests to enable this functionality, adding another layer of complexity to the process.\n\nAs Linux and Windows navigate these challenges, it remains to be seen how they will balance the need for secure, sandboxed application distribution with the usability demands of command-line users.",
  "summary": null,
  "key_points": [
    "Flatpak simplifies Linux application distribution by bundling dependencies.",
    "CLI usability for Flatpak is challenging due to long syntax and additional commands.",
    "Windows Store and Desktop Bridge offer sandboxed distribution but add complexity."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}