[probonopd]

Repository: https://github.com/bobbycomet/Appify

Built for Windows switchers. I built Appify after getting fed up with manually scripting PWA builds. It’s a streamlined automation tool that turns web apps into optimized desktop experiences in seconds.

• Stars: 6
• Latest release: v3.0.4 (2026-08-18T20:10:55Z)
• AppImage asset: Appify-3.0.4-x86_64.AppImage
• License: GPL-3.0

Found by .github/workflows/discover-apps.yml, which looks for GitHub
repositories that publish AppImages but are not in the catalog yet. This
entry was not tested by a human; please review it before merging.

Possibly not from the application's authors: the README says "not official" (label not-upstream). Please check whether the catalog should list this AppImage, or rather one from the application's own project.

[github-actions]

❌ Test failure

@bobbycomet: this pull request adds the AppImage from your GitHub repository to the AppImage catalog; the test reports the following. Could you have a look?

Compatibility: not self-contained: uses the C library of the system

• The application quit or crashed right after starting. The error below usually shows why.

First error in the log:

ERROR: The application exited within 11 seconds instead of showing a window

Commit 2c6cc24. Full log

[bobbycomet]

/retest

[github-actions]

✅ Test passed

Please check that the screenshot shows the application's main window.

Appify

Tested:

• Appify-3.0.4-x86_64.AppImage from release v3.0.4.1

Compatibility: not self-contained: uses the C library of the system; references glibc 2.34

Warnings:

• The window is mostly dark, so the application seems to start in a dark theme although the test system is not set to dark mode. Please use a light mode by default and use the dark theme only when the system is configured for dark mode (e.g. the GTK/Qt or theme setting) or the user chooses it in the settings.
• The AppImage contains no update information, so users cannot update it with AppImageUpdate or similar tools. Please consider embedding it when building the AppImage (e.g., appimagetool -u) and publishing the .zsync file next to the AppImage; see https://docs.appimage.org/packaging-guide/optional/updates.html

Commit 2c6cc24. Full log

[bobbycomet]

Appify has a sister tool for updates. https://github.com/bobbycomet/GriffinUpdater

It updates Appimages, deb files, and archive packaged tools like Godot. So, it does have an update path, as I did not go the conventional route, as I am building an entire platform with my tools.

[probonopd]

Why not use https://docs.appimage.org/packaging-guide/optional/updates.html? It has zsync based delta updates and is part of the AppImage specification. Why reinvent the wheel?

[probonopd]

Do you know why it choses dark mode on my system? I have not set up dark mode.

[bobbycomet]

So, the reason I do not use zsync is because I am making a platform, and while I do get the benefits of zsync, it was just never part of the plan, as all tools are to support the Griffin and CUXL applications I build. AppImages tools that require zsync do not handle multiple packaging forms, and that is why I built the Griffin Updater, to handle those differences. It is not so much reinventing the wheel, but simplifying a step for the end user, as I build with Windows switchers in mind. They do not care about zsync or different philosophies, they just want it to work.

As for the dark mode, I coded it to start with dark mode in all of my applications UI. It is not because I dislike light mode, but dark mode is popular with users in applications, so I decided to have the app start in it, and they can change to light mode if they rather. However, if you mean dark mode in the PWA Appify creates, that should not happen, and I can investigate that, if that is the case.