Is there any reason an AppImage couldn't use a similar method to Obtainium to download and install updates for itself (automatically or when promoted)? Maybe with an option to specify a different source of updates.
The administrativia of keeping AppImages up-to-date is one reason I almost never use them. Despite liking the idea better than FlatPak and Snaps.
@strypey I've had this same thought about AppImages. I think it should be pretty easy to build and ship AppImages via F-Droid. The tricky part is whether there is good standardized metadata in AppImages. With Android and APK, the system enforces a number of key properties: a globally unique Application ID, a Version Code integer to determine which is the newer APK, only one APK per Application ID can be installed, etc. These come from the OS, so it could be tricky to handle with AppImage
@strypey I only know about other applications to keep AppImages updated. I'm not really active in that section, sorry.
@eighthave
> I think it should be pretty easy to build and ship AppImages via F-Droid
My suggestion was focused on how to make desktop AppImages securely self-updatable. So this is a totally different idea, but an intriguing one. Especially in the context of Goggle trying to lock-down Android and centrally control who can develop software for it;
https://forum.f-droid.org/t/google-will-require-developer-verification-to-install-android-apps-including-sideloading/
> The tricky part is whether there is good standardized metadata in AppImages
Anyone know about this? @fdroid @IzzyOnDroid