5 ms·
Having worked with PWAs I don't get my hopes up anymore when it comes to iOS, they have added and subsequently broken support for key features in the past. I wi
by tuxie_ 4y ago
Having worked with PWAs I don't get my hopes up anymore when it comes to iOS, they have added and subsequently broken support for key features in the past. I wish they would just fix the current features they claim to support rather than keep adding half-assed features that won't properly work once you install the app in the phone, for example.
- ramesh31 4y agoPWAs are never going to happen. I wish for a free and open app ecosystem as much as anyone else. But PWAs are not the way.
- collaborative 4y agoCare to elaborate?
- ramesh31 4y ago>Care to elaborate? It's been nearly a decade, and we're still talking about PWAs being the next big thing. Mozilla/Firefox has killed them off for good [0], and Safari support is tepid at best. It was ultimately just another push by Google a la AMP to corner the browser market some more, and the rest of the vendors are fed up with it. Devs by and large never bought into it because they are objectively inferior to native, while the tiny number of niche use cases where they do make sense have (rightfully) just avoided the complexity and remained as normal web apps. [0] https://9to5google.com/2021/01/27/firefox-discontinues-work-pwa-desktop/ https://9to5google.com/2021/01/27/firefox-discontinues-work-...
- postalrat 4y agoWhat developers are you talking about that are writing native apps?
- dmt0 4y agoWhen PWAs became possible, the biggest obstacle was that you're loosing all the iPhone users.
- collaborative 4y agoAs a developer, I am putting my eggs in the PWA basket[0]. I fully maintain my native versions, but actively work on achieving parity on the PWA front. The complexity is definitely not greater than developing native. It feels a lot safer to develop a PWA than a native app. Developing native apps subjects you to the arbitrary fancies of Apple and Google. And even worse, your life depends on them. For all we know they might crash tomorrow and then what? Developing a PWA frees you from these worries. I am not a developer to make a quick buck, or to go public. I care about the things I make. I want them to live forever and be sustainable. Buying into the "web toolchain" is a lot safer than buying into the latest native fad pushed by a tech giant that owns the platform and only cares about profits. I have come to terms with this. One day, I will only have a PWA version. Don't know when. It's my conclusion of many years [0] https://6groups.com https://6groups.com
- Gigachad 4y agoThe telegram PWA is shockingly good. It’s not quite as good as the native app but it feels as good as a regular okish native app. It’s useful to get around chats banned by apple as well.
- NonNefarious 4y agoWhat is a "PWA?"
- brundolf 4y ago"Progressive Web App" https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps https://developer.mozilla.org/en-US/docs/Web/Progressive_web...
- yoavm 4y agoProgressive web application - https://en.m.wikipedia.org/wiki/Progressive_web_application https://en.m.wikipedia.org/wiki/Progressive_web_application
- ramesh31 4y ago>What is a "PWA?" Exactly.
- jandorn 4y agoA website.
- z3t4 4y agoAn app that starts out as a web app, but lets you add it to your desktop and it will look just like any other app on your computer. Given that the browser/OS supports it.
- deleted 4y ago[deleted]
- VWWHFSfQ 4y ago> Having worked with <technology> I don't get my hopes up anymore when it comes to iOS In my experience iOS and Safari in general is an absolute wasteland of buggy, half-implementations of tech that should be table stakes at this point. WebRTC [0] is the most egregious. It's one of the many reasons that Google had to fork WebKit into Blink. [0] https://bugs.webkit.org/buglist.cgi?quicksearch=webrtc+safari https://bugs.webkit.org/buglist.cgi?quicksearch=webrtc+safar...