Still that’s the process Apple’s had in place ever since the company first disclosed plans for the App Store nearly a year ago. And it’s helped create an online store that Apple chief operating officer Tim Cook called “absolutely the envy of the industry” during this week’s Apple shareholders meeting.
Nevertheless, it’s safe to say that the process Apple uses to decide which apps are acceptable and which aren’t is less than transparent—a fact that remains a sore spot for some iPhone developers. Apple didn’t respond to a request to explain its process for this article.
However, given some of the high-profile App Store rejections in the seven-plus months since the store opened its virtual doors, a picture is beginning to emerge—albeit only part of one—on what kinds of iPhone apps run afoul of Apple’s guidelines.
“After a couple of attempts to get the application approved, we are sad to say that our app has been rejected. According to Apple, the content was ‘potentially offensive,’” reads the post on the South Park Studios Web site.
The door hasn’t been completely closed for a South Park app. According to the developers, Apple said that standards evolve, noting the iTunes Store didn’t initially offers songs with explicit lyrics when it launched. Still, South Park Studios say, at this stage, the app is “dead in the water.”
Apple also rejected developer Adrian Ross’s remote access app, FarFinder, for displaying trademarked Apple icons. In his blog, Ross posted Apple’s rejection reason: “Using your application, when the user logs in to the machine, the default OS X directory and file icons are displayed.” But Ross argues that several iPhone VNC apps also show Apple’s icons, although those apps display what’s on a computer’s actual screen, while FarFinder has its own interface.
Of course, Podcaster famously got the cold shoulder because it “duplicate[d] the functionality of the Podcast section of iTunes.” (The app did finally make it onto the App Store in a different form as RSS Player). MailWranger met with a similar fate; developer Angelo DiNardi said he was told by Apple that his effort was rejected because it “duplicates the functionality of the built-in iPhone application Mail without providing sufficient differentiation or added functionality, which will lead to user confusion.”
Apple has also cited “inappropriate sexual content” and “ridiculing public figures” in other cases of app rejections gone public. (Our colleagues at PC World have assembled a list of 10 such rejected applications.)
One company, 10base-t interactive, even created an Unofficial App Store Rejection Criteria Web page based on developer experience. Originally featuring 10 reasons for rejection—the tally is down to nine now that the surplus of gas-passing simulators has rendered the “No Flatulence” rule moot—the list covers everything from having an app that continuously vibrates to problems with tableviews.
A silver lining
But at least one developer thinks Apple’s tight grip is a good thing. Glenn Howes, creator of the Lullabies app, wrote on his blog that Apple rejected his first attempt for violating Apple’s interface guidelines. (In his original app, there was no way to return to the main menu until a chosen animation had played through). Howes added a button, and also used the opportunity to make a few other tweaks as well.
“And in the end, I have a much more responsive app,” Howes wrote, “and code which I’ll be able to reuse in future projects.”
Does it matter?
If you want an app for your iPhone, the only place to get it is through the App Store (unless you jailbreak your iPhone, of course). In Apple’s collective mind, controlling what’s available to iPhone users is both a means of assuring a high-quality experience for its users and a way to rake in 30 percent of every sale.
But Apple now faces competition from other smart phones with the launch of the Google Android Market, as well as Microsoft’s upcoming Windows Marketplace for Mobile. Will Google and Microsoft help put Apple’s feet to the fire and cause Apple to change its policies (or at least make the app process more overt)? Or is the strength of the iPhone enough to insulate it from the competition?
These other avenues offer developers more options when creating mobile apps, and it would be a shame if Apple’s difficult and seemingly arbitrary ways drove talented developers away from the iPhone. (The image of a tunic-clad, flute-playing Steve Ballmer leading developers to Redmond comes to mind). But at least for now, there’s good money to be made on the iPhone, and it still exudes that must-have vibe that Apple is known for.