About AppImage on openSUSE Asia Summit 2017

There are two AppImage talk on openSUSE Asia Summit 2017. The first one is my talk, Flatpak & AppImage Usage on openSUSE. Which One Suitable for openSUSE Users? and the second is Using OBS to Build Containerized Application Image . At the last day of summit, Simon Peter write an issue about my topics. He give me some additional information that i’m probably missed about AppImage.

No software necessary to install a packageYes. Actually, with AppImage, software is never “installed”. The downloaded format is the same as the executed format. This an advantage
Shared runtimesNo. By design, AppImage allows no dependencies other than what can be expected to be part of all target systems. Like with apps for iOS, everything is either in the OS or in the app. This removes the need for dependency management on the user’s end. This an advantage
SandboxingYes. AppImage works with various sandboxes such as Firejail. It is not hardcoded toward any particular sandbox. This an advantage
Repository supportNo. Users can just download and run one file without having to manage repositories. This an advantage
Central repoNo. By design, AppImage is meant to be decentral, so there are no “gatekeepers”. An author can put an AppImage onto the download page just like an EXE or DMG. This an advantage
UpdatesYes. AppImage supports binary delta updates where you only download the few MB that actually have changed from version to version. Additionally, there is AppImageHub which lists tested AppImages, and that is managed as a GitHub repository to which everyone can contribute. This an advantage

Actually, those table above came from this page but the information is obsolete so that Simon gave me clarify of the features that i claimed missing from AppImage.

The other AppImage guys also reminds me about some material that i’m put into the slide from Simon’s slide at openSUSE Conference 2017. Now the slide updated with url source.

Flatpak and AppImage usage on openSUSE from Kukuh Syafaat