[jefftougas]

The core problem with PWAs is that ultimately the success of the overall idea is held hostage by the level of consensus across the browser development teams. Whilst they "collaborate" on "common" web standards (they being many, btw), iOS and Android (note: only 2) have very well defined apis for how to create awesome native UX. The problem of creating a unifying native abstraction (like react native or flutter) that is actually effective from the User's POV, is far more attainable, than that of trying to create a consistently awesome PWA with such inconsistent browser support, across a far greater multitude of platforms than the iOS / Android bifurcation in native-land. My $.02.

PWAs have always seemed like one of those beautifully idealistic yet totally doomed to fail ideas (at least for several years relative to native-based-approaches). Don't get me wrong, I think the web will ultimately evolve into the new JVM (read: via WASM), and the beatific promise that was foretold by PWA will finally reach the masses.

Reality Check: We're not quite there yet. Firefox deleting a legacy, buggy, and dev-time-sink attempt at this, makes total sense to me so they can focus on the other awesome stuff they're doing that actually creates real value for the masses today.

To be fair - perhaps they could've handled the ticket on this a bit more gracefully...? But then again - they know their stuff, so I don't blame them entirely :)