Affected by Apple’s 3.3.1 rule? Here’s something you can do

Many developers and businesses are being massively affected by this little addition to the developers agreement.  Some of us have new apps that are nearly done, some of us are companies with real projects already on the books and starting development, some are the actual tool makes (like Unity and adobe) who are now loosing massive amounts of possible money.

We’ve heard all of the reasonings as to *why* apple would do this, but here’s a reason not to:  Apple needs realize that the reason they have such a massive appstore catalog is BECAUSE of the 3rd party apps.  I’m willing to bet that at least 50% (that’s a safe bet, I think it’s actually much higher ) of the games in the appstore are created with tools other than Xcode.  it’d be interesting to see, in their tv commercials, HOW many of the apps displayed were created with non Xcode tool kits – that’d be VERY interesting indeed.

So, if you’ve created an app, or know of an app that was created with a 3rd party tool like Unity, please take a moment and check to see if the app is listed in this spreadsheet.  If now, please add it:
PS> if you can’t get it to load initially, keep trying – there’s a ton of traffic 😉

  1. Apple is not forcing anybody using XCode, they say that you have to use C, C++, Objective- C or javascript. As far as I know all these languages can even be mastered using something like VIM ;).

    They are reject apps that are not written in the above mentioned languages because the developer cannot predict the performance etc of the app.

    I think that they can better reject apps on performance measures (I have used Flash CS5 iPhone export and the performance is at this point not quit good).

      • Me
      • April 13th, 2010


      Are you trying to say that you cannot write a bad-performing app in “C, C++, Objective- C or javascript”? Cover up your Apple tattoo fanboy and shut the HELL up until you know the facts and not the Apple propoganda.

      And yes, they ARE forcing people to use a certain language – RTFM – and it’s ONLY to hurt companies like Adobe. Go away.

    • Jonathan
    • April 13th, 2010

    If your going to reject 3rd party apps due to performance standards then publish the performance standards. I can write a poor performing app in c, c++, objective-c, or javascript.

    Apple needs to open their standards and let everyone be accountable, even themselves.

    • give it a rest already
    • April 14th, 2010

    “The reasoning behind Apple’s intransigence is that private frameworks are, according to the company, “works-in-progress” that have not yet been finalized and could change at any time in the future. If this were to happen, any app built using the functionality provided by them would stop working, leading to all sorts of incompatibility problems that Apple, as the ultimate gatekeeper of the App Store, would have to deal with. Public frameworks, on the other hand, are guaranteed to stick around for a really long time—on some platforms like UNIX, they have stuck around for decades—therefore guaranteeing long-lasting compatibility with any software that uses them.”

  2. So…If performance is the issues – what if I write it in Assembly ? Will that be rejected ? – My point is, what if that intermediate layer _did_ produce a better performance – will that app be rejected ?

    • Peter
    • April 16th, 2010

    Couldnt we organize more? ignore the app store for a day or week? something like this?

    or just the opposite:
    making apps with flash, unity, monotouch and load them up at the same day. that would be fun 🙂

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s