A Developer's Rejection Exposes the Arbitrary Gatekeeping in Apple's App Store

A recent App Store rejection has reignited a persistent debate about Apple's control over its ecosystem. The developer behind LaunchCade, a utility designed to overhaul the outdated macOS Launchpad, was blocked from updating his app. Apple cited rules against duplicating built-in functionality, a decision that has struck many in the developer community as inconsistent and revealing.

The core issue is one of selective enforcement. Apple's Launchpad has seen minimal meaningful development since its 2011 debut. LaunchCade offered the customization and workflow integration that Apple has not. The developer, Sindre Sorhus, is a respected figure known for high-quality, focused tools that often address Apple's own oversights. His rejection underscores a guideline that grants reviewers wide latitude to decide what constitutes a 'duplicate,' even when the original feature is widely considered insufficient.

This creates an unpredictable environment for software builders. Developers cannot reliably anticipate whether their work will pass review, as the rule is not applied uniformly. This inconsistency acts as a deterrent to innovation, particularly for the niche utilities that have long defined the Mac's appeal.

The friction arrives as Apple faces increased regulatory pressure to open its platforms. While the company has made concessions on iOS in certain regions, the Mac App Store remains a critical channel for visibility and user trust. Being barred from it can severely limit an app's reach.

Apple maintains its review process safeguards users, a valid concern. However, the rule in question isn't about security or privacy; it's about platform control. The history of podcast apps, keyboards, and maps on iOS shows a pattern of restriction followed by reluctant opening under external pressure.

The outcome is a chilling effect. Developers must weigh the risk of sudden rejection against the effort of building for the Mac. Some opt for direct distribution, sacrificing discoverability. Others may simply stop. The cost isn't just one blocked app, but a gradual erosion of the third-party developer energy that makes the platform thrive. As scrutiny intensifies, Apple's policies face a simple test: do they ultimately benefit users, or merely preserve the company's control?

Source: Webpronews