Overview

This FAQ digs into naming, usage quirks, and common confusion points.

1. Do the YAML files in this repository prioritize Nitrux?

Yes. The curated YAML files in this repository are designed to create AppImages that work reliably in Nitrux, i.e., AppBoxes.

These AppImages are guaranteed to work in Nitrux but are not guaranteed to work in other Linux distributions.

While we may test these AppImages in other environments (e.g., via Distrobox containers), doing so is optional and purely for formality.

2. Is the goal of NX AppHub Apps to provide AppImages for all Linux users?

No. NX AppHub Apps is not a universal AppImage distribution service.

This project aims to provide AppBoxes—AppImages tailored for Nitrux—using curated YAML definitions. Compatibility with other distributions is incidental, not intentional.

Supporting every Linux distribution is not within this project's scope, even if AppImages themselves are broadly compatible.

3. Can I contribute a YAML file for an AppImage that also targets other distributions?

Yes, as long as the resulting AppImage also works in Nitrux.

NX AppHub Apps accepts contributions that may support other Linux distributions, but Nitrux compatibility is a requirement. AppImages that fail to run properly in Nitrux, even if they work elsewhere, will not be included.

4. Why YAML files don't just download existing AppImages or other portable binaries from upstream developers or third-parties?

We don't do that because that's not the goal of NX AppHub Apps.

This repository provides YAML build definitions that assemble AppBoxes—AppImages designed to work reliably on Nitrux by staging .deb packages into clean, reproducible AppDirs.

Existing AppImages and other portable programs (e.g., tarballs, static or bundled binaries) are often built from source code by their developers/maintainers/packagers; for evident reasons, we do not know about their build processes. Additionally, these files do not prioritize Nitrux.

By contrast, AppBoxes are:

• Built consistently from known prebuilt .deb packages.
• Provide a Nitrux-first way to use AppImages.
• Fully reproducible via nx-apphub-cli using declarative YAML.

5. How is NX AppHub Apps different from other AppImage stores or catalogs?

Unlike traditional AppImage catalogs or centralized app stores, NX AppHub Apps doesn't distribute binaries or act as a link aggregator.

Instead, it distributes build specifications (YAML files) that let users build the application using trusted upstream Debian-based repositories.

This approach removes:

• The need to trust an unknown third party to build and host binaries
• The maintenance burden of hosting, mirroring, or snapshotting large binary archives
• The risk of binaries becoming outdated, broken, or compromised without user visibility