zap VS AppImageLauncher

Integrate zap with that repo and make it official. It will automatically download the appimages inside a directory 'Appimage'. You can move them anywhere else ONLY if it has a directory named 'Appimage'. In this case it is moved to an external usb.

Personally, on a debian based distribution I would either use the AppImage (you could even use something like zap to manage its version). Or, the solution I would and have personally used is to compile it from source. I am a developer, so I am biased, but the instructions are very simple and clear so it should be pretty easy to do.

That said, there is Zap.

Tho bread is github focused which is a big drawback as many software aren't on github, i discovered this program Zap Which was a appimage package manager like AM or bread but it's far much better than mine.

If you can download and install software from the web (which you also can do with debs and rpms btw), you can create a package manager to automate that from the terminal. You either trust a project or you don't, and if your don't the package format makes no difference.

NOTE: I don't know when and if to add new AppImages from the main catalog, also because a part of them is mostly broken and out of control. The AppImage packages compiled and managed by "AM"/AppMan are new AppImages that use scripts that also allow constant updating and recompilation from scratch, as if they were installed from AUR, using more reliable sources (official repositories for Debian and derivatives) . If you are interested more to the applications made available officially from the official AppImage.GitHub.io catalog, I suggest you to use Zap, Bread or the aforementioned Appimagedl. All these amazing utilities can be quickly installed via "AM" or AppMan.

Every file that you want to execute has to be in your environment PATH. I would also advise to put symlinks and personal executables in ~/.local/bin and put that to your path. Since your user has ownership over that directory, you won't have any probs with permissions that may or may not occur at all. Since we're talking about AppImage files, you might also want to take a look at AppImageLauncher which does a pretty good job at creating entries for your Desktop Menu for the AppImage files that you install to your system.

I think it's safe to install it directly as it stores everything in a single directory. For AppImages there is also AppImagePool + AppImageLauncher (can be installed rootless, useful for better integration of appimages).

This reminds me of a prettier version of AppImageLauncher. Is there also an "Uninstall" option in the right-click menu of the app launcher?

I'm using AppImageLauncher on Fedora.

"... I recall that this was related to an issue with most Electron apps, wherein the AppImage cannot be integrated with the desktop or the favourites bar. So far we've found that the AppImageLauncher (https://github.com/TheAssassin/AppImageLauncher) helps with getting around this!