What apps are we missing out on?
In-app purchase rules do more than set a fee. They decide which business models can exist on a phone at all. When a model needs per-seat billing, per-creator payouts, or a margin thin enough that a 30% cut erases it, the app often never ships. This guide maps the two constraints behind that outcome and gives a checklist for deciding whether your model fits IAP or needs another path.
The premise here is dated captured evidence, not current law. The original argument was written around the Epic v. Apple case and the possibility that it might open up commerce on the app stores. Treat every regulatory statement below as a snapshot of that moment rather than a description of today's rules.
Companies that don't quite fit the mold
Some software ideas fail before launch because the payment system cannot express them. User-generated content is the clearest case. A platform that pays many creators needs a distinct product for each creator, and administering and paying out hundreds of those products is a heavy operational burden. Add a 30% cut on every consumer dollar and the developer's margin disappears.
When a model pushes against the App Store Guidelines, no one can promise a developer that Apple will approve it. The result is not a rejection letter — it is a product that never gets built. The rules do not need to be malicious to have this effect; they only need to exclude the shape of the business.
Technical vs. economic constraints
Two separate constraints do the blocking, and they need separate fixes.
Technical. Under IAP, altering a subscriber's plan from your own backend is awkward. The change is possible, but it depends on the customer opening the app and completing a second purchase screen. That second screen is hard to test reliably, and it stacks another layer of complexity onto a system most small teams already find heavy.
Economic. Apple's take rate applies to any digital transaction regardless of how many parties share the revenue. In ebooks, the author, publisher, app creator, and user all sit in the same transaction. After the publisher and Apple take their portions, little is left for the app developer, which weakens the incentive to build content-distribution apps at all.
First-party content owners can absorb the cut. F1 owns the rights to Formula 1 broadcasts, and MotorTrend produces much of its own programming; both have the margin to make IAP work. A smaller app that resells someone else's content usually does not, because after Apple and the publishers are paid there is nothing left to run on. One possible fix — charging 30% for first-party content and a different rate for resellers — would add review complexity, and normalizing decisions across thousands of reviewers is itself hard.
The prosumer app category
Business tools for small operators run into the technical constraint fastest. Picture a barber-shop app where the owner holds several chairs and the barbers rent those chairs from the owner. The natural price is per chair: a shop with more seats pays more. IAP gives you no clean lever to raise a subscription by a step, so the owner cannot simply ask for two more seats this month and have billing follow, unless the app builds a full upgrade/downgrade journey.
That is enough friction to make the model impractical, and the same wall stands on iOS and Android. Usage- or seat-based pricing is often the price most directly tied to value in prosumer and business software. Mobile is a strong form factor for small business owners — everyone has a phone, and a full point-of-sale system is not always needed. When good software has no clean way to charge, companies are pushed toward awkward monetization instead.
Pushing through technical constraints
Some teams do force the model through. Tingles, an ASMR app and one of the earliest customers of the original publisher, offered a gold pass for all-you-can-eat content alongside individual Patreon-style creator subscriptions. Because the content is one-to-many recorded access rather than person-to-person work, the 30% cut applied. The team had to build hundreds of in-app purchase SKUs, one per creator, and the result was inflexible because of the technical limits.
A different payment platform would collapse that structure. With Stripe, one SKU can be tagged with the actual creator and tracked easily. Under IAP, the same attribution is genuinely difficult. Companies can push through, but the engineering burden is large.
Field/control map for creator attribution:
The way forward
If the App Store rules loosen, the practical change is not the disappearance of IAP. It is that IAP stops being the only sensible option. In simple cases IAP still offers a good user experience. In complex cases, sending a customer to a website or a Stripe checkout lets the developer charge per seat, per haircut, or whatever unit matches the value delivered.
That flexibility is what allows the missing categories to appear. The question for a developer is not whether IAP is good or bad in the abstract, but whether the model fits the constraints it imposes.
Decision checklist:
- Does your price change with usage or seats? If yes, IAP's upgrade/downgrade flow is a technical risk.
- Do you pay many creators? If yes, per-creator SKUs create an administrative and engineering burden.
- Is your margin thin after a 30% cut? If yes, the economic constraint may make the model unviable.
- Do you own first-party content? If yes, you may be able to absorb the cut.
- Can you route customers to an alternate payment method? If yes, per-seat or per-unit billing becomes practical.
| Need | IAP approach | Stripe-style approach |
|---|---|---|
| Identify the creator | One SKU per creator | One SKU plus a creator tag |
| Add a creator | Create and administer a new SKU | Add a tag value |
| Track payouts | Manual mapping across many SKUs | Query by tag |
| Flexibility | Limited by purchase-flow constraints | High |
Frequently asked questions
What is the difference between a technical and an economic IAP constraint?
A technical constraint is about what the purchase system can do — for example, changing billing programmatically requires the user to be in the app and go through a second purchase flow. An economic constraint is about margin — a 30% cut on every digital transaction can leave a reseller with too little to operate.
Why is seat-based pricing hard under IAP?
IAP does not offer a simple way to increment a subscription. A shop owner who needs two more seats cannot adjust billing without a complicated upgrade/downgrade flow, and the same difficulty appears on both iOS and Android.
Why does a creator platform need hundreds of IAP SKUs?
Each creator's subscription is a separate product under IAP, so a platform with many creators must create and administer a SKU for each one. A platform like Stripe can instead use one SKU tagged with the creator.