Slashdot Mirror
Apple Relaxes iOS Development Tool Restrictions
An anonymous reader writes "Earlier this year Apple caused major upset among developers by updating the iPhone developer program license with clause 3.3.1. It basically stopped the use of cross-platform compilers, meaning Adobe Flash could not be used to develop an app for the App Store. The move also put into doubt which other development platforms could be used and generally caused a lot of confusion. Apple has just significantly relaxed that policy and allowed for the use of development tools, as long as 'the resulting apps do not download any code.'"
More importantly, developers will no longer have to second guess the reasons why apps may or may not be accepted. From the statement:
"In addition, for the first time we are publishing the App Store Review Guidelines to help developers understand how we review submitted apps. We hope it will make us more transparent and help our developers create even more successful apps for the App Store."
webkit is exempt.
Written like a true slashdotter who didn't read the article.
Let's clarify, since the description isn't that great. Apple will now allow Adobe's Flash to export in iPhone app format
Also, Apple released their App Store Review Guidelines (PDF). Worth a read.
there is no way for an anticheat system to update itself.
What's to prevent the game maker from simply issuing a software update, and having software issue challenges to each other related to versions before accepting games?
Online cheating is not as great a problem as with the PC's or consoles.
It only takes a few seconds to update a new version on the device.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
That's because the rules against interpreted code are part of the SDK rules not the app approval guidelines.
Sure, so how does Skype get through.
Because it doesn't duplicte existing functionality. There is no built in VOIP client, and it uses the Apple contacts. GV linked back to Google contacts...
In fact, how do most apps get around points 2.11-2.13?
2.11 Apps that duplicate apps already in the App Store may be rejected, particularly if there are many of them
At this point that might be a problem for some applications but there's always a new idea without many apps in the store.
2.12 Apps that are not very useful or do not provide any lasting entertainment value may be rejected
I think you might just be able to work around that by writing an app that is useful or entertaining.
2.13 Apps that are primarily marketing materials or advertisements will be rejected
To me that simply repeats point 2.12 since an application that is primarily marketing is also not useful (though I suppose it could be entertaining, and thus possibly accepted).
I would say the vast majority of apps in the store fall under these points.
Like what? Very few of the applications I have seen fall under these points, except possibly for point 2.11 - but that's the thing, the avoidance of replication is more a point going forward than it has been (though Apple has been starting to reject some applications in crowded categories).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I think this line from the guidelines is pretty funny:
"If your app is rejected, we have a Review Board that you can appeal to. If you run to the press and trash us, it never helps."
So basically, don't snitch.
To the contrary, however, in the past, it seems like running to the press and trashing them can really help get your app approved.
See, e.g. http://apple.slashdot.org/story/10/04/16/2327219/Bad-PR-Forces-Apple-To-Reconsider-Banning-Mark-Fiores-App
Also, you say, "That's why I prefer to work with iOS development, because they do listen to developers and take into account feedback or concerns, and really change fundamental policy instead of continuing said policy just because it exists as so many other companies would do..." Has there been any fundamental policy shift before today? If not, what were you saying prior to today on why you prefer to work with iOS development?
They listened to developer demand and introduced an SDK and stopped allowing only HTML5 web apps. They allowed turn by turn navigation products. And neither of those were really influenced by the rising success of Android, at the time. I could probably think of a few more, but you asked for "ANY", of which two satisfies.