Apple bans entire dev account, no reason given
Account termination & lack of explanation
- The dev’s Apple account was terminated citing section 3.2(f) of the Apple Developer Program (ADP), but without a concrete, actionable explanation.
- Commenters note this is common: Apple rejection/termination letters are highly generic and legally sanitized.
- Some argue we can’t fully judge the case because the developer hasn’t shared much about what they did; others counter that regardless, such serious actions should always be clearly explained.
Section 3.2(f) & Apple’s power
- 3.2(f) is seen as extremely vague, covering any act “intended to interfere” with Apple software/services or business practices.
- People speculate it could be used to block apps that conflict with Apple’s plans (e.g., “Recall”-like screen recording tools) or even treat support contact as “interference.”
- There’s criticism that Apple unilaterally controls developer identity and notarization, with no alternative attestation providers.
Broader pattern: bans, geoblocking, and fraud
- Similar opaque bans are reported from AWS, Amazon retail, Imgur, and others, often triggered by login from “high-fraud” countries or cross-region usage.
- Users describe geoblocking and “fake” error messages (e.g., capacity errors instead of honest 403s), and even “birthblock” of users born in occupied regions.
- Some justify IP-based blocking as a crude but common “defense in depth” against botnets; others highlight the collateral damage.
Lock-in, ownership, and alternatives
- Many emphasize that tying critical work or content to locked ecosystems (Apple, Amazon, etc.) is dangerous; bans can mean instant loss of purchases and data.
- Apple is criticized as uniquely restrictive: you need its permission to run most software, especially on iOS; macOS notarization is becoming de facto mandatory.
- Android and Windows are seen as somewhat more escapable via alternative OSes, sideloading, or offline use, though banking/government apps can limit that.
Developer risk & ecosystem effects
- Developers express anxiety that their livelihood can be destroyed overnight with no recourse.
- Some say this is yet another reason to avoid Apple platforms or not build a business inside any gatekeeper’s “moat.”
- Hopes are pinned on regulation (e.g., EU/DMA) to open distribution and force more transparent processes.