Unity and other 3d-party engines safe from the Great Flash War of 2010
With all of the hype surrounding the magnificent iPhone 4 and the imminent release of the iOS 4.0, Apple has snuck in an amendment to their infamous and controversial ToS 3.3.1 that made it seem no code interpreters, other than Apple’s are allowed. What this did originally was bar all of the would be Flash-to-native-iOS apps created using the Adobe CS5 suite from ever hitting the AppStore.
At the same time this paragraph technically made all of the widely distributed multi-platform engines, like Unity as the most widely known example, illegal. Despite this, the extent to which Apple was going to enforce this rule was uncertain. Thankfully, with the latest change it is obvious Apple was a bit harsh in their original implementation of the rule and have appended ToS 3.3.2, stating that with Apple’s prior written consent an app may use embedded interpreted code in a limited way if such use is solely for providing minor features or functionality (full wording after the gap).
Whether this will truly exclude the developers using tools such as Unity remains to be seen, but it is definitely an indication that the big A wants to calm the community down a bit.
3.3.2 An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise. Unless otherwise approved by Apple in writing, no interpreted code maybe downloaded or used in an Application except for code that is interpreted and run by Apple’s Documented APIs and built-in interpreter(s). Notwithstanding the foregoing, with Apple’s prior written consent, an Application may use embedded interpreted code in a limited way if such use is solely for providing minor features or functionality that are consistent with the intended and advertised purpose of the Application.