Appimages totally suck, because many developers think they were a real packaging format and support them exclusively.
Their use case is tiny, and in 99% of cases Flatpak is just better.
I could not find a single post or article about all the problems they have, so I wrote this.
This is not about shaming open source contributors. But Appimages are obviously broken, pretty badly maintained, while organizations/companies like Balena, Nextcloud etc. don’t seem to get that.
AppImages are great and easy to use and they can be very easily archived. Today I tried to archive a Flatpak package (yuzu) and it was a pain, complicated and gave up in the end. I end up archiving multiple versions of the AppImages and continue using the Appimage for this emulator. Also sometimes Flatpaks do not work correctly, and I (and any other user) have to figure out what settings and configuration, rights and other stuff is needed to setup with Flatseal. Recently I solved the open links issue with Flatpaks, and found out a certain portal was required to be installed. Also sometimes the theming is not correct too.
All in all, I use Flatpak still and AppImages too, each for their own reasons. The lack of repositories and not needing an installation for being functional is not a problem with AppImages, because that’s the entire point of it. They can be automatically generated and ready for download, regardless of any repository, directly on Github from the developers. There is even a program, RPCS3 (a ps3 emulator), which can check and update itself and list all changes since last update.
If you download AppImages from shady places, then off course its shady and insecure. Just like installing any software without knowing what you are doing is insecure. So that’s not a point against the format itself. The argument “Duplicated libraries” is hilarious, if we speak about AppImages vs Flatpak, because Flatpak has duplicated drivers (especially with Nvidia, I know how bad it is because I had Nvidia cards before) and desktop environment versions, just because certain versions of the application needs it.
I don’t understand these evangelism for packaging formats. Flatpak, AppImage, native system packages and other formats have their own uses and are all useful and not bad.
What do you want to achive with archiving, because of a potential takedown by Nintendo?
Just for your purpose you could just keep it installed and probably block it from getting updated. I am sure you could also backup the .flatpak file somehow, and all the dependencies would still be accessible.
flatpak runtimes are pretty bloated, when you use different versions etc. And its bad that you cant only use Flatpak, currently. But locally they use deduplication, so GNOME, KDE and Freedesktop.org will share at least some libraries.
But for sure, it may not be the best library management there is.
Its not evangelism, there are developers that thinl Appimage is an acceptable format and only support that. I dont know but guess some licenses prohibit user repackaging as Flatpak, so you have to stick with that pain.
The deduplication is only for one specific version, even if its installed on my operating system already. AppImages do not include the entire KDE system. And Flatpak will install multiple versions of drivers (Mesa in example) and other dependencies. While this is exactly what Flatpak was designed for and there are good reasons for, it is important to understand that was counter arguing your argument against AppImages for being bloated. Both approaches are good in their own way, depending on what you want or need.
The backup of Yuzu Flatpak was just a current example why someone would want do that. There can be any reason to backup specific software versions, which is not the topic of today. The topic is, that with Flatpak its a mess to backup and restore. Yes, you can copy the configuration and installed binary files, but that does not work on any other computer. You can backup the key and other important files as well, but then its complicated to restore them as well, that I just gave up. It’s probably not impossible, but not straight forward; a bad user experience.
Meanwhile I can just download an AppImage and copy the file and its archived. Done. In multiple versions. No extra software, knowledge or complicated dance to do this very simple and important task.
Good points.