We actually shut down the project because a good PWA implementation does this better than we ever could. PWAs can have extensions like ad blockers (very difficult to impossible in Electron). PWAs get automatic browser updates (very difficult with Electron).
PWAs are great, and FF’s implementation of them is not.
Extensions still run in PWAs on Chromium-based browsers, so I'm not sure that's the intent behind implementing them.
> Personally, I wish we could purge the vast majority of 'apps' from the world
Out of curiosity, where do you draw the distinction between an app and a website? PWAs are largely just websites with an OS shortcut, and in some cases more integration via platform APIs. I'm sure you're familiar with the term "web app", which perfectly highlights how muddied the line is with modern tooling.
Letting companies save money while still claiming they have "desktop apps".
Having apps that works as well as native ones, while using the same codebase and open technologies, and that is naturally as decentralized, safe and accessible as the web.
Also not needing to be politically correct, approved by Google and Apple or share large percent of revenue and marketing data with them.
It could be happening if Firefox took it more seriously and Apple didn't prevent it from happening.
On macOS this is even more important because switching windows within an app does not use most recently used order.
I'm still baffled that mobile browsers don't have the desktop equivalent of F11. Or a console for that matter, the ADB is good and all but it's not always an option.
They just seem like another way to attempt to shift users from the 'proper web' into a place where blocking ads is more difficult.
Personally, I wish we could purge the vast majority of 'apps' from the world, they shouldn't be apps in the first place, most have no need to run native code, they should be links to websites, sites that can work on more-or-less any device in any browser.