Skip Navigation

Don't use Appimages (a writeup about all the reasons they are a pain for users)

github.com GitHub - trytomakeyouprivate/dont-use-appimages: Appimages are an insecure packaging system with very limited use cases. Please use Flatpak instead!

Appimages are an insecure packaging system with very limited use cases. Please use Flatpak instead! - trytomakeyouprivate/dont-use-appimages

GitHub - trytomakeyouprivate/dont-use-appimages: Appimages are an insecure packaging system with very limited use cases. Please use Flatpak instead!

Appimages totally suck, because many developers think they were a real packaging format and support them exclusively.

Their use case is tiny, and in 99% of cases Flatpak is just better.

I could not find a single post or article about all the problems they have, so I wrote this.

This is not about shaming open source contributors. But Appimages are obviously broken, pretty badly maintained, while organizations/companies like Balena, Nextcloud etc. don't seem to get that.

178

You're viewing a single thread.

178 comments
  • AppImages can be signed. Flat pak is the lesser option for security

    • Explained in a other comment how a pain it is to verify such a signature.

      Is that stored in the appimage file?

      I find it funny how flatpak neglectors always spell it wrong

You've viewed 178 comments.