Flatpak

Summary

Flatpak is the main application layer for GUI apps on Fedora Atomic. It is the right place for desktop applications because it keeps graphical software separate from the host base system and fits the Atomic model much better than trying to treat the host like a traditional mutable workstation.

Why this matters

• Flatpak is one of the core layers of Atomic-style desktop usage
• it keeps desktop applications separate from host-level system changes
• if you install the wrong things on the host instead, you make the system harder to reason about and maintain

Environment / Scope

Item	Value
Platform	Fedora SWAY Atomic
Main tool	flatpak
Best use for this note	GUI app workflow
Safe to test?	yes, in a lab
Related area	desktop apps / Atomic layers / user environment

Key concepts

• Flatpak - application packaging model for desktop software
• GUI layer - this is where desktop apps belong in the Atomic model
• Separation of concerns - host system and user applications stay more clearly separated
• Practical rule - use Flatpak for GUI apps, not for everyday CLI tooling that belongs in Toolbox

When to use Flatpak

Need	Better choice	Why
Install a desktop application	Flatpak	fits the GUI app layer
Install Git, Python, compilers	Toolbox	CLI tooling belongs there instead
Change the host system	rpm-ostree	host-level responsibility

Steps / Workflow

Workflow 1: list installed Flatpak apps

flatpak list

Use this when you want to confirm what GUI applications are already installed through Flatpak.

Workflow 2: think in layers before installing

Before installing anything, ask:

1. Is this a GUI desktop app?
2. Does it belong in my daily desktop environment?
3. Would Toolbox be a better fit because it is really CLI tooling?

If the answer is “this is a desktop app”, Flatpak is usually the correct layer.

Commands / Examples

Basic command

flatpak list

What it means

Command	Meaning
flatpak list	show installed Flatpak applications and runtimes

Example output

Name                 Application ID                    Version
Firefox              org.mozilla.firefox              stable
Flatseal             com.github.tchx84.Flatseal       stable

Verification

Check	Expected result
Flatpak command works	flatpak list returns installed entries
Apps are visible	expected GUI apps appear in the output
Layer choice makes sense	GUI apps are here, not mixed into Toolbox or host unnecessarily

Verification commands:

flatpak list

Pitfalls / Troubleshooting

Problem	Likely cause	What to check
App is not found in list	not installed through Flatpak	installation method, expected app source
Wrong mental model	user expects Flatpak to behave like CLI package management	whether the app is GUI or CLI
Layer confusion	too many tools installed in the wrong place	host vs Toolbox vs Flatpak responsibility

Common beginner trap

Flatpak is very convenient, but that does not mean every tool belongs there. On Atomic, it works best when you reserve it mainly for GUI applications.

Key takeaways

• Flatpak is the main GUI application layer for Fedora Atomic
• it fits desktop apps well, but it is not the right home for normal development tooling
• Atomic becomes easier to understand when GUI apps, CLI tools, and host changes stay in separate layers

Official documentation

• Fedora Silverblue getting started
• Flatpak documentation

Related

• Back to Fedora SWAY Atomic
• Fedora SWAY Atomic
• Toolbox
• Container Commands