- cross-posted to:
- firefox@lemmy.ml
- cross-posted to:
- firefox@lemmy.ml
Mozilla did their biggest Reddit AMA yet on Thursday, June 13, with eight members of the Firefox leadership team. With 400 total comments on the post, they c…
Surprised that nobody asked about their recent purchase of an advertising company.
Maybe they did, but got moderated.
Or maybe most of the critical community left reddit a while ago, I mean, the top rated question in the AMA asks about changelogs in video format…
🫠
The AMA was June 13th, the acquisition news was posted June 16h.
Ah. That makes sense!
Bobby responded that the desktop PWA prototype that Mozilla built a few years ago got “some pretty negative feedback” in user testing and they didn’t have the bandwidth to take another crack at it.
I love how much people forget about this. PWAs were not liked when they came out. And that’s putting it very very mildly.
And morover, at the time, people in general did not like PWAs as a concept. Independent of the browser. It’s a bit funny when nowadays people always ask for PWA support, considering it was once yelled at until it was axed, and the whole concept ridiculed.
I still don’t like it.
But it doesn’t change the fact that some big players insist on PWAs instead of standalone Electron/whatever wrappers if you want anything close to a native desktop experience instead of a browser tab.
And as for taking another crack at it, this time hopefully in a way that won’t confuse non-users, here’s some interesting followup looking for input: https://connect.mozilla.org/t5/discussions/how-can-firefox-create-the-best-support-for-web-apps-on-the/m-p/60561
PWAs were not liked when they came out.
By some ppl. There were also ppl who did like them. As soon as the desktop support was axed, fans of the feature started complaining immediately.
at the time, people in general did not like PWAs as a concept. Independent of the browser
Again, I think this is a sampling issue, because my experience was the complete opposite.
And one of the key parts of PWA features was the “Progressive” part. The site works without those features and you don’t have to use them so removing the support never made much sense to me.