What's the Latest way to distribute as Flatpak?

[Keshav-writes-code]

So, i wanted to distribute my app as a flatpak. What's the new way of doing it. the old guide has probably been removed here

[FabianLars]

tauri-apps/tauri-docs#2948

[karan5028ji]

The official guide is live again and updated: https://v2.tauri.app/distribute/flatpak/

There is still no built-in --bundles flatpak target, so the current recommended flow is: build a .deb, then wrap it in a Flatpak manifest that repackages the extracted files into /app. Summary:

1. Tools & runtime

sudo apt install flatpak flatpak-builder        # or pacman/dnf/emerge equivalents
flatpak install flathub org.gnome.Platform//46 org.gnome.Sdk//46

The GNOME 46/47 runtime ships every dependency a stock Tauri app needs.

2. Build a .deb

npm run tauri build -- --bundles deb

(or set "targets": ["deb"] under bundle in tauri.conf.json).

3. AppStream metainfo (required for Flathub)
Create org.your.id.metainfo.xml, and bake it into the deb so it lands in the Flatpak automatically:

"bundle": {
  "linux": {
    "deb": {
      "files": {
        "/usr/share/metainfo/org.your.id.metainfo.xml": "relative/path/to/org.your.id.metainfo.xml"
      }
    }
  }
}

4. Manifest — a flatpak-builder YAML with runtime: org.gnome.Platform that extracts the deb and installs the binary, .desktop file, icons and metainfo into /app. If your app uses a tray icon, add to finish-args:

finish-args:
  - --socket=wayland
  - --socket=fallback-x11
  - --device=dri
  - --share=ipc
  - --talk-name=org.kde.StatusNotifierWatcher
  - --filesystem=xdg-run/tray-icon:create

5. Build & test locally

flatpak-builder --force-clean --user --disable-cache --repo flatpak-repo flatpak flatpak-builder.yaml
flatpak run <your.id>

6. Submit to Flathub — fork flathub/flathub, add your manifest, open a PR against the new-pr branch.

One tip: for an open-source app Flathub reviewers prefer a source-based build (flatpak-node-generator + flatpak-cargo-generator to vendor your npm/cargo deps) over shipping a prebuilt deb — the docs cover both the open-source and closed-source variants under separate tabs.

[FabianLars]

One tip: for an open-source app Flathub reviewers prefer a source-based build (flatpak-node-generator + flatpak-cargo-generator to vendor your npm/cargo deps) over shipping a prebuilt deb — the docs cover both the open-source and closed-source variants under separate tabs.

This is more important than just a tip. They often decline your submission if you're using the .deb for an open source app!

There is still no built-in --bundles flatpak target

And i doubt there ever will be.