As a Linux developer, I see it as very necessary that this version be in Flatpak or at least in Flatpak beta.
Same here, and many others.
Vote for the idea on Mozilla Connect:
Follow the issue on the bug tracker:
Also discussion on flathub:
2 Likes
Sadly, there hasn’t been an update on the bugzilla ticket in years.
The only blocking bug is “[flatpak] runme.sh should allow to use custom app id for other release branches”
and it appears stalled until a new person takes it up
1 Like
Installation is a roadbump for many devs. If firefox is serious about market share, they need to offer a fast way for devs to install their tools and test it.
I had the patience now, but I don’t think I’m going to spend the time to download a tar and update it next time.
2 Likes
There are now some different blockers listed which make more sense. It is actually due to an upstream problem with Flatpak only allowing one additional channel (beta), per application, and the ticket to resolve this was closed as Not planned:
There is a proposal to use per-branch app id’s, but a better idea IMHO is what I proposed in the comments there:
Since there are actually four channels (Stable, Beta, Developer, and Nightly), and beta is already the official Flathub ‘beta’ channel for Firefox main, what if we instead just released Firefox Developer Edition on Flathub, with Nightly as the so-called ‘beta’ channel for it? This makes sense because Dev edition is based on beta, and nightly a version ahead of it.
It also has the benefit of exposing the stable edition for most users, and the developer edition for developers, while making the least stable versions not as prominently advertised to general audiences.
There seems to be some pushback, but hopefully more people agree with my suggestion 
1 Like