appimaged VS AppImageKit

I can't speak for others but I use appimaged still, which monitors the ~/.local/bin directory and automatically adds the shortcut to my application menu in Ubuntu-Mate.

I found out that there is a daemon for it ([appimaged](https://github.com/AppImage/appimaged)) but it doesn´t seem to be supported anymore. The site points to an [alternative codebase](https://github.com/probonopd/go-appimage) but it is not clear (at least to me) if it is stable or not.

Hi u/tnc68, I use AppImageLauncher on Ubuntu to handle this automatically as it will handle the installation of new updates and preserve/generate desktop app icons for each update. Some users may prefer appimaged (as u/ProgsRS mentioned), but I currently do not use it.

There seem to be more than one solution to integrate AppImage with the desktop and still somehow a work in progress. The original version of appimaged is deprecated for a newer version written in go. There is also AppImageLauncher, which is not entirely the same as appimaged, but maybe does what you need. Docs: https://docs.appimage.org/user-guide/run-appimages.html#integrating-appimages-into-the-desktop

What you're looking for sounds like AppImages (https://appimage.org/) . I have only used them while downloading games from itch.io, etc. (since i prefer package managers) but they seem to work out of the box on popular distros.

Ideally a new instance of the application is installed for each user. This also provides better isolation if one user upgrades/removes/breaks their application instance. I, for one, have really come around to the AppImage model [0] in the last couple of years.

[0] https://appimage.org/

I found a similar issue on github and tried this solution but still getting the same error .

There is AppImage[1], which packs a lot of stuff into a SquashFS filesystem, appends it to the executable, so everything is in one file.

[1] https://appimage.org

Nah i think yall just hating appimage. Real gold standard.

Although I haven't used plugins feature myself yet, this does sound like the perfect use case for them. Not every patient needs to access every single source. With plugins you can load only the source (or few sources) that they actually need. You can still use something like https://appimage.org/ to give them "a single binary", but will actually contain your slim binary and all the plugins.

```dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information```

This doesn't look like a squashfs image. Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage  if you run it with the --appimage-extract option.  See https://github.com/AppImage/AppImageKit/wiki/FUSE  for more information open dir error: No such file or directory

appimages. Appimages are similar to flatpaks, exept that they are a file you download and double click to run. Think of them as portable softwares like windows has (portable apps). They are sandboxed too. You can learn more about appimages here