>Android has long had PWA support. Almost no one uses it at all.
Yes. Because if you're making a mobile app you want to target the two major platforms. If IOS's PWA's suck, you're not going to try and make a PWA for android. So it's a negative feedback loop.
>Despite entirely separate bases that could be served in entirely different ways,
differnt ways costs money. So often it isn't done. They pick a framework that launches to all targets and deviate as little as possible. We're long past the days of having two dedicated teams trying to appeal to android users vs ios users. They are all simply "users".
>A couple of years ago Apple pretty much fully supported PWAs, including push notifications.
They pretended to while changing a bunch of develop terms to make it hard to actually use the PWA's. They "fully supported" PWAs the same way they "complied" with the DMA.
Besides, adoption takes a few years. You can't make a half-hearted update and expect changes overnight.it takes a few years to really see the results.
>Ignoring that almost all of these orgs are also building web apps
Poorly, but yes. You can say they have something reseming a web app.
>several of the major frameworks can share the majority of code with PWA apps.
But as we should all know, it's not enough to press a button and deploy perfectly. You gotta fix all thr quirks, and that's where most of the budget for a dedicated team back in the day went. Not so much these days.
>Yet despite Android making up like 75% of the market....almost no PWAs have any traction at all. It's almost like it isn't Apple's fault.
75% isn't enough when targeting 100% of the market. And this decade isn't a good example of how companies are trying to win customers over with quality and care.
Can't get more term-Y than "you can't do this here".
>It isn't Apple's fault, as boring and constant as that cry is.
It's not apples fault in the same way it's not their fault Flash died. they didn't land the killing blow, but they sure did slice some limbs off.
You seem too obsessed with thinking that there's this "android exclusive "market to appeal to to really understand my argument on how app development and support actually works in practice, so I'll leave it at that metaphor.
>But as we should all know, it's not enough to press a button and deploy perfectly. You gotta fix all thr quirks, and that's where most of the budget for a dedicated team back in the day went. Not so much these days.
Have you ever worked on a project that targets both Android and iDevices? Close to none of them are just one magical code base that hits both devices. Overwhelmingly there is an enormous amount of custom code for each platform. You are propping up a myth to support this ridiculous contention.
>75% isn't enough when targeting 100% of the market.
Only garbage apps target "100%" of the market with one app. Again, I feel like I'm talking to people who have never, ever touched a mobile app.
>Straight from the horses' mouth
You literally linked to the app policies. That has zero relevance for PWAs.
The fact that my upper level comment got flagged, hilariously, betrays how utterly delusional, detached from reality, and just nonsensical almost all discussions on this are. It is always portrayed against a mythical strawman (the magic "only one app magically targets everyone, that no one is actually doing it").
PWAs fail because they're usually bad, and web development teams usually have horrifying attitudes towards users. It has nothing to do with Apple.
Yes. Because if you're making a mobile app you want to target the two major platforms. If IOS's PWA's suck, you're not going to try and make a PWA for android. So it's a negative feedback loop.
>Despite entirely separate bases that could be served in entirely different ways,
differnt ways costs money. So often it isn't done. They pick a framework that launches to all targets and deviate as little as possible. We're long past the days of having two dedicated teams trying to appeal to android users vs ios users. They are all simply "users".
>A couple of years ago Apple pretty much fully supported PWAs, including push notifications.
They pretended to while changing a bunch of develop terms to make it hard to actually use the PWA's. They "fully supported" PWAs the same way they "complied" with the DMA.
Besides, adoption takes a few years. You can't make a half-hearted update and expect changes overnight.it takes a few years to really see the results.