If you mention Bazzite, you have to mention Bluefin, right?
Universal Blue—the community-driven toolkit behind both systems—builds them on top of Fedora Silverblue. Technically, they’re distributions, even if they don’t really like to be called that.
The idea is appealing: system, applications, and user data are separated to such a degree that you can genuinely talk about a certain “cleanliness.” Of course, this comes at a price, since it differs significantly from what has been considered standard for decades.
One clear advantage is the update model. System updates can be applied without much anxiety. On the one hand, they’re delivered as cohesive images, which means potential issues may be caught earlier—before they ever reach your machine. On the other hand, you can simply roll back if something breaks. On the next boot, you select the previous working state and ignore the problematic update. That significantly increases post-update reliability—and takes a lot of stress out of the process.
More controversial, at least for some, is the near-exclusive reliance on Flatpaks for applications. The most obvious downside is increased storage usage. On the upside, each application brings along what it needs (aside from shared runtimes), which generally improves reliability. Flatpaks also don’t interfere directly with the base system and are actively maintained. Personally, I like the concept—but the real question is: does it hold up in everyday use?
Another question that immediately came to mind: who is this system actually for? Regular users? If so, why does it sometimes look like a teenager’s bedroom—dinosaurs everywhere and dark wallpapers? Then again, Bazzite exists for gamers, its bigger brother in a way.
We’ll see.
This will be a long-term review on a laptop. Bluefin will be the only operating system used daily. Updates won’t be forced (except once right after installation). The goal is to run the system as intended—with automatic background updates and as little manual intervention as possible.
Installation
The installation was pleasantly straightforward and, above all, fast. The laptop still had around 30% battery left, and even that was more than enough. Realistically, that’s all you need to get started.
The installation process itself is clearly structured and shouldn’t overwhelm anyone who has installed a modern Linux system before. Choose your language, select the keyboard layout, pick the target drive—that’s essentially it. No major surprises, which is a good thing. Installation doesn’t need to be an adventure.
Encryption would have been possible, including the classic LUKS setup. In my case, I decided against it. According to the documentation, automatic encryption is also supported, which could make things even easier for less experienced users—though I didn’t test that myself.
Overall, the installer does exactly what it’s supposed to do: it stays out of the way, finishes quickly, and gets you into the actual system without unnecessary detours. No frills, no needless tinkering.
Start
After the first launch, I have to be fair: I immediately ran updates using the included update app. I wanted the January 20, 2025 version to be my baseline. Starting a long-term test with a potentially outdated image didn’t seem like a good idea.
And one thing was instantly better: Bazaar, the app store I already knew from Bazzite, finally had a significantly improved logo. A good start.
Next came user creation—and that’s where I felt slightly irritated. The selection of user avatars is… let’s call it distinctive. Yes, the dinosaur artwork is technically well done. But most of it is dark, mystical, and in some cases barely recognizable. This was already something I noticed in Bazzite, which is why I use custom images there. I simply don’t identify with barely visible game characters—or, in this case, dinosaurs that all look slightly menacing. Some of the images are so detailed that, in the small circular preview, you can barely tell what you’re looking at.
The boot logo—again, a dinosaur—also feels somewhat out of place to me. In my opinion, Bazzite handles this better with a clear, distinct logo. For Bluefin, a simpler, more stylized emblem would likely be more approachable. As it stands, the design speaks to a very specific audience—but not necessarily to everyone.
On the positive side, as with Bazzite, several of GNOME’s long-standing usability quirks are addressed right away. Dash to Dock is enabled, background app indicators are visible again in the top-right corner, and Blur My Shell comes preinstalled. The latter is purely cosmetic and makes the system feel more modern—technically unnecessary, but visually effective. On a laptop, though, it’s fair to ask whether such effects have any measurable impact on battery life over time.
After the first update and reboot, the wallpaper automatically switched to a winter-themed image—still dark, and still dinosaur-themed. I don’t mind it per se, but it remains a matter of taste.
Beyond that, the system initially presents itself as a fairly standard GNOME setup—just with a few deliberate tweaks meant to smooth out everyday use.
Design
As mentioned earlier, the design feels somewhat divided. Of course, under Linux you can change and customize almost everything—that’s not the issue. But out of the box, Bluefin gives off a vibe that feels more aligned with a teenage audience.
Is that good or bad? Hard to say. But it is limiting. It doesn’t exactly feel like a system you’d install for your mother or grandmother. And even the author—no longer in his twenties—needed some time to adjust.
Design and interface are things people identify with, sometimes almost independently of the technology underneath. And technically, the foundation is still GNOME. Which raises an important question: are the developers aware that such a distinct visual identity also narrows the potential audience?
To be fair, the chosen design language is applied consistently throughout the system. Colors, motifs, and overall styling feel cohesive. This isn’t random or accidental. In that regard, it definitely deserves credit.
Personally, I tend to tweak Blur My Shell a bit—more blur, slightly reduced brightness. The result feels calmer, text becomes easier to read, and white elements stand out more crisply. A small adjustment, but a noticeable improvement.
Apps
Since the app model here relies entirely on Flatpak, a few—let’s call them—trade-offs come into play.
Everything included is up to date and well integrated. Bazaar, already familiar from Bazzite, deserves special mention. It’s clearly evolving quickly and feels modern, clean, and far more polished than what many expect from GNOME Software. The main limitation, however, is obvious: Flatpaks only. Nothing else. No system packages, and no system updates handled here.
At the same time, I have to admit: for me, that’s not a problem. Alongside the standard apps, you’ll find Chrome, Brave, Spotify, LibreOffice, backup tools, GIMP, HandBrake, Steam, radio and music apps, VLC, as well as dedicated clients for Nextcloud and Syncthing. In daily use, I don’t feel like anything is missing. Once your data is in place, you can get back to productive work almost immediately.
Startup times are no longer worth mentioning. Flatpak had its quirks in the past, but today everything feels smooth. I haven’t run into any real issues.
Back to the store itself: Bazaar significantly improves on the sometimes sluggish experience of GNOME Software. It can’t fully replace it, though, since GNOME Software is still responsible for system updates. That’s handled separately here. Perhaps this separation is something GNOME OS might adopt in the future. Either way, I certainly don’t miss GNOME Software’s occasional long loading times.
Bazaar also offers a much better landing page, clearer app descriptions with more detailed information, improved organization overall, and even options to support developers directly. What I still miss, however, is the ability to switch between channels or versions. Take Thunderbird, for example: currently only the ESR release (140.x) is available, while the regular 147 release cannot be installed. The option to install or pin specific versions—or even run multiple versions in parallel—would be welcome. Granted, these are edge cases. But from a technical standpoint, it would be interesting.
One point is particularly important: when you search for an application, you see one version. That’s it. In traditional GNOME Software setups with Flathub enabled, you often end up with two or three variants of the same app—and no average user knows which one to choose. This is where the Flatpak-only approach truly shines. It’s clear, fast, and reduces friction.
In the end, the concept works surprisingly well. It’s consistent, straightforward, and in everyday app usage easily keeps up with Windows or macOS—provided you’re comfortable with the Flatpak-first philosophy.
Work
As is often the case with a system like this, day-to-day use is rather uneventful—and that’s a good thing. It’s based on Fedora with GNOME, so the foundation is solid.
The only noticeable issue is waking from standby. If the laptop has been closed for an entire day, resuming can take a bit longer. It’s not dramatic, but it’s noticeable. During normal daily use, however, the system behaves flawlessly.
For my review, updates were particularly important—alongside the usual factors like speed and stability. Ideally, you shouldn’t really notice them. And that’s exactly what happens here.
After about a month, a notification appears if you haven’t shut down or restarted the system during that time. The reason is simple: system updates are prepared silently in the background but only activated on the next boot. After roughly two weeks, I restarted on my own—without any warning or prompt—and found myself running the January 27th version. Just like that. No drama, no fuss.
In practice, the mechanism works. How it performs over the long term remains to be seen, but even after a month the updates were ready and waiting. The only real adjustment is that you need to restart deliberately every now and then. Then again, that’s true for other systems as well—at least here you do it on your own terms.
The second major topic is the Flatpak-only approach. And honestly, most people don’t care about the underlying technology because they neither understand it nor need to. What matters is that apps are cleanly separated from the system. Updates run automatically in the background, and you usually receive the latest versions directly from the developers.
In theory, that can cause issues—but it doesn’t have to. At least not in my case. Thunderbird, Chrome, Brave, Steam, LibreOffice, Syncthing, and Nextcloud—all installed as Flatpaks—have worked without problems so far. Updates arrive automatically, without requiring attention. That’s convenient, and in the first few weeks it worked very well.
One “downside” remains: Flatpak applications are generally larger than traditional packages, and additional runtimes need to be installed. But realistically, anyone using a reasonably modern system with a 256 or 512 GB SSD won’t notice. This is often debated in theory; in practice, it’s irrelevant for most users. Those still running very old or extremely limited hardware should probably look elsewhere anyway—Debian or a lightweight Xfce-based distribution like Linux Mint would be more appropriate.
After the first month, I can say the system runs pleasantly smoothly. With stock Fedora, I could install minor updates almost daily if I wanted to—and occasionally ran into small issues. That hasn’t happened here so far. That said, the Fedora 43 base has already matured for a few months; most bugs tend to surface early in a release cycle.
Also worth mentioning is ujust. This small terminal utility isn’t for everyone, but when you need it, it’s genuinely useful. It bundles a range of helpful commands for common tasks—such as installing DaVinci Resolve or handling maintenance and update routines. Anyone comfortable opening a terminal will likely appreciate it.
Multimedia
As expected, the standard apps for viewing images and playing videos are included. For anything beyond that, you can install GIMP or a conversion tool from the store if needed—and that generally covers most use cases.
That said, I still miss a few basic editing features in GNOME’s image viewer. It doesn’t need to be a full-blown Photoshop replacement. Simple tools like cropping and rotating (which GNOME already supports), basic color, contrast, or brightness adjustments, and perhaps simple annotations would be enough for many everyday users. As it stands, you end up opening a separate app more often than necessary.
And then there’s the missing “Save As” flexibility. For example, converting a PNG to a JPEG—something that comes up surprisingly often—requires launching GIMP. That feels unnecessarily cumbersome for such a basic task.
As mentioned earlier, DaVinci Resolve is generally usable as well, depending on the hardware. The first real limitation, however, involves codecs. MP4, H.264, and H.265 don’t work out of the box. Footage needs to be converted beforehand—typically to formats like ProRes or DNxHR. That’s entirely possible, but it’s time-consuming and consumes significantly more storage space, depending on quality settings. In my case, the conversion process currently works only via the terminal, which certainly isn’t ideal for everyone.
For simple multimedia tasks, the system is more than sufficient. But anyone working seriously with video will need to deal with the familiar Linux codec limitations—and be prepared to invest a bit more time.
Laptop
Unfortunately, there are occasional short delays when opening the laptop—especially if it has been in standby for a day or more. The system takes a few seconds to become fully responsive again. It’s not a crash or system failure, but it is noticeable. During normal daily use, however, this hardly comes up.
Otherwise, a surprisingly large number of features on my device work right out of the box. From keyboard backlighting to most of the special function keys, there were no unpleasant surprises. Brightness controls, volume adjustment, power-saving features—everything behaves as expected. That’s not always a given with laptops, so it’s definitely worth pointing out.
One particularly interesting feature—and something I consciously noticed for the first time—is the ability to limit charging on my Lenovo Yoga to 80%. Previously, I only knew this setting from the BIOS. Here, it can be adjusted directly within the system settings and easily switched back to 100% when needed. It’s not something you use every day, but it’s a genuinely practical option—especially when you’re traveling or know you’ll need the full battery capacity.
Details like this show that the system isn’t just functional on the desktop, but also thoughtfully implemented for mobile use. If the occasional delay when waking from standby were addressed, the overall experience would feel very polished. That said, the issue may lie more with GNOME—or even the kernel—than with Bluefin itself.
Desktop
The jump from a 13-inch HD laptop display to a 32-inch 4K monitor is always interesting. Suddenly, there’s an abundance of space; everything feels bigger, wider, more open. And overall, it works here without any major issues.
Technically, there’s little to complain about. Scaling, window management, multiple workspaces—everything functions reliably. Most applications behave consistently across both displays. So anyone transitioning from mobile work to a fixed desktop setup doesn’t need to worry. Bluefin—or rather GNOME—handles the shift well.
That said, one thing stands out: the dock’s behavior doesn’t always feel ideal on a large display. On a laptop, auto-hide makes perfect sense because screen space is limited. On a 32-inch 4K monitor, however, there’s more than enough room to keep the dock permanently visible without it getting in the way. A more dynamic adaptation to screen size—or at least a different default setting—would make sense here. Once again, this highlights why extensions like Dash to Dock remain so popular. Many users clearly want more flexibility in how the dock behaves.
A more subjective point, but one that becomes noticeable over time: GNOME’s animations. On a laptop, they feel coherent and appropriate. On a large display, however, they can start to feel slightly exaggerated—especially when opening the overview with the Super key. Movements are larger, more pronounced, and therefore more visually dominant. It’s not dramatic, but over time it can feel a bit tiring.
In the end, the system is perfectly usable in a desktop setup. More screen real estate opens up more possibilities, and the foundation remains solid. A bit of fine-tuning around dock behavior—and perhaps slightly more restrained animations—would make the experience on large displays even better.
Multi-Monitor
Unfortunately, there’s a well-known issue here—most likely GNOME-related: the lack of a proper “memory” function for display configurations. The system seems to forget external monitors almost as quickly as some people forget to brush their teeth.
Technically, using external monitors works without issue. In my case, both a Full HD display and a 4K monitor connect via USB-C without problems. Signal, resolution, scaling—everything functions as expected.
The frustration begins when you want to use only the external monitor. You have to manually switch the display mode every single time. The system doesn’t reliably remember your preference. So whether you’re connecting the laptop to a docking station at home—or simply plugging in a USB-C cable to charge and work on a larger screen—the process starts from scratch.
Over time, this feels disconnected from real-world usage. In 2025, you’d expect the system to recognize: “This monitor, this configuration—that’s what the user prefers.” Windows and macOS have handled this smoothly for years. Here, it still feels unnecessarily cumbersome.
It’s not a deal-breaker. But it’s one of those recurring inconveniences that slowly wear on the experience. And ultimately, it’s exactly these small, repeated frictions that determine whether a system feels truly seamless—or just almost there. Not everyone knows about shortcuts like Super+P to work around it quickly, and they shouldn’t have to.
Games
As expected, games from Bazaar—and of course Steam—run without issues. Installation works as usual, downloads are stable, and updates happen quietly in the background.
Steam itself did take an unusually long time to launch the first time. Really long—several minutes, long enough to make you wonder whether something had frozen. After that initial run, however, everything behaved normally. It was most likely a one-time initialization process.
In my case, the laptop is at best an occasional, low-tier gaming machine. Demanding AAA titles aren’t the focus here. But for casual sessions, it’s perfectly adequate.
Many indie titles available via Flathub or Bazaar are readily accessible and quick to install. As usual, Proton plays a crucial role, allowing a large number of Windows games to run smoothly without extensive tweaking.
Limitations? By Linux standards, hardly worth mentioning. Anti-cheat remains an issue with certain multiplayer titles, as it always has—but that’s not specific to Bluefin; it’s a broader Linux ecosystem challenge. For everything else, it’s simple: install, launch, play.
For a system that isn’t primarily marketed as a gaming distribution, this is impressively well-rounded. Anyone serious about gaming will likely choose Bazzite. But for casual gaming on the side, Bluefin is more than sufficient.
Conclusio
So, so, so.
At its core, this system isn’t entirely new. The building blocks are familiar: Fedora, GNOME, Flatpak, the immutable approach. And yet, something distinctive emerges. In its design, its focus, and its underlying philosophy—“it just works.”
Still, “cloud-native” remains a question mark for me. It sounds compelling. But what does it actually mean in the daily life of a typical user?
The core system is convincing. The “invisible” updates work. The app store is solid. Application updates run quietly in the background without constant intervention. That genuinely feels modern. GNOME has always been a bit of a love-hate relationship for me—but at its heart, it represents a clean, contemporary system rather than a bloated Windows imitation filled with features nobody asked for.
And yes, once again, typical GNOME shortcomings are addressed through extensions. Dash to Dock, Blur My Shell—extensions that have ranked among the most installed for years. Meanwhile, the GNOME team still hesitates to integrate certain features by default. So my usual GNOME rant stands: a dock? Min/max buttons? Really?
But back to Bluefin: where’s the actual problem?
Technically, I don’t see one. I can absolutely imagine working productively with this system for years. Updates run smoothly, and the concept is well thought out. I might wait for another major release before fully committing—but the overall impression is clearly positive.
The real issue, for me, is a different question: who is this system actually for?
It may sound superficial, but design isn’t superficial. Many people could use Bluefin perfectly well from a technical standpoint—if it weren’t so visually focused in one direction. Teenage aesthetics, dark themes, dinosaur logos, highly detailed graphics. Even for someone like me, who has watched Jurassic Park at least twenty times, it feels too dark, too playful, too specific.
And yet, I see enormous potential. From a marketing perspective, I’d argue the core idea works—if it were defined more clearly and opened up a bit. Custom color options, a more neutral logo, perhaps some distance from the dinosaur motif. Or at least variants. Because when the website essentially says “for everyone,” honesty demands a correction: no, not everyone will resonate with this style.
The good news? If something as ordinary as “windows” can become a global brand, then dinosaurs certainly have a chance too.
For now, Bluefin will remain on my laptop. The LTS version is interesting, but it doesn’t yet feel like the ideal choice for completely non-technical users. When I set up a system for my parents or grandparents, I install Debian with Flatpak—for good reason. It’s predictable and stable. But perhaps that’s not what Bluefin aims to be.
In the end, I’m left with a mixed—but positive—impression. I use Bazzite on my gaming PC and Bluefin on my laptop. Both work well. Both are fast. Both feel modern. The difference is that Bluefin’s long-term direction still feels slightly undefined—even though the core principle is excellent.
No traditional package management, everything via Flatpak, improved security through system separation, and ideally less maintenance. Technically, that’s compelling. Tools like ujust add real value. TPM encryption works. The foundation is solid.
And yet, it feels like a technically brilliant car designed to look like a toy. That doesn’t repel buyers because of performance—but because of perception.
Maybe it’s not for hardcore gamers (they’ll choose Bazzite), not for conservative users (Debian or Linux Mint), not for classic office environments.
Maybe it’s meant for those who identify with the term “cloud-native”—even if the meaning isn’t entirely clear in everyday use. Maybe it’s less about the user profile and more about the system philosophy: a desktop that behaves more like an iPhone than a traditional Linux PC. A system that just works. Stays out of the way. Requires little management. It just doesn’t yet have the universal, polished look of something like an iPhone.
Technically, Bluefin is impressive. Strategically and visually, it’s still searching for its final identity.
And that’s exactly what makes it interesting.
A few more thoughts on the underlying infrastructure—the part you rarely notice in day-to-day use.
First of all: the whole concept genuinely feels a bit futuristic. Mostly because you barely notice it. Updates happen quietly in the background. The system stays stable. You simply continue working.
Technically, though, the concept still requires some explanation. The average user has no idea what it means to boot from a specific “OSTree deployment.” Yet this information is displayed during startup. That might be interesting for enthusiasts, but for regular users it’s more confusing than helpful. If the goal is true accessibility, more automation—and more abstraction—is needed. The technology should fade into the background.
In practical terms, that means automatic detection when something goes wrong, followed by appropriate self-healing mechanisms. Power users can always intervene manually. But for the majority, what matters is simple: it should just work, without requiring an understanding of why.
From a technical standpoint, the clean separation of layers is a real strength. The base system lives in one place. Runtimes, dependencies, and libraries are handled separately. Applications are isolated. User data is distinct. Of course, things can still overlap at the filesystem level, but conceptually the structure is far clearer than in traditional distributions.
And this is where the real promise lies: fewer long-term “slowdowns” of the kind many associate with Windows over time. If the base system remains unchanged and applications are isolated, there are fewer ways to gradually undermine the foundation. Whether that holds true over years of use remains to be seen—but the logic behind it is sound.
This isn’t a miracle solution. No system is magically perfect. But the approach is compelling: less maintenance, reduced risk from system-level changes, and a clearer architectural model. It may also reduce the burden on distribution maintainers, since they no longer have to validate endless combinations of individual packages. That potentially frees up resources—for refinement and reliability rather than sheer package volume.
In the end, the concept feels mature. Still somewhat technical, not yet explained in a way that resonates with everyone—but fundamentally strong.
And if this technology can become both more transparent and less visible at the same time, it could very well become a blueprint for the future of many Linux desktops.