Episode 4 · 14 Jul 2026

What an app store rejection actually tells you

Platform policy is written in guidelines but enforced in rejections. Reading the gatekeepers' decisions as the real terms of service.

Show notes

• The published guideline is the theory; the rejection letter is the practice. Developers plan against the practice.
• A platform's real policy is the sum of what it rejects, what it allows and what it ignores. The gaps between the three are where businesses get built and killed.
• Dependency on one gatekeeper is a business risk that belongs on the same page as the cap table.

Chapters

• The week in five lines
• Guidelines versus enforcement
• The rejection as a policy document
• Listener mail

Transcript

This episode runs as written notes rather than a recording. The argument, in order.

Every major platform publishes guidelines, and every experienced developer will tell you the guidelines are the beginning of the conversation, not the end. Enforcement is uneven, appeals are opaque, and the same clause can end one business while another ships under it for years. That gap between the written rule and the enforced rule is where platform power actually lives.

This is why a rejection letter is worth reading like a policy document. It tells you what the platform is protecting this quarter: a revenue line, a partnership, a regulatory position. The reason given is rarely the whole reason, and the pattern across many rejections is more honest than any single guideline page.

For anyone building on a platform, the lesson is structural. A single gatekeeper dependency is not a technical detail; it is a business risk, and it deserves a seat in the same conversation as funding and hiring.