I'm just going to address the most disingenuous parts of this absolute stemwinder of a reply, but users pay for Maps with their device purchase. What, do you think Apple’s a charity, too?Wrong. Apple provides many free services to developers that are critical to their apps as well as their users. One example: maps. Google Maps is EXTREMELY expensive to developers (and is one of Google's main revenue streams). Apple provides Apple Maps for free. Developers like Yelp switching to Apple Maps save them hundreds of thousands of dollars per year alone.
Phew, hope you don’t get into trouble for revealing that highly sensitive top-secret information. (An idiot who watches a few WWDC sessions could piece that together, setting aside that it’s just common sense at Apple’s scale.)One example: they have a Maps team, and then there's a MapKit team.
Now talk about how many features the MapKit team works on at the behest of other Apple teams, including but certainly not limited to the Maps team, which is the point I was making. You can draw a straight line from most publicly available API to features that Apple would soon implement in their own apps if they hadn’t already when it was made public. And even where that’s not the case, there’s usually a straightforward business justification for doing so.
Using your Maps example, they’ve added features in MapKit that they themselves may not actively need just to compete with the Google Maps SDK. It allows them to crow about how many requests Apple Maps gets including those for things that aren’t actually in Maps, instead of a developer being forced to use another mapping service for a specific feature not available in MapKit.
No one’s saying that developers have to no longer use IAP; there are certainly strong arguments for it and against it. That’s why a developer should be able to make a choice as to what works best — or works at all — for their business. Besides, they could even use Apple Pay; it’s an easy, fast, and secure experience for the user. However, unfortunately, nanny Apple says no. Apple claims Apple Pay is reserved for physical goods and services, but spoiler alert, Apple themselves don’t neatly follow this rule.You're not thinking from the user perspective. If I made my users login to PayPal every time they want to do an IAP purchase, it would scare many users away from ever attempting an in app purchase. Just yesterday I downloaded Tastetea app and it asked me to type in my credit card number to order a drink from them. I deleted the app immediately after and just went to Starbucks. If this was a general experience by most apps, it would put users on alert before they even tap the "checkout" button which would lower the total amount of money spent inside an app in general.
The fact that Apple made it incredibly easy and made this process consistent across the platform plays a huge role in driving more revenue to developers and Apple. Would you want 100% of a small pie or 70% of a much bigger pie? You failed to take this into account.
Huh. Guess the times that the App Store wouldn’t work or was unusably slow when AWS was having trouble were just wacky coincidences, then. (You know what I meant, and I won’t address this further.)Spinning up an EC2 server or enabling Cloudfront on AWS isn't what I call building a CDN. You do know that there's more to that right?
Fewer free apps? Tragic! Whatever would we do without low-effort soundboard apps and those flashlight apps that haven’t been updated since iOS 6?If Apple charged free app developers extra for hosting free apps, there would be far less free apps on the App Store.
Besides, if a free app can’t support itself with nominal fees for hosting and bandwidth usage, maybe they should just change their business model. That’s what Apple’s policies can force paid/IAP developers to do, so why are they special?