Mobile // Mobile Applications
News
9/3/2014
09:06 AM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Apple's Top 10 Reasons For App Rejection

Developers keep submitting apps that violate Apple's rules.

IT Job Interviews 101: What Not To Wear
IT Job Interviews 101: What Not To Wear
(Click image for larger view and slideshow.)

Apple has a message for its developers: Read the @#$% manual.

Though Apple is far too reserved to actually let the expletives fly -- unlike former Microsoft CEO Steve Ballmer, if Mark Lucovsky's testimony is to be believed -- the company has for the first time published data about the reasons iOS and OS X apps get rejected by its app review staff, to stress the importance of becoming familiar with its app review criteria.

"We've highlighted some of the most common issues that cause apps to get rejected to help you better prepare your apps before submitting them for review," Apple explains on its website.

Apple requires that apps submitted to its App Store and Mac App Store meet a long list of technical, content, and design requirements. Initially, the company disallowed registered developers from discussing its requirements through a non-disclosure agreement. But in September 2010, after a number of controversial app rejections, the company made its app review rules public.

Apple's requirements are more numerous and broader in scope than Google's rules for Android developers. Both companies ban apps that attempt to deceive or violate laws or community standards. But Apple's rules give it the latitude to ban pretty much any app because it's not sufficiently useful or is somehow offensive.

[Not our fault, says Apple in celebrity photo hack. Read Apple Not Hacked In Celebrity Nude Photo Breaches.]

Both companies gain coincidental competitive benefits from bans issued ostensibly for the benefit of customers or other developers: Apple's refusal to allow iOS browsers not based on WebKit gives it control of mobile browsing on iOS devices, while Google's recent ban on Disconnect Mobile makes mobile ads more profitable.

But Google takes a more permissive approach, letting developers publish apps to Google Play without review and only removing apps when violations are discovered. Apple tries to be more careful. It employs a large number of app reviewers who approve every app before the app is admitted in its App Store or Mac App Store. Each approach presents advantages and disadvantages.

One disadvantage for Apple appears to be that too few developers actually bother to familiarize themselves with Apple's rather lengthy set of rules. By publishing the most common reasons it rejects apps, Apple aims to improve app quality and to lighten the workload of its review staff.

Here's what Apple's developers are doing wrong. Below are the 10 most common reasons Apple's reviewers reject apps, representing about 58% of all app rejections during the seven-day period ending Aug. 28.

14% -- Incomplete information
When submitting apps for review, developers must provide a substantial amount of information, from specific files to updated contact information. Unsurprisingly, many developers omit a few required details.

8% -- Crashes and bugs
Software has bugs. There's no way around it. But thorough testing can get rid of most of them. A fair number of developers appear not to be very conscientious about debugging. But Apple's review process may be part of the problem: Because it tends to take about a week from the time an app is submitted until it is reviewed and approved, developers who discover bugs after their app is submitted may be disinclined to halt the review process and restart the clock with a revised app submission. Apple should consider a way to submit a new app binary for review without affecting the app's place in the review queue.

6% -- Failure to comply with developer license agreement
This could be anything, from breaking Apple's non-disclosure agreement terms to using private APIs to inappropriate use of Apple intellectual property.

6% -- Ugly interfaces
Apple review guideline 10.6 says, "If your user interface is complex or less than very good, it may be rejected." Beauty is not in the eye of the beholder; it's a determination made by Apple.

5% -- Metadata misuse
Guideline 3.3 says, "Apps with names, descriptions, or screenshots not relevant to the App content and functionality will be rejected." These are likely to be scammy bait-and-switch apps.

5% -- Icon hijacking
Guideline 22.2 says, "Apps that contain false, fraudulent or misleading representations or use names or icons similar to other Apps will be rejected." Unethical developers will often clone successful apps and market them with confusingly similar icons or names.

4% -- Name mismatch
Apple wants app names in iTunes Connect (its developer console) to be similar to the name an app displays on a device.

4% -- Placeholder content
Apple will reject apps that have placeholder text in the app metadata, which gets displayed in App Store listings.

3% -- Missing or inaccurate app ratings
Apple asks its developers to assess the age appropriateness of app content. Sometimes developers may err, cynically (in an effort to maximize the audience for an app) or innocently (when the developer's interpretation of, say, cartoon violence differs from Apple's).

2% -- Forbidden labels
Apple says it will reject apps labeled "beta," "demo," "test," or "trial." Yet somehow, 2% of developers submitting apps for review are labeling their apps using these terms.

Apple deserves credit for publishing this information, which brings more openness to the company's relationship with its developers. In so doing, the company is broadening the commitment CEO Tim Cook made two years ago to be more transparent in terms of supplier and environmental responsibility.

You've done all the right things to defend your organization against cybercrime. Is it time to go on the offensive? Active response must be carefully thought through and even more carefully conducted. This Dark Reading report examines the rising interest in active response and recommends ways to determine whether it's right for your organization. Get the new Identifying And Discouraging Determined Hackers report today (free registration required).

Thomas Claburn has been writing about business and technology since 1996, for publications such as New Architect, PC Computing, InformationWeek, Salon, Wired, and Ziff Davis Smart Business. Before that, he worked in film and television, having earned a not particularly useful ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Gary_EL
50%
50%
Gary_EL,
User Rank: Ninja
9/3/2014 | 11:01:33 PM
Re: Nice to have public now
I've noticed that many of the people I know who are some combination of non-technical, not interested in computers, and can afford to pay a lot more for convenience prefer Apple, because for many of theses folks' purposes, all you have to do is plug it in, turn it on, and get to work. Not that you can't get just as technical as you care to with Apple, but if you don't want to, you never have to.
zaious
50%
50%
zaious,
User Rank: Ninja
9/3/2014 | 10:33:39 PM
A good rubrik
It is a good gesture from Apple's part to inform its app developers what was going wrong. They now know what can be the potential problem and fix them before submitting. These minor issues might have prevented many great apps from being released. It will benefit users (more apps), developers (less rejections) and reviewers (less failures while testing) -everybody wins!
Michael Endler
50%
50%
Michael Endler,
User Rank: Author
9/3/2014 | 7:58:11 PM
Re: Nice to have public now
Yeah, I was thinking something like that too, Gary. Apple keeps a tighter leash than some would like, but it generally helps ensure that the experience remains at a high level.
Gary_EL
50%
50%
Gary_EL,
User Rank: Ninja
9/3/2014 | 2:54:48 PM
Re: Nice to have public now
This is surely one of the reasons people are willing to pay more for Apple products. Everything is super-solid before it's released to users, so nobody is dragooned into being a volunteer beta-tester.
anon1866207628
IW Pick
100%
0%
anon1866207628,
User Rank: Apprentice
9/3/2014 | 11:25:00 AM
Nice to have public now
Millions of apps are submited to Apple for review, this article would be very helpful to a developer who hasn't successfully submited an app before. Always good to submit Beta projects on google and then fix issues before attempting release on Apple. 

Sincerely,

Misty

www.ABMobileApps.com
Building A Mobile Business Mindset
Building A Mobile Business Mindset
Among 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps and it's past time for those with no plans to get cracking.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Tech Digest, Dec. 9, 2014
Apps will make or break the tablet as a work device, but don't shortchange critical factors related to hardware, security, peripherals, and integration.
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
Join us for a roundup of the top stories on InformationWeek.com for the week of December 7, 2014. Be here for the show and for the incredible Friday Afternoon Conversation that runs beside the program!
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.