AppImage files are handy when you don’t want to install the package or you want to have different versions of the package. AppImage files are in containerized format and suit me with fast changing packages like Obsidian, where I can keep older versions in case of issues with all my community plugins.
Obsidian is in AppImage format and they release new versions very often and I have a bunch of third-party community plugins that may not always play nicely with their latest release. You can install Obsidian from the AUR, but it’s maintainers are way behind Obsidian’s official site, and as this is such a mission-critical tool for me, that I can’t be dealing with bugs from outdated versions.
If you don’t mind having all your AppImage files in one folder then you can navigate to them in a file manager, but if you have a lot of them, then it would be good to have them in a menu system.
@dalto pointed out a neat companion tool which integrates AppImages into your menu system called appimagelauncher in the AUR by creating a .desktop in the menu. I use Plasma, so I don’t know about other DE’s, but I suspect they work the same.
@ricklinux started an interesting thread in 2020 which talked about AppImage Rather than revive an old thread, which talked abut audio file tagging with kid3, I thought it was time for a fresh thread.
I would be interested if there is much interest in AppImage and anyone with experience of with AppImage Installer, another package in the AUR.
Does anyone have experience with know about AppImage Installer and whether it should be used.