Earlier quoted context omitted.
No way that's happening on iOS as long as Apple takes 30% off the top
Yes because think of all the money Apple gets from taking 30% all of the free apps that would be free web apps....
Private client-side-only PWAs are hard, but now Apple made them impossible
821–830 of 927 posts
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#822Earlier quoted context omitted.
> I’m guessing that Apple will start hindering web apps because the new mouse support in iPadOS is going to be such a boon to web apps. As a web developer , I've never believed Apple has hindered web development on their platform, purposefully or not. They just don't spend their resources adding in WebBluetooth or whatever new API-of-the-day Google has decided to come up with. As I see it, their focus is on the user…
As a web developer, I've never believed Apple has hindered web development on their platform, purposefully or not. [...] As I see it, their focus is on the user, which is why they've been slow to adopt APIs that are privacy concerns, or drain battery, or have other negative implications. As another web developer, I find this entirely unrealistic. Apple's QoI even for popular new features like the HTML5 media elements…
Even on the Android phones that supported Flash, it ran like shit and drained battery. Apple just never opted into that experience.
This revisionist history, of seeing people wanting the proprietary Flash to come back, is crazy.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#823I ported Polar ( https://getpolarized.io/ ) over to a PWA about a year ago. It's kind of a nightmare due to both Google and Apple messing things up. PWAs could be an amazing platform but both companies are really messing it up. Apple is trying to kill them by giving plausible explanations as to why they can't have PWAs. Security this, blah blah blah. There's no reason they can't have PWAs work well in Safari other th…
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#824The source clarifies that this only applies to websites run within the Safari browser.[1] PWAs added to the home screen aren't affected. > As mentioned, the seven-day cap on script-writable storage is gated on "after seven days of Safari use without user interaction on the site." That is the case in Safari. Web applications added to the home screen are not part of Safari and thus have their own counter of days of use…
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#825Earlier quoted context omitted.
> ... Consumers are another problem. ... You blame Apple, Google and your consumers, instead of just making native apps. Why?
"just making native apps"
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#826Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#827Earlier quoted context omitted.
Yes because think of all the money Apple gets from taking 30% all of the free apps that would be free web apps....
The 30% includes any kind of subscriptions or payment tied to the user account.
How many apps require a subscription and cannot be a web app because of limitations of Safari?
How many paid apps would be websites if it weren’t for limitations of Safari?
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#828Better title: Apple restricts tracking by limiting browser storage, which hurts my particular app. Browsers need to be severely limited due to them running arbitrary code from the web. Doesn't matter if it's an offline web app. If you want more access, make a native app (with or without web technologies).
Making a native app is more complicated than making a webapp, especially if you want something cross platform. Browsers are now an universal virtual machine, what was the JVM years ago, and with webassembly we will se more and more things done in the browser. The real 'write once, run everywhere' are webapps, a webapp doesn't care if you are using Apple, Windows, Linux, BSD, whatever, if you have a compatible browser…
that’s not been my experience*
* unless you use some huge web framework to abstract everything and patch all the differences between the browsers
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#829Earlier quoted context omitted.
Yes because think of all the money Apple gets from taking 30% all of the free apps that would be free web apps....
Yeah, cause everything in the browser is free, right? Clearly it's A LOT of money for apple. If they didn't care about the money then they would just allow it so everyone could avoid receiving payments using apple and giving them 30 %.
What makes you think users would willy nilly put their credit card on every random website.
Everyone can avoid using Apple for subscriptions. There are existence proofs of apps on the store that require payments outside of the store - like all digital content from Amazon.
Most of the money that people spend on the App Store are from games and in app consumables. Especially since the major services like Netflix and Spotify don’t allow in app subscriptions.