81–90 of 250 posts
Earlier quoted context omitted.
We're now at the point where writing web-first apps that can get optionally also get compiled into "native" apps that run in a js/wasm runtime on any platform and act like native apps might get popular again.
Is this allowed under iOS?
I think people are focused on the wrong issue. The fee % is not the problem. The problem is the restriction against using other types of payment processors. I am 100% OK with Google, Apple, or whoever charging whatever price they want to charge for using their app store services. They are, after all, providing all of the infrastucture for software delivery, updates, payments, etc. Not to mention giving you access to…
Earlier quoted context omitted.
I want it one step further, it's not called "sideloading" but just "normal install", people should be able to install anything they want without some unwanted middleman, all the restrictions are just market distortions.
> people should be able to install anything they want without some unwanted middleman What “people” are you referring to? The millions of people, like yours truly, who’ve made the conscious decision to pay Apple because of their App Store model. I’m an engineer, I have a desktop and a laptop I can install whatever I want on. I’m ok with not doing that on my phone. In fact, I don’t want that experience on my phone. So…
The google play subscription API is probably the worst I ever had to integrate with. For example * Response leaves out historic data (i.e. a subscription doesn't show it was paused, had a trial, etc. once they're over) * Fetching the subscription state frequently returns data inconsistent with previous results (e.g. the start date of the subscription keeps changing, the expiry date keeps jumping around), so piecing t…
Earlier quoted context omitted.
We're now at the point where writing web-first apps that can get optionally also get compiled into "native" apps that run in a js/wasm runtime on any platform and act like native apps might get popular again.
Is this allowed under iOS?
I think people are focused on the wrong issue. The fee % is not the problem. The problem is the restriction against using other types of payment processors. I am 100% OK with Google, Apple, or whoever charging whatever price they want to charge for using their app store services. They are, after all, providing all of the infrastucture for software delivery, updates, payments, etc. Not to mention giving you access to…
I think people are focused on the wrong issue. The fee % is not the problem. The problem is the restriction against using other types of payment processors. I am 100% OK with Google, Apple, or whoever charging whatever price they want to charge for using their app store services. They are, after all, providing all of the infrastucture for software delivery, updates, payments, etc. Not to mention giving you access to…
I think people are focused on the wrong issue. The fee % is not the problem. The problem is the restriction against using other types of payment processors. I am 100% OK with Google, Apple, or whoever charging whatever price they want to charge for using their app store services. They are, after all, providing all of the infrastucture for software delivery, updates, payments, etc. Not to mention giving you access to…
And how would it be enforced? (If charged outside of the app store and get an invoice from google instead on their cut)
Earlier quoted context omitted.
> I'd really love to know his mindset, because it's completely unfathomable to me. He was fixated on having complete control.
And why would webapps give Apple complete control? Someone develops a webapp, I can make my own phone and anyone who wants to continue using all the webapps they were using in Safari on their iPhone can come over and do that in the browser on my phone. People develop native apps for the iPhone, and suddenly leaving the iPhone means leaving behind all those apps.
It sounds crazy but at the time the wild west of apps on the desktop meant that the user experience was pretty poor and allowed malware to explode.
It has been said that Microsoft's failure to fix these issues is really what drove web application development. No one realized a viable alternative was to lock down the device to a single store/publisher and then take a 30% cut.
Now that WebApps probably could replace nearly all native apps, it's in Apple's best interest to not fully support PWAs, WASM, etc. because the app store is so lucrative.