PhoneGap-built apps getting the digital shaft?

Developing and programming applications for any device is by far no easy task. It takes a certain skill and person to carry out such tasks. The iPhone has created many overnight sensations and wealth by giving the average Joe a chance at stardom and fame. However, because of the iPhone’s multiple languages used, developing for the platform can put many people off as they simply don’t have the time, will, or money to learn new programming languages. However, a clever development platform that goes by “PhoneGap” allows developers to develop across multiple platforms using only HTML and Javascript opening the door to a much larger pool of people. In return, we get better apps as well as a larger selection. Choices are always good. Though the path isn’t a nice straight green one. Apple apparently though sadly unsurprisingly has a few problems with this.

Apple may be singling out these PhoneGap-built apps as a large number said built apps are being rejected from Apple. According to an open letter posted by Mike Nachbaur, a now disgruntled iPhone developer, he shares with us his rejeciton notice from Apple which says:

Upon review of your application, cannot be posted to the
App Store due to the usage of private API. Usage of such non-public
API, as outlined in the iPhone SDK Agreement section 3.3.2 is
prohibited:

” An Application may not itself install or launch other executable
code by any means, including without limitation through use of a plug-
in architecture, calling other frameworks, other APIs or otherwise.
No interpreted code may be downloaded and used in an Application
except for code that is interpreted and run by Apple’s Published APIs
and built-in interpreter(s).

The PhoneGap API implemented in your application is an external
framework.

PhoneGap is merely a tool to help make the iPhone better and Apple and their ever so intelligent approvers and approval process are hindering that process. Of course, there could be several problems with PhoneGap that Apple simply isn’t sharing.

The biggest and most obvious problem would be if PhoneGap isn’t supported or doesn’t work under iPhone OS 3.0. But if that is the case, why doesn’t Apple say that so that the PhoneGap team can fix the problem before it becomes a real headache after 3.0 arrives?

Another feature unique to PhoneGap is the “Online Mode” which allows developers to change code after it’s already on another device. Obviously there could be problems there that Apple doesn’t want to touch. It’s best to keep Pandora’s box closed as long as possible in regards to iPhone’s and viruses/web based attacks.

And finally, another feature of PhoneGap that I’m sure leaves a bitter taste in Apple’s mouth is the cross platform support. Apple has a history of a being a very closed and resistent to popular demand sort of company. (Look how long it took copy&paste to officially come to the iPhone). Apps built on PhoneGap can more or less be ported between other mobile devices making iPhone apps less “unique” in the sense that other platforms and manufacturers can beneft – a big no no from Apple’s standpoint.

So what is the real reason a great developer tool such as PhoneGap is getting the shaft? Until Apple opens their mouth and lets us in on the real reason all we can do is speculate and fume. Is this a sham?

Source: NYT, PhoneGap