How about you have a read of the developer agreements? They’re pretty comprehensive and capture all your “what ifs?”. Apple has thought of everything to ensure that developers don’t skirt the rules and if they do, they will be suspended/ banned.Define “unlock extra functionality in the app”.
What if the app doesn’t have “extra” functionalities, and features are presented to “relevant user groups,” which are managed externally?
In agreeing to the developer agreement, you authorise Apple to act as your agent to market and host your Licensed and Custom Applications. The only method of enabling any extra functionality within the app is via IAP. You must submit to Apple for review, all content, functionality or services that are to be unlocked and their prices. The IAP API will then be used to unlock that functionality - and can be directly used for auditing purposes…no need to request anything from a developer after the fact. Any extra functionality becomes part of the Licensed Application and as such, Apple can charge commissions. The judge has ruled this to not be an anti-trust violation and as such, can continue. A developer can take payment elsewhere, but the content will still need to use the IAP API to unlock that functionality. Apple already knows the cost because the developer is required to submit that to Apple prior to offering the extra functionality. Therefore, the only difference to developers is that they will receive an invoice for commissions from Apple at the end of the month instead of the balance of in app payments. There is no requirement on Apple to reduce the commission rate for those developers who use their own payment processors, although they may choose to drop it by whatever it costs them. Given the size of Apple, I’d suggest that they get better deals from Visa than a small developer would therefore the costs would likely still be higher than choosing Apple to handle everything.
A quick, non-exhaustive list of some relevant points:
“Licensed Application” shall include any content, functionality, extensions, stickers, or services offered in the software application.
“Licensed Application” means an Application that (a) meets and complies with all of the Documentation and Program Requirements, and (b) has been selected and digitally signed by Apple for distribution, and includes any additional permitted functionality, content or services provided by You from within an Application using the In-App Purchase API.
“In-App Purchase API” means the Documented API that enables additional content, functionality or services to be delivered or made available for use within an Application with or without an additional fee.
3.3.3 Without Apple’s prior written approval or as permitted under Section 3.3.25 (In-App Purchase API), an Application may not provide, unlock or enable additional features or functionality through distribution mechanisms other than the App Store, Custom App Distribution or TestFlight.
1. Use of the In-App Purchase API
1.1 You may use the In-App Purchase API only to enable end-users to access or receive content, functionality, or services that You make available for use within Your Application (e.g., digital books, additional game levels, access to a turn-by-turn map service). You may not use the In-App Purchase API to offer goods or services to be used outside of Your Application.
1.2 You must submit to Apple for review and approval all content, functionality, or services that You plan to provide through the use of the In-App Purchase API in accordance with these terms and the processes set forth in Section 6 (Application Submission and Selection) of the Agreement. For all submissions, You must provide the name, text description, price, unique identifier number, and other information that Apple reasonably requests (collectively, the “Submission Description”). Apple reserves the right to review the actual content, functionality or service that has been described in the Submission Descriptions at any time, including, but not limited to, in the submission process and after approval of the Submission Description by Apple.
If You would like to provide additional content, functionality or services through the In-App Purchase API that are not described in Your Submission Description, then You must first submit a new or updated Submission Description for review and approval by Apple prior to making such items available through the use of the In-App Purchase API. Apple reserves the right to withdraw its approval of content, functionality, or services previously approved, and You agree to stop making any such content, functionality, or services available for use within Your Application.
1.3 All content, functionality, and services offered through the In-App Purchase API are subject to the Program Requirements for Applications, and after such content, services or functionality are added to a Licensed Application, they will be deemed part of the Licensed Application and will be subject to all the same obligations and requirements. For clarity, Applications that provide keyboard extension functionality may not use the In-App Purchase API within the keyboard extension itself; however, they may continue to use the In-App Purchase API in separate areas of the Application.
Last edited: