Skip to content

Feature Request: Provide Linux distribution formats (Flatpak / AppImage) #208

@cuervolu

Description

@cuervolu

Is your feature request related to a problem? Please describe.
Currently, Linux users primarily have access to a .deb package in the releases. While this is helpful for Debian/Ubuntu-based distributions, it leaves out a significant portion of the Linux ecosystem (Fedora, Arch, OpenSUSE, etc.).

For an application that aims to be a "Store," the absence of a universal, native-feeling distribution format creates friction. Users on non-Debian systems must manually manage the execution of binaries or JARs, which lacks system menu integration and automatic updates.

I've noticed that there is already some ongoing discussion regarding AppImage support in issues #161 and #162, which is a great step forward for portability.

Describe the solution you'd like
I would like to see official support for universal Linux distribution formats, specifically Flatpak (ideally published on Flathub) to complement the AppImage efforts and reach all distributions.

Since this is a Kotlin Multiplatform project, a great reference for distributing a Compose Multiplatform app on Linux is FeedFlow:

Describe alternatives you've considered

  • Current .deb package: Only works for a specific subset of Linux users.
  • Manual Binary Execution: Lacks desktop integration (icons, launcher).
  • Native Packages (RPM/Arch): Too much maintenance overhead compared to a single Flatpak/AppImage.

Additional context
Given that GitHub Store functions as an installer/manager for other binaries, the Flatpak Sandbox presents a unique challenge:

  1. Permissions: The app would require specific permissions (e.g., filesystem=home or filesystem=host) to manage and execute binaries on the host system.
  2. Why Flatpak anyway? It ensures the exact JRE/JBR required is bundled, avoiding rendering issues across different distros, and provides a centralized update stream.

I would be more than happy to help test or troubleshoot any Linux-specific issues during the implementation of these formats.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions