Comment by threatofrain
8 months ago
There isn't just Apple, there's also Google which is a big promoter of PWA's, and in fact they popularized the term. PWA's just never took off.
8 months ago
There isn't just Apple, there's also Google which is a big promoter of PWA's, and in fact they popularized the term. PWA's just never took off.
> There isn't just Apple, there's also Google which is a big promoter of PWA's, and in fact they popularized the term.
Google is the primary champion of PWAs, they have a vested interest in its success. The reason I focused on Apple is because its actions are one of a profit-maximizing gatekeeper actively defending its most lucrative business against an existential threat that is PWA. Every bug, every delayed feature, and every artificial limitation imposed on PWAs on iOS is a calculated strategic move in this defense of its walled garden that makes maximum taxation possible.
>PWA's just never took off.
That's just the lazy manufactured and false narrative that I've already thoroughly debunked. I'm not going to repeat it, since you would just ignore it again.
[flagged]
[flagged]
>I’m building a PWA right now in the drone automation space. I can feel the sparsity of the ecosystem.
What are you talking about? The ecosystem of the web is VASTLY SUPERIOR to anything else. You're just desperately trying to score a point where the is none to score. You don't have to bend over backwards in defense of gatekeepers like Apple (unless you are a massive shareholder)
>A lot of people following this discussion are all devs in the web space.
I am a web dev myself. I actually started out as a software engineer by making iOS apps.
>However, your prejudice for people has already sealed the future of your discussion, regardless of whether your prejudice is correct.
You're projecting, since I've zero prejudice that's why I made arguments based on concrete evidence and consistently backed up my claims.
4 replies →
I use PWAs for my home websites (things like calendars and thermostat) running on tablets. They're a bit awkward, or I'm just ignorant of The Correct Way. I have to set metadata in a file for some reason I don't understand (most importantly, it must have a dedicated icon to display because ???). Then whenever tablet is restarted, I have to tap the website icon to launch it, then push up from bottom of screen to top and hold it up to bring up whatever Android calls the app manager, and then I tap and hold the window of my app and tap to pin it. -and if Android decides to reboot for whatever reason, I must do this again.
-But it's less pain than trying to turn a generic Android tablet into something more like a kiosk, best I can tell (there are third-party apps that do this, which survives reboots, I'm led to believe, but I'd rather not mess with third-party stuff). I previously made Android apps in Java for the tablets, and while I enjoyed the fragment system it uses, the permissions handling was always a nightmare whenever I wanted to do something neat or experimental -- TTS and mic listening in a PWA makes me much less frustrated than trying to do it via native app (which seems backwards to me), and I can still use the website on any non-Android device.