Friday, July 17, 2009, 12:25 pm
Developers claim Apple rates all browser-embedded apps mature
Apple has caught the ire of some developers this week after it was revealed that all applications with integrated Web browsers will reportedly be rated for ages 17 and up, and that all such apps will not be entitled to promotional codes.As first reported at The Unofficial Apple Weblog, the App Store's new app rating system prevents developers from obtaining promotional codes for their applications. Such codes allow up to 50 free downloads for developers to distribute however they see fit, such as for publicity or promotion.
"As it stands, neither the 3.0 software nor iTunes display parental warnings when using a promo code to purchase apps with a mature (17+) rating," TUAW writes, "so Apple has made the promo code functionality unavailable for apps that fall into that category. We were informed of this condition by a developer who prefers to remain anonymous."
This has upset some developers, such as the creator of Instapaper and Tumblr, Marco Arment. The developer conveyed his frustration in a blog post Friday, saying he now doubts the viability of a business based on iPhone apps. Arment has expressed his displeasure with Apple before, specifically with regards to the iPhone maker's alleged unwillingness to answer developers' questions.
Now, Arment claims that Apple takes 8 to 30 days for review, and all Web-capable applications must come with nudity warnings.
"Theyre making a killing taking their 30% commission on the 1.5 billion copies of $0.99 top-25 games that theyve sold," he wrote. "Who cares if the App Store discourages good developers from putting serious effort into it? Apple doesnt need to care. And, clearly, they dont."
With iPhone OS 3.0, Apple added an age rating system for applications. This not only allows parents to set appropriate application access for their families, but also opens up the potential for developers to release applications with adult content.
Friday another developer also complained about the length of time in Apple's App Store approval process. Syncode, the developer behind the application iTweetReply, claims that Apple tested their application merely a few days after its submission to the App Store, but didn't provide a formal rejection until nearly a month later. The reason for the rejection: An illustration of an envelope displayed when the application launches included Apple's address, 1 Infinite Loop in Cupertino, Calif.
After the developer revised the application, it was approved two and a half weeks later.
"My personal guess is that once an app passes the initial technical test, it must be approved by multiple other levels from legal (to prevent illicit apps) to, well, God knows," Matthew Lesh of Syncode wrote. "If nothing else it has highlighted the need for a far more transparent approval process Come on Apple, is it so hard to give us at least a quasi-detailed description of the approval process?"
On Topic: iPhone
- High resolution images claim to show 'iPhone 5S' and iPhone 5 display assemblies side-by-side
- Briefly: Sprint LTE service expands to 22 more areas
- Inside iOS 7: Apple's Weather app gets animated
- Case intended for Apple's low-cost iPhone shows thicker, rounded design
- AT&T starts nationwide FaceTime over cellular rollout





Want to write for AppleInsider? Submit your application now!



In a future update, to separate the Safari/Browsing abilities from the App ratings altogether. You can already turn them off independently, but a .x update will need to allow developers to access these settings through an API and have the software be able to disable browsing features if the user has turned these off. This would allow the App to still be rated according to its unique content, and still protect the poor, innocent youth of America. That, or people could just could making frivolous lawsuits every time they feel the need to blame their parenting errs on corporations. Apple shouldn't be expected to risk their ass, or the livelihood of the App Store itself (especially in an age where we have an Internet "Czar") just because a few developers can't figure out how to lock their apps down, or don't see the potential hazard in not doing so. That being said, I do think my above solution would work, and would probably be as easy as several lines of code to implement into an App. Just my thoughts.