zap VS AppImageUpdate

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.

There's an updater for appimages https://github.com/AppImageCommunity/AppImageUpdate

AppImages can contain update information (and even support partial updates using zsync), check out https://github.com/AppImage/AppImageUpdate.

https://github.com/AppImage/AppImageUpdate this only works if the application has information regarding where to fetch the update from...

It would be very nice and handy if we could easily update Tutanota Linux desktop app. Luckily, since it is packaged as an AppImage, there's an easy-to-integrate utility available just for that.

It's not centralised, not like Snap with SnapCraft, not even like Flatpak with it's 'not technically but kinda is in practice' Flathub repository. Anyone can make an AppImage, anyone can host an AppImage, anyone can download and run an AppImage, anyone can implement AppImage integration in a distro, and there's even a nice system for automatic updates for AppImage which again is nicely decentralised.

Some have built-in. some not. Btw I considered AppImageUpdate , but it would become re-install a full new app

The fact is that the delta update system via Zsync and appimageupdatetool are real solutions to the problem, but too many developers do not implement it in their AppImage, myself included.

Btw, regarding Flatpak, I've had multiple issues related to mouse cursor, fonts, and local folder access - all related to the sandboxing of apps, all resolvable, but potentially a problem for a non-technical user. I've had much better experiences with AppImages, but I don't know if they have a graphical app store like interface; even the AppImageUpdate idea is still catching on.