Showing results for 
Show  only  | Search instead for 
Did you mean: 
Making moves
Status: In review

Progressive Web apps are an important feature of a browser that Firefox is the only one missing.
For some, it can be the reason to switch to another browser.
In other cases like for the Steamdeck, it's what imposed the choice to only include Chrome in the SteamOS interface.
Other problem even for avid Firefox users, since I wanted Social apps on my pc I had to get them on the Microsoft Store which is an Edge PWA that opens every link in an Edge window, making me use this... other browser.

Strollin' around

For me, the nice thing about PWAs is having a unique and static app_id/class for a window under sway or i3 so that I can automate arranging my desktop as I wish and easily navigate to them across monitors and workspaces. I use swaywm on my desktop and I like to force some windows to open on certain monitors/workspaces. PWAs give each instance its own app_id that does not change which makes identifying the contents of the window straightforward. That is how all other implementations that I have seen handle PWA windows including Gnomes Epiphany web app implementation. I have a workaround for Firefox with javascript bookmarks to open a popup and a shell script that continuously listens to the sway socket to detect the new window and automatically move it and assign it to a workspace. It is not a great solution since it can't detect which app it is before the window is shown and can't rely on the window title. This causes unwanted, ugly window reformatting every time I create one of these popups since I can't move the window until after it has been created. And I have to launch it from Firefox since I can't launch a javascript bookmark from the command line. If there was a unique app_id/class I would be able to direct the window appropriately before it even opens. I have my Fastmail, Element, Google Voice and a couple of Mastodon instances at minimum open in their own popup windows on various workspaces/monitors that act enough like a PWA for me once I have them open and placed where I want. They do not live on the same workspaces/monitors.  With 3 monitors and 10 workspaces having things sitting in tabs does not work well since I can only search for the active tabs with my task manager script. With PWAs or in my case popup windows I can task switch between them just like any other app when even when they are on a workspace that is not currently visible. I will live without PWAs on Firefox since I am not going to use anything Chromium based and I have a livable workaround. However, it would be a significant quality of life improvement for me and my desktop workflow and I imagine to other swaywm and i3-wm users to have that unique app_id.  I think KDE might be able to work with that app_id for it's scripting as well.  We are a minority but I figured I would chime in on the unique app_id/class part of PWAs it since I did not see that mentioned in any of the other posts. 

New member

I actually switched browser because of the lack of pwa support... Hope it will be implemented soon. 

New member

would love to see them

New member

Firefox should be able to create a completely independent session for PWAs but also be able to offer a PWA like experience for websites not supporting PWA, such as

On that way, we can use "apps" for any website, using Firefox/gecko as an engine, with the benefit of using add-ons to block content or shape the"app" on the way we want.

Making moves

So PWA's give normal users a feeling that reminds the youngest generation more of a smartphone.

If I could estimate, this type of device is the entry into the computerized world of the latest generation.

A PWA also leads to more variety when using the website, thanks to desktop icons or taskbar icons, smaller websites are less likely to be forgotten.

There is an advantage, for example, in offline caching but also in caching in general.
It is possible to specify in a PWA which web content should be transferred directly to the cache to be loaded from there.

Making moves

Although the idea of PWA's is nice, at moment i'm glad Firefox does NOT support it...

In todays world where so many script kiddies are active, i don't need another "attack vector" especially for Linux.
The Linux community so far demands that ALL software be inspect able for their code BEFORE needing to install them, OpenSource...

Allowing PWA's would open a can of worms where the code you install would not be able to be supervised by independed specialist....

So i'm glad that the needed Know-How is a bit higher as plain Web-languages for most software that can be installed on Linux, it keeps the script-kiddies at least behind that fence 😜

New member

Why not a PWA like support where any webpage can be turned into it's own profile?

Strollin' around

The lack of PWA is quite frustrating. It has been a while since PWAs is among the top requested features. I hope it gets pushed into development soon as it would greatly improve FF.

New member

+1 for this. Firefox is quickly falling behind to Chrome and MS Edge in features.  I keep Firefox for the security and privacy, but still wish it had some of the useful features of other browsers.  Please consider implementing PWAs.

New member

Keep in mind that FireFox mobile for iOS DOES SUPPORT PWA!