3 ms·
> Apple requires companies to submit some form of user-level payment data. E.g. "iOS device XYZ paid via our website, we owe you 30%" A company could just, y'k
by kelnos 5y ago
> Apple requires companies to submit some form of user-level payment data. E.g. "iOS device XYZ paid via our website, we owe you 30%"
A company could just, y'know, not do that. Or vastly under-report. Apple has no way of knowing, especially if the developer has apps and/or customers on other platforms. Because:
> Apple also adds provisions where they can audit your books.
I'm skeptical that a provision in the developer agreement that requires that the developer allow Apple to audit their financials would stand up in court. Especially for any company that has any significant non-Apple-related business. That information is proprietary and confidential.
I think it is hard to enforce. And agree on your card control system example, though I think the 30% cut is already not in play when it comes to physical goods... consider that otherwise Amazon couldn't have an iOS app: a 30% cut would bankrupt them, and raising prices by 30% would mean no one would buy from them.
- nodamage 5y ago> I'm skeptical that a provision in the developer agreement that requires that the developer allow Apple to audit their financials would stand up in court. See footnote 617 on page 150 of the ruling where the judge suggests exactly that: "In such a hypothetical world, developers could potentially avoid the commission while benefitting from Apple’s innovation and intellectual property free of charge. The Court presumes that in such circumstances that Apple may rely on imposing and utilizing a contractual right to audit developers annual accounting to ensure compliance with its commissions, among other methods. Of course, any alternatives to IAP (including the foregoing) would seemingly impose both increased monetary and time costs to both Apple and the developers."