Tony BarkFirefox Nightly Preps Progressive Web App Support
UnmappedI dont use many PWA’s since I had to run them on chromium before. But as a web Dev and even more so as a user, I feel like PWA’s are the way to go. They completely avoid all the app stores drama plus the 30% fees. Also the devs get to deploy instant updates without the delay going through the app stores. Just like any other web app. If done right I could see them replacing most native apps. Assuming we can get app to allow PWAs full CPU usage. Currently they are throttling them from what I understand.
BogasseBut it’s easier to block trackers & ads on a PWA, and life made me very cynical about “the industry” 😅
Didn’t apple disable PWA’s in Europe?
Yes, they did that when the EU made the ruling about allowing other app stores. Apple doesn’t like PWAs cause they lose their 30% cut. Hopefully we some ruling or law that they have to treat them equal to native apps.
Apple doesn’t like PWAs
Which would probably have Jobs rolling in his grave. He was all for web apps. Hell, their first attempt at widgets on macOS were just web apps. That’s why he was so adamant about getting rid of Flash. He knew the technology was viable.
moe90techmonitor.ai/…/apple-reverses-decision-to-ban-p…
it was. But, they bring it back
PWAs are god awful on IOS.
dblsaikoThey are god-awful everywhere. I don’t get why people can be like “yeah I want all of my apps to be janky crap that is usually missing a lot of features you’d get for free using the platform toolkit”. The only exception I’ve seen thus far that was actually good is Figma and god knows how much effort they had to put into that to make it behave even remotely reasonably.
The idea is that Google and Apple on Android and iOS have purposefully gimped PWA functionality in order to maintain the popularity of their app stores. Which I get, because web apps are much more useful and functional on full computers. So it’s not really the fault of the PWAs that PWAs suck. But unfortunately, they do suck.
My only problem with PWAs is that they have arbitrary security requirements. Anything non-localhost needs https. No self-signed cert allowed.
Enforcing people to buy a router that supports dyndns for their self hosted apps is odd. I’m wondering who makes these rules.
You can do DDNS for free, using a client app on your server, rather than router.
I use cloudflare-ddns
Oh right. Thanks, indeed. However, for private apps on LAN addresses it’s still a problem.
Yes it is. PITA to work within your own network.
I run a DNS server for this purpose.
And FWIW, Firefox already supports them on android; this is about desktop support.
roofuskitI was going to say, “am I losing my mind?” I’ve had PWAs on Firefox for years. I’ve never once cared to use one on the desktop I guess.
Indeed. I’m not sure when they added mobile support back, but it wasn’t there when I last looked for it. Guess its time for me to move my PWAs out of brave now. Thanks.
I wrote a little background app and extension that opens links from a Chrome PWA in the same named Profile in Firefox for exactly this reason. Probably shoupd have released that…
Yess finally. Switched off of Chrome after seeing uBlock Origin was going to go away, but I have a lot of PWAs which has been hacky to get working.
most wanted feature
Ive been using PWAsForFirefox for couple of years now and it’s pretty good tho a bit clunky at times as firefox updates tend to break some settings.
What’s even the point if they do that, might as well just use bookmarks
Yeah what a wasted opportunity which is very typical for Firefox
I wanted a taskbar button for Navidrome at work. This is so I could quickly find my music in between the several open Firefox windows.
As the IT admin, I could’ve installed this. But I knew I REALLY shouldn’t. It needed administrator rights, and I had no idea how secure it was.
So instead I used Brave for Navidrome PWA. Brave was installed as local user, so it couldn’t bring down my entire organization if it got my password.
Now I’ll be able to switch back.
What year is it?!