Honestly, I still think people writing native code and using the native APIs for a platform like the iPhone is something worth enforcing. On the desktop multipl

Honestly, I still think people writing native code and using the native APIs for a platform like the iPhone is something worth enforcing. On the desktop multiplatform development toolkits consistently fail to deliver a user experience that is seamless and on par with apps built with the native APIs (especially on a platform with different interface conventions and guidelines, ie Mac OS) and for a platform such as the iPhone where resources are not infinite, and the interface is especially important, it just makes sense to enforce people doing things 'properly'. If that knocks out a few decent applications along with all the lazy, rubbish ports then I think that's acceptable. If they're really that amazing, then they probably justify being rewritten natively. One place where I do have issue with this policy is in the case of game engines/middleware (ie. Unity). Due to the complexity and development requirements of game middleware I think an exception, or a more refined policy, is required to allow middleware to give the required 'leg-up' to game developers. Additionally, while Apple has provided an awful lot of what developers need to create great View-based applications for the iPhone with Cocoa Touch (within the constraints what third-party apps are allowed to do, at least), they haven't done so for games. This is understandable, again due to the aforementioned complexity of game engines, but it makes games a special case.