Last week, the Electronic Frontier Foundation‘s Corynne McSherry had to break the sad news to Apple iPhone users that due to Apple’s incredibly restrictive developer rules, the EFF cannot produce an iPhone version of their mobile app:
As we have been saying for years now, the [Apple] Developer Agreement is bad for developers and users alike. Here are a few of the terms that we are worried about:
Ban on Public Statements: Section 10.4 prohibits developers from making any “public statements” about the terms of the Agreement. This is particularly strange, since the Agreement itself is not “Apple Confidential Information” as defined in Section 10.1. So the terms are not confidential, but developers are contractually forbidden from speaking “publicly” about them.
Ban on Reverse Engineering: Section 2.6 prohibits any reverse engineering (including the kinds of reverse engineering for interoperability that courts have recognized as a fair use under copyright law), as well as anything that would “enable others” to reverse engineer, the software development kit (SDK) or iPhone OS.
App Store Only: Section 7.3 makes it clear that any applications developed using Apple’s SDK may only be publicly distributed through the App Store, and that Apple can reject an app for any reason, even if it meets all the formal requirements disclosed by Apple. So if you use the SDK and your app is rejected by Apple, you’re prohibited from distributing it through competing app stores like Cydia.
No Tinkering with Any Apple Products: Section 3.2(e) is the “ban on jailbreaking” provision that appears to prohibit developers from tinkering with any Apple software or technology, not just the iPhone, or “enabling others to do so.”
Apple Owns Your Security: Section 6.1 explains that Apple has to approve any bug fixes or security releases. If Apple does not approve such updates very quickly, this requirement could put many people in jeopardy.
Kill Your App Any Time: Section 8 makes it clear that Apple can “revoke the digital certificate of any of Your Applications at any time.” Steve Jobs once confirmed that Apple can remotely disable apps, even after they have been installed by users. This contract provision would appear to allow that.
We have some other concerns as well, but these top the list.



So here’s the thing: this is almost certainly wrong. Not even controversial. Just wrong: broken windows policing may well have been helpful in reducing New York’s crime rate, but there’s flatly no evidence that it’s been pivotal. It’s true that crime in New York is down more than it is nationally, but that’s just because crime went up more in big cities vs. small cities during the crime wave of the 60s through the 80s, and it then went down more during the crime decline of the 90s and aughts. Kelling and Bratton can dismiss this as ivory tower nonsense, but they should know better. The statistics are plain enough, after all.
Take a look at the two charts on the right. The top one shows crime declines in six of America’s biggest cities. As you can see, New York did well, but it did no better than Chicago or Dallas or Los Angeles, none of which implemented broken windows during the 90s. The bottom chart is a summary of the crime decline in big cities vs. small cities. Again, the trend is clear: crime went up more during the 80s in big cities, but then declined more during the 90s and aughts. The fact that New York beat the national average is a matter of its size, not broken windows.


