(In reply to heapifyman from comment #25)
it is the decision that makes sense at this time.
Could you elaborate on why it makes sense?
As Gijs says, we have limited resources and so have to spend those resources on work that appears to have the most impact on our mission. Based on the available data we have (both the research we performed as well as looking at how Chrome and Edge's implementations are being received) PWAs on desktop fall behind other work right now.
Secondly, how can you justify removing a feature because
user research found little to no perceived user benefit
when the user research was performed on a different implementation?
The research was performed on something very close to what we envisioned our implementation looking like and so its results give us a good indication of how our implementation would be received.
(In reply to dreadnaut from comment #23)
Do you know if this will affect work on #1283670, the
--app command-line switch?
PWAs were essentially the route to implementing that feature so I expect to wontfix that bug as a part of this.
(In reply to landsman from comment #20)
(In reply to Dave Townsend [:mossop] from comment #15)
This is very sad! PWA is future of agile apps development. Please let's consider this decision again. Is there something what the community can do?
The problem is that even if someone volunteered a patch that completes implementation we would have to spend resources on reviewing that and the ongoing maintenance costs. If there is some hard data somewhere we've missed that shows we would gain more market share by implementing this than other projects then that would sure be useful though!