[Feature request]: Feedback and UX Friction Points on Flatpak PWA Integration, File System Permissions, and Icon/WMClass Resolution
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
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
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:
- 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).
- 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.
- 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
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flatpak/flatpak
-
[Feature request]: remove flatpak.fish completion so the shell's own completions are usedPossibly taken @Franklin-Qi claimed this 33 days ago. Openenhancement needs triage
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
[Feature request]: add support for `xdg-state` filesystem prefixPossibly taken @Franklin-Qi claimed this 33 days ago. Openenhancement libflatpak
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
flatpak/flatpak#5958 · 1 comment ·
Maintainers usually reply within 1 day
-
cli enhancement low priority
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Some flatpak repair strings are not translatableMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stratum-mining/sv2-tp#167 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
libsdl-org/SDL_ttf#650 ·
-
HTTP Request Smuggling: non-final chunked Transfer-Encoding not rejected (CWE-444)Possibly taken @code1a2024 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
jaredgei/wow-forever-android#97 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
openziti/ziti-sdk-c#1254 ·
Maintainers usually reply within 1 day