All of a sudden, Apple lowered down its guard a bit and allowed cross-compilers in the App store, a reversal of its very stringent rules on what to be sold on the App Store. Backed by a quite strict App Store Review Guidelines, Apple has set ground rules not only the kinds of tools that can be displayed for Apple users’ consumption but it also outlined the things that will block an item from getting displayed at all.
Now this U-turn on specific regulations on some of its most basic sources will impact a lot of things in the Apple application development arena, and eventually the end users.
This all started with the very unyielding sets of standards and the rigid review process applied by Apple on its app developers back in March of 2008 when the first SDK specific to the iPhone was launched. Apple made it absolutely apparent that it will be very unswerving in its mobile applications. More of this type of consistency was manifested when programs were pushed to use Objective-C and the Cocoa Touch framework. In those days, the Mac application developers were also the iPhone app makers and cross-platforming was never such a big issue yet until eventually the focus was all on the mobile platforms because everybody was hooked on anything that can be hidden in a bag or kept in the pocket.
In all the haste to come up with integration and enhancement of the mobile gadgets, it was inevitable for Apple to get the service of third party toolkits, frameworks, and IDEs to facilitate the whole upgrading process. Open source implementations were applied to make iPhone apps. Flash, being unavailable currently on the iPhone(which is causing magnificent losses in sales to the Android phones where Flash is available), is set to be utilized now in Windows platform to create better apps and then converted into a Mac file and afterwards submitted to the App Store for iPhone and other Apple mobile devices downloads.
This particular method may have been the culprit in the sudden scare in the Apple world and even Steve Jobs himself defended the move saying that apps “created using non-native toolkits are slower and can be buggier and less responsive than their native counterparts. In other words, this was a quality assurance move”.
You must log in to post a comment.