New iPhone Developer Agreement Bans the Use of. Thursday, 8 April 2010 Prior to today’s release of the iPhone OS 4 SDK, section 3.3.1 of the iPhone Developer Program License Agreement read, in its entirety:
Steve Jobs Has Just Gone Mad. Today Apple announced a version 4 their iPhone OS.
It seems to answer most of the open issues relating to the platform. All sounded good. But then, John Gruber over at Daring Fireball discovered a "hidden gem" in the new developer terms. His Dashboard App For iPad Rejected, Developer Publishes Code On. Apple Crushes Adobe’s iPhone App Dreams. UPDATED So much for Adobe trying to provide a workaround for Flash developers to create iPhone and iPad applications.
Apple today fired its latest salvo in its war against Flash, with an update to its iPhone Developer Program License Agreement that specifically bans the use of third-party compilers for creating apps that will run on the iPhone OS. As pointed out by Daring Fireball’s John Gruber, the language in the license agreement has become much more aggressive, if not downright antagonistic, against applications not written in Objective-C, C, C++ or Javascript. Apple's Mistake. November 2009 I don't think Apple realizes how badly the App Store approval process is broken.
Or rather, I don't think they realize how much it matters that it's broken. The way Apple runs the App Store has harmed their reputation with programmers more than anything else they've ever done. Their reputation with programmers used to be great. Game Haxe » Blog Archive » Bravo, Apple. Finally, Apple is doing away with those arrogant upstarts who think then can write a few lines in a high level language and call it a program.
Their new developer agreement requires: 3.3.1 – Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).
This has a couple of good points – firstly banning stupid languages (used by those people who are not smart enough to learn c++), and secondly getting rid of translation layers. Languages The new langages, such as haxe, are so terse that you do not even know when you are using a delegate. Is Steve Jobs Ignoring History, Or Trying To Rewrite It? Very few people get the chance to make history.
Even fewer get the chance to make it twice. Perhaps that is why it is so fascinating to watch Steve Jobs as he tries to usher in the era of mobile touch computing today, just as he ushered in the era of the personal computer three decades ago. But I wonder whether he is repeating the very same mistakes which relegated Macs to a niche market. Or did he learn from those mistakes so that Apple comes out on top this time?
Jobs is once again pitting Apple’s complete product design mastery against the rest of the industry, except this time he thinks he will prevail. Developers and pundits can cry foul all they want about Apple’s lack of openness. In the desktop era, Windows had the most apps, which translated directly into sales. The App Store platform could turn into a long-term de facto standard platform. But how long will that license last? Of all people, surely he sees what is coming. The State Of Web Development Ripped Apart In 25 Tweets By One Ma. There are few people who know the ins and outs of the web as well as Joe Hewitt.
For the past decade, he’s had his hands deep in everything from Netscape, to AOL, to Firefox, to Facebook (where he currently works). Hewitt also knows a thing or two about the iPhone. He’s the one who first built Facebook’s excellent iPhone web app (before there were native apps on the iPhone), and then the native app — which is one of the best apps on the platform. Apple's Tightening Grip: This Could Be Android's Big Chance. The long-closed nature of Apple's iPhone OS ecosystem is coming to a head with the addition of major new restrictions on developers.
If there ever was a time when the Android world had a chance to out-innovate Apple, this could be it. Each day this week, developers have pointed out another indignity Apple's legal framework subjects them to. Could this be the pressure that gets resolved by the rise of a compelling Android offering? It seems like a long shot. Saying Goodbye to Apple → benjaminthomas.org. Jobs' latest act of villainy has less to do with Adobe than Grub.
Apple Gives Adobe The Finger With Its New iPhone SDK Agreement. Earlier today, Apple held its iPhone 4.0 event, where it showcased some of the new features the latest release of the mobile OS will offer.
Appsfire dumps iPhone App store after 2 month wait for update. Apple’s iPhone app store approval process is famed for its inconsistencies, but today the developer of a popular iPhone app has had enough.
Appsfire, an app for discovering popular iPhone apps, was approved in its version 1.0 form last August, but after two months its version 2.0 has not been approved, despite repeated calls by the startup to Apple, they claim. In an excoriating blog post today, founder Ouriel Ohayon effectively accuses Apple of not approving its latest update because Apple wants to keep discoverability to itself: “Your approval process is full of holes; you have approved Appsfire v1.0 last August and wished you hadn’t because almost no one had any real clue about discoverability issues back then – indeed, we were the very first to address this issue in an app. Now you know what’s at stake, so you’ve locked-down every aspect of the SDK ToS. He says they are pulling out because v1.0 is outdated and not serving its users. They’ll now be considering out-of-store alternatives.