3 ms·

Firefox isn't even playing catchup. Mozilla aborted what scant work it's done on PWA support. From the horse's mouth: https://bugzilla.mozilla.org/show_bug.cgi

Firefox isn't even playing catchup. Mozilla aborted what scant work it's done on PWA support. From the horse's mouth: https://bugzilla.mozilla.org/show_bug.cgi?id=1682593 https://bugzilla.mozilla.org/show_bug.cgi?id=1682593 Chrome and its variants have already won the PWA space, not by some brilliant strategy or sinister ploy on Google's part, but by default of its competitors.

mhoad 5y ago
I mean I think they are already in an extremely rough position but if they find themselves in the situation where they are seen as a browser for Web pages rather than Web apps I think that could prove fatal for them. It’s clear that there is a lot of new tech on the horizon for browsers that is closing the gap with native very quickly. If they are unable to make that transition which sadly seems like a real possibility then I don’t know where that leaves them.
cpeterso 5y ago
That bug is only about Single Site Browser mode (SSB), where a desktop link would open a website in a Firefox browser window with no browser controls.
- Dracophoenix 5y ago
  The relevant information is presented in the comment section below the bug report proper. If you would like a particular post to be pointed towards, here is one reprinted and slightly edited for clarity: —————————————————————————————— Dave Townsend [:mossop] Assignee Comment 15 • 10 months ago (In reply to Hexandcube from comment #12) >I disagree, many people have been waiting for PWA support in Firefox. Removing this feature, may result in people (including me, a huge Firefox advocate) switching from Firefox, to a browser that supports PWA. I'm very disappointed. We already don't have the feature working in any decent fashion so I'm not sure removing it will have any impact here. >I also would like to see the results of the research, Dave was talking about. Unfortunately I think that the research is confidential at the moment. (In reply to joshas from comment #13) >You should reconsider this decision. It is understandable that currently there might not be enough resources to finish full PWA support, like in competing browsers, but removing it completely will not only make all work done on it a waste of time, but also send wrong signal to some users. >Leaving feature hidden under flag for enthusiasts to experiment on and, maybe, even submit patches that will nudge it closer to completion - that would be a bigger win, than removing feature altogether. The signal I hope we are sending is that *PWA support is not coming to desktop Firefox anytime soon* {emphasis: mine}. At this point I don't think we would accept patches to improve the feature so I don't think leaving the code in Firefox makes any sort of sense. Speaking as the developer who spent a good deal of time writing most of the code I am frustrated to see it removed too, but it is the decision that makes sense at this time. ——————————————————————————————
  - Liquid_Fire 5y ago
    Again, this is only referring to the feature that lets you run a webapp in a dedicated browser window as if it was a native app. Nothing to do with running webapps in the browser normally.

mhoad 5y ago

I mean I think they are already in an extremely rough position but if they find themselves in the situation where they are seen as a browser for Web pages rather than Web apps I think that could prove fatal for them. It’s clear that there is a lot of new tech on the horizon for browsers that is closing the gap with native very quickly. If they are unable to make that transition which sadly seems like a real possibility then I don’t know where that leaves them.

cpeterso 5y ago

That bug is only about Single Site Browser mode (SSB), where a desktop link would open a website in a Firefox browser window with no browser controls.

Dracophoenix 5y ago
The relevant information is presented in the comment section below the bug report proper. If you would like a particular post to be pointed towards, here is one reprinted and slightly edited for clarity: —————————————————————————————— Dave Townsend [:mossop] Assignee Comment 15 • 10 months ago (In reply to Hexandcube from comment #12) >I disagree, many people have been waiting for PWA support in Firefox. Removing this feature, may result in people (including me, a huge Firefox advocate) switching from Firefox, to a browser that supports PWA. I'm very disappointed. We already don't have the feature working in any decent fashion so I'm not sure removing it will have any impact here. >I also would like to see the results of the research, Dave was talking about. Unfortunately I think that the research is confidential at the moment. (In reply to joshas from comment #13) >You should reconsider this decision. It is understandable that currently there might not be enough resources to finish full PWA support, like in competing browsers, but removing it completely will not only make all work done on it a waste of time, but also send wrong signal to some users. >Leaving feature hidden under flag for enthusiasts to experiment on and, maybe, even submit patches that will nudge it closer to completion - that would be a bigger win, than removing feature altogether. The signal I hope we are sending is that *PWA support is not coming to desktop Firefox anytime soon* {emphasis: mine}. At this point I don't think we would accept patches to improve the feature so I don't think leaving the code in Firefox makes any sort of sense. Speaking as the developer who spent a good deal of time writing most of the code I am frustrated to see it removed too, but it is the decision that makes sense at this time. ——————————————————————————————
- Liquid_Fire 5y ago
  Again, this is only referring to the feature that lets you run a webapp in a dedicated browser window as if it was a native app. Nothing to do with running webapps in the browser normally.