[Feature request]: Feedback and UX Friction Points on Flatpak PWA Integration, File System Permissions, and Icon/WMClass Resolution

Open
#6,972 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
linux, ubuntu
Domain
desktop, security

Research direction

This is a broad feedback report, not a defined change, and the body names no source file, test or entry point. Before any code, a newcomer would need a maintainer to decide which of the three points (sandbox file access for PWA shortcuts, Icon= paths, StartupWMClass= matching) is in scope for Flatpak itself. Done would mean a narrowed, agreed proposal, not a patch.

Written by the indexing model from the issue text.

Description

enhancement needs triage
Checklist
  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Suggestion

Dear Flatpak Development Team,

I am writing to share feedback and practical solutions regarding the user experience and integration of Progressive Web Apps (PWAs) installed via browser Flatpaks (Google Chrome, Brave, and Microsoft Edge) on Linux desktop environments (specifically GNOME/Ubuntu).

While Flatpak provides an exceptional and secure sandboxing model, we encountered specific friction points during PWA deployments that require manual workarounds. I would like to outline these challenges and the solutions we successfully implemented:

  1. File System Access for PWA Creation
    The Issue: When attempting to create or install a PWA from within a sandboxed browser (e.g., Chrome or Edge), the browser throws an error stating it lacks write access to ~/.local/share/applications and ~/.local/share/icons, preventing automatic .desktop file and icon creation.

The Solution / Request: Native PWA installation flows should ideally have a standardized, seamless permission bridge or portal interaction to provision shortcuts in standard user directories without forcing users to rely on external tools like Flatseal or manual filesystem overrides (--filesystem=xdg-data/applications).

  1. PWA Icon Resolution Pathing
    The Issue: Browser Flatpaks store internal PWA assets (such as high-res icons like 512.png or 256.png) deep within the sandbox under ~/.var/app//config/.../Manifest Resources//Icons/. By default, generated .desktop entries sometimes look for system-wide icon paths, causing missing icons.

The Solution: Pointing the Icon= field in .desktop files directly to the internal browser manifest resource path ensures persistent, highest-resolution icon rendering (prioritizing 512px/256px) that survives browser and PWA updates automatically.

  1. Window Management and Dock Grouping (StartupWMClass)
    The Issue: Launched PWAs often fail to detach from their parent browser on the desktop dock (Dash to Dock), grouping under the main browser icon instead of displaying their dedicated PWA icon due to a mismatch in window class identification.

The Solution: Explicitly matching or aligning the StartupWMClass= field inside the .desktop entries to match the browser's specific PWA window signature (e.g., chrome--Default or crx__) successfully forces the desktop environment to treat PWAs as independent, standalone applications.

I hope this feedback helps improve the out-of-the-box PWA support and integration for Flatpak-packaged browsers in future releases. Thank you for your incredible work on Flatpak.

Best regards,

Ilya

Dominant language
C
Stars
5.1k
Forks
526
Avg merge
3d 1h
Merged PRs (30d)
23

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flatpak/flatpak

All issues in flatpak/flatpak

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.