If KDE Discover is the sprawling, all-inclusive supermarket of Linux software centers, GNOME Software is its curated, minimalist boutique. As the default graphical “app store” for the GNOME desktop, it serves the same fundamental purpose: to simplify finding, installing, and updating applications for millions of users on distributions like Fedora, Ubuntu, and Debian.
However, GNOME Software is built on a different, more opinionated philosophy. It isn’t just a neutral frontend; it’s a driving force behind the adoption of modern, sandboxed packages. It has firmly embraced a “Flatpak-first” ideology, shaping how users interact with their applications. This guide explores the depths of using GNOME Software, its powerful integrations, its controversial omissions, and its persistent challenges in 2025.
The Philosophy: An “App Store,” Not a Package Manager
Like its KDE counterpart, GNOME Software is not a package manager. It is a high-level abstraction layer. It doesn’t replace powerful command-line tools like DNF or APT; it simply provides a clean, safe, and user-friendly interface to manage them and other software sources.
The entire design philosophy, consistent through the GNOME 40+ series, is built around simplicity. It intentionally hides complex details like package dependencies, libraries, and granular versioning. The goal is to provide an experience akin to a mobile app store: you search for what you want (e.g., “photo editor”), you see a list of applications, you click “Install,” and it works. This focus on “applications” rather than “packages” is central to its design.
The “Flatpak-First” Approach: A Bet on the Future
The single most important thing to understand about GNOME Software in 2025 is its deep and fundamental commitment to Flatpak. While Discover treats all backends more or less as equals, GNOME Software actively prioritizes the Flatpak format.
- Deep Flathub Integration: GNOME Software is designed to work seamlessly with FLATHUB, the de-facto central repository for Flatpak applications. On most distributions, Flathub is pre-configured or easily added, instantly giving users access to thousands of apps.
- Source Prioritization: This is key. When an application is available from both a distribution’s native repository (e.g., Fedora’s RPMs) and Flathub, GNOME Software will often default to the Flathub version. It may still offer a dropdown menu to select the source, but the Flatpak is frequently presented as the primary choice.
- Why Flatpak? The GNOME project’s reasoning is clear: security (sandboxing), stability (apps bundled with their own dependencies), and developer convenience (a single package that runs on all distros).
- Permissions at a Glance: A major benefit of this integration is that GNOME Software clearly displays the permissions a Flatpak is requesting (e.g., “Access to your Home folder,” “Access to the network”), giving users transparent control over their security.
What About the Other Backends?
While Flatpak gets the spotlight, GNOME Software is still a unified hub for managing your entire system. It relies on several other backends running quietly in the background.
PackageKit for System Packages
For all traditional software—the .rpm packages in Fedora or .deb packages in Debian/Ubuntu—GNOME Software uses the PACKAGEKIT PROJECT daemon. This is the backend that allows it to:
- Find and install applications from your distribution’s official repositories.
- Manage core system updates (like kernel updates, new drivers, and system libraries).
PackageKit is a crucial, if somewhat invisible, component. It’s also, unfortunately, the source of many user complaints about GNOME Software’s performance, as its process of checking for updates can be slow and resource-intensive.
Seamless Firmware Updates via LVFS
One of GNOME Software’s greatest strengths is its flawless, “just-works” integration with the LINUX VENDOR FIRMWARE SERVICE (LVFS). Through the fwupd daemon, GNOME Software automatically scans your hardware—motherboard BIOS/UEFI, SSDs, Thunderbolt docks, and peripherals. When an update is available from a vendor like Dell, Lenovo, or Logitech, it appears in your “Updates” tab alongside your regular software, allowing for easy and critical hardware-level updates.
The Big Omission: Where is Snap Support?
This is the most significant difference when comparing GNOME Software vs. KDE Discover. The upstream, default version of GNOME Software—the one you’ll find on Fedora, openSUSE, and most other non-Ubuntu distributions—does not support Snaps.
This is a deliberate, philosophical choice. The GNOME project has thrown its weight behind Flatpak as the single, standard universal package format.
The exception, of course, is Ubuntu. Canonical (the company behind Ubuntu) maintains its own patched version of GNOME Software that not only includes support for its own SNAPCRAFT STORE but actively prioritizes Snaps. This has created a fragmented experience: using GNOME Software on Ubuntu is fundamentally different from using it on Fedora.
The Persistent Challenges: Performance and Search
Despite its clean design and modern approach, GNOME Software is not without its long-standing problems. For years, users have reported two main issues:
- Performance: The application can be notoriously slow to load, especially on startup. It often presents an empty window or a spinner for many seconds (sometimes minutes) while it waits for PackageKit to refresh its package cache in the background.
- Search Accuracy: Search can be a hit-or-miss affair. It sometimes fails to find applications that are known to be in the repositories, and the relevance of its search results has often been criticized.
While the latest GNOME releases, including GNOME 49 (September 2025) and its predecessor GNOME 48, have brought significant performance optimizations to other parts of the desktop (like animations and core apps), these core issues with GNOME Software itself remain a common pain point for many. On the bright side, for Fedora users, the ongoing transition to DNF5 is expected to resolve a major related issue: the duplication of package caches between the command line (DNF) and GNOME Software, which will save disk space and improve consistency.
The Verdict: An Opinionated, Modern, and Flawed Hub
GNOME Software is the perfect embodiment of the GNOME 40+ philosophy: it’s simple, elegant, and highly opinionated. It is not trying to be a “do-everything” tool like Discover or a powerful package-wrangling tool like Synaptic.
It is a forward-looking “App Store” that has placed a firm bet on a Flatpak-powered future.
For its intended purpose—providing a secure, simple way for mainstream users to find and install sandboxed applications and manage critical system/firmware updates—it excels. But its stubborn performance issues and the deliberate, fragmented exclusion of Snaps make it a tool that is as frustrating as it is functional.
What are your thoughts on GNOME Software? Do you appreciate its “Flatpak-first” minimalism, or do you find its performance and lack of Snap support frustrating? Let us know in the comments!