APIs for software services make this whole thing even more complicated. Some company has a web service offering which they charge $10/month for. They also have a web API, which allows 3rd-party developers to write apps for the service. Case (1): The services writes an iOS app to access their service. Case (2): A third party comes along and writes an iOS app for the service, using the service's API.
If it's true that in (1), they have to offer an IAP-way for users to purchase a subscription, what does that say about (2)? The third-party developer has no way of adding IAP to their app (it's not their company and the API doesn't expose such functionality).
Under these (more and more crazy sounding) rules, is (2) still required to pay the 30%? And given that it's impossible for (2) to have an IAP subscription option, maybe (2) isn't even allowed to exist? But if it is, then the service company could just pay 3rd-party developers to write apps for their service to add value for their subscribers without having to deal with the 30% stuff.
If it's true that in (1), they have to offer an IAP-way for users to purchase a subscription, what does that say about (2)? The third-party developer has no way of adding IAP to their app (it's not their company and the API doesn't expose such functionality).
Under these (more and more crazy sounding) rules, is (2) still required to pay the 30%? And given that it's impossible for (2) to have an IAP subscription option, maybe (2) isn't even allowed to exist? But if it is, then the service company could just pay 3rd-party developers to write apps for their service to add value for their subscribers without having to deal with the 30% stuff.