The flatpak "app" system has always felt like amateurish techbro crap to me, but today I finally put my finger on why.
The website is loaded with how-tos for installing it & packaged applications ("apps"), but there's not even a hint of how to maintain, manage, remove, or update them.
It has a set of halfway decent manpages that *do* say how to do these things, but there's literally zero reference! You have to just know they exist, & you have to just know `man flatpak` is how you start.
Okay, so there's a technicality. I could also install Firefox from the Android subsystem's Google Play app, but it would be the phone/tablet version, not a desktop/laptop version, which means the UX, UI, & add-on ecosystem are significantly restricted.
@arielmt assuming the distribution you're on has manpages and the software to render them installed by default!
@arielmt i never liked it because of how much resources it took to do anything and barely ever worked for me, but i wonder if those things improved since the last time i tried
i ended up just compiling things from source
@arielmt honestly between snap and flatpak i think both are egregious mistakes and the linux development community needs to use a "non-free" computer again to figure out what is it that "normal" people expect of them
The only reason I use flatpak at all is because, in Google's tightly controlled walled garden of ChromeOS, it's literally the only way to install Firefox.
Mozilla Support, "Run Firefox on ChromeOS": https://support.mozilla.org/en-US/kb/run-firefox-chromeos