App Rejections Are a Lousy Way to Communicate Policy Changes
In both of these cases, we see Apple breaking with their own documentation or with long-established practice with no warning, and instead using app rejections as a tool to communicate and carry out new policies. This is wretched for developers, who get caught scrambling to fix problems they didn’t know they had (or didn’t expect just yet).
1 Comment RSS · Twitter
"App Rejections Are a Lousy Way to Communicate Policy Changes"
In the real world, sure.
But, once again, the AppStoreMonster's true rules are either written on sand, or deliberately not written at all. Therefore, the true rules are whatever the bouncer at the velvet rope says they are. This, from Cupertino's POV, is a major feature, not a bug. More control, more flexibility, more obscurity from scrutiny. Policy changes are communicated at the velvet rope by design. It's designed the same way at 'exclusive' night clubs or strip clubs for the same reasons.
Lots of the AppStoreMonster's habits are lousy in the real world.
