Apple Reveals the Most Common Reasons That It Rejects Apps
mrspoonsi writes One of the great mysteries of the App Store is why certain apps get rejected and why others don't. Apple has let a surprising number of ripoffs and clones through the store's iron gates, yet some developers face rejection for seemingly innocent apps. "Before you develop your app, it's important to become familiar with the technical, content, and design criteria that we use to review all apps," explains Apple on a new webpage called "Common App Rejections." Rejections include: Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good, it may be rejected; Apps that contain false, fraudulent or misleading representations or use names or icons similar to other Apps will be rejected.
There's not enough fingers in the world to count all the awful apps that violate most of Apple's so-called "standards."
My favorite are the apps that have a string of words from other popular apps' names in them, just to muck up the search results. And they make sure to periodically change the icon to look like another app as well.
Also if they're free as in freedom.
Apple PR again. In light of good press from Microsoft and android simply having more apps. IOS is falling behind in both quality and quantity. Posted from a 5.5" phone
In other words, if your not uncool like all the other uncool kids you cant stay in the uncool crowd...
I've had an app in the store for years now that requires a login. We provide two to apple to test (one success one fail). I don't recall the last time the accounts logged in (perhaps version 1.0.0.0), their last login date has sat the same for years. So, not hard if you get in and sit there to slowly change to something malicious.
I have dealt with App Store rejections on various projects, and it was quite a culture shock coming from the desktop development world. In many ways it reminded me of college. Giving the right answer is not important per se, but rather just providing the answer you know the professor/grader wants to hear. As a programmer, it rankles me for someone else to dictate major issues of app architecture that touch on quality in a debatable way.
/slight-exaggeration
But it's their way or the highway if you want to sell to iOS users. And yes, you do want to sell to iOS users. Android users never spend any money.
Such a subjective phrase. Looking at the App Store I doubt they even begin to comprehend its meaning. For every semi decent app there are a few thousand absolute shites copying the function. For every blockbuster app there's a few million trying to be it.
Absolute rubbish.
All the better to limbo under...
I though the most common reason was bypassing the iTunes pay wall by using their own mechanism for in-app purchases.
What is this, amateur hour? Why does Slashdot constantly rehash the "reasons Apple rejects apps" topic? They've published detailed guidelines on this for years. If you're developing for iOS, read them.
Apple obviously does not deeply review each and every entry. Many of the apps would hardly even stand up to a glance. So how can they arbitrarily say that an interface is too complex if they do not even spend the time to learn anything about the app.
Troll is not a replacement for I disagree.
Does that include protecting your cloud apps with basic security so that pics of Jennifer Lawrence's pussy don't get leaked?
SJW's don't eliminate discrimination. They just expropriate it for themselves.
thankfully, no.
Sometimes it's ok for me it the UI of an app it's not so great as long as it does the job which i need to be done right now. (e.g. importing/converting files formats, unusual calculations etc....)
I feel like this is basically the same issue as the "Displaying Top Apps" discussion from a while back. There's no great way or perfect rule to solve the issue. You somehow need to make it flexible enough to be able to work for every possible kind of app, but also strict enough to keep out the riff raff. You have to make some kind of judgement to help the user and the developer both... which at some point will annoy both parties. In my experience, it works well enough. Sure it could be better (and also worse), but it seems to do the job well enough.I just feel like by making them stricter it'd have plenty of seen and unforseen consequences.
Why does Slashdot constantly rehash the "reasons Apple rejects apps" topic?
To help certain iOS fans who frequent Slashdot (BB, SK, etc.) understand why not all apps are ported to iOS and why some people choose devices that run something other than iOS. The featured article states that most applications that Apple rejects are broken in some important way. But conspicuous by omission are apps that aren't broken but which Apple rejects for other reasons.
They've published detailed guidelines on this for years.
Only very recently (a few months ago) has Apple made the guidelines available to the public. Previously you had to sign up for the paid iOS Developer Program just to see them. That hurt people who bought a Mac and an iOS device to start developing, only to learn that the application's concept was in a category of applications that Apple completely rejects. That's entire sections of the market that Apple has made a business decision to decline to serve.
Not enough lasting value
If your app doesn’t offer much functionality or content, or only applies to a "small niche market", it may not be approved. Before creating your app, take a look at the apps in your category on the App Store and consider how you can provide an even better user experience.
You mean Like Apple? i know troll hahahaha
or only applies to a small niche market, it may not be approved
I've got android apps with only 5-10k downloads, but they fit my needs. One is Fulio Pro, a nice little application for tracking fuel usage and car expenses, the developer has been very open to enhancement requests and quick to respond on bug tickets. The guy certainly hasn't gotten rich at $10-20k in earnings from the paid app, but he's got some income and I have a useful application.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
Instead of putting an application in the App Store, a developer could usually create the application as a web application using Safari JavaScript. Web apps can even run offline now if needed.
Most of the apps I have seen get rejected are due to the developers not reading the agreement they clicked through on their way to paying the $99 to publish their app. They develop something before they find out what is verboten and then get upset when the app gets rejected. I have been developing apps for the App Store since 2009 and have yet to get one rejected, for any reason. All the stories I hear are from devs that thought they could do whatever they wanted, use any API and get their app through. That's just not how it works.
Talk about ugly as f***...
Loading...
If your app doesn’t offer much functionality or content, or only applies to a small niche market, it may not be approved.
Not long ago Apple used to be niche market.
So that sort of undermines their credibility in judging other people's work on the basis of usability, doesn't it? Also, the App store search is essentially broken. They should get their own house in order.
Still don't know why the truly tasteless jokes app was rejected.
http://www.trulytastelessjokes.com/protest/
I'm not sure that 5,000 downloads for an application that tracks fuel usage would be a "niche app" that Apple would reject. I think it's more like, if you released an app that was dedicated to the purpose of surveying Siberian tiger-moles for the purposes of determining fur growth and moulting during the leap-years, specifically in attempting to correlate growth to the frequency of solar flares, Apple might go, "Yeah, that could be a great app, but we don't see the point of putting it up in our store."
I think that it should be recognized that for all of these reasons that Apple might reject an app, they're probably looking for fairly extreme cases. Like they're saying that they can reject an application for being poorly designed, but I've seen plenty of ugly and cheap-looking applications in the iTunes store. They're probably just rejecting applications that are completely awful.
There is nothing preventing a developer from creating an OSX or iOS application that goes outside the guidelines provided they don't with to sell within the walled garden. But, if you want to sell to users using the app store, you are subject to their requirements.
This is true of OS X but not of iOS, because OS X has sideloading and iOS does not. There are exactly three ways to get an app installed on an iOS device. The first and most common is Apple's App Store. The second is being an employee of an established company that is a paying member of the iOS Developer Enterprise Program or a student of an accredited university that is a member of the iOS Developer University Program; such organizations are allowed to run their own App Stores. The third is to be a paying member of the iOS Developer Program yourself.
What would be nice is if Apple provided a separate area for this types of apps (classwork and developer portfolio apps) and leave real, useful and commercial quality apps, on the store.
In high school, classwork is done on OS X, which allows sideloading. In college, classwork is done through the iOS Developer University Program. A developer portfolio should use a combination of three methods: A. having one or more of your applications on the App Store to demonstrate that you are familiar with the skill of negotiating with Apple, B. videos, and C. demonstration on a device connected to a paid-up iOS Developer Program membership during an in-person interview.
They forgot to mention the rejections due to the App Store reviewer having had an argument with his SO that morning, or had a lousy breakfast, or sat in a traffic jam, or ...
I figured once this made it in, it was pretty much 'anything goes'.
Have gnu, will travel.
i have to hand apple one thing, about their walled garden. although i have some cool android apps on my phone, my wife's iphone is much more of a pleasure to use.
why? because, for example, there are ten thousand friggn' notepad apps for android, and i'm too lazy to find one that look like the rest of the android interface, so after browsing through a dozen, i just picked one...
click her notepad app, and it looks like im just smoothly entering another part of the iphone experience... ... click mine, and i'm launched into an ugly frenzy of badly placed wrongly colored controls etc with entry fields that behave strangely, and buttons with icons that i don't recognize.
when you have 1000 developers making 1000 apps that do the same thing, the only difference being how the ui looks, and none of them even match the rest of the operating system, you fucked up your operating system. that's android for you. nobody even knows what an android app is really supposed to look like anymore, and developers don't care, they're just off in their own little world with no taste in design.
graphical operating systems need fairly strict ui design conventions. period. they need to be breakable, but encouraged very strongly to the point of where breaking them for no reason makes your app seen as a peice of junk. this is apple's only real advantage in locking out outside apps, being able to blacklist ugly things.
i appluade them for attempting to force that kind of consistency on their device, not that it always works... no solution is 100%.
not that i'd buy an iphone myself, and you don't have to either. just sayin'.
Why stop at 5.5"? Wouldn't a 10, 20, or even 30" phone be more useful and impressive?
There are probably 10-20 applications in the Apple App Store that do fuel/vehicle expense tracking.
I don't think you are understanding what a niche really means...
There are also many, many applications that have received under 100 downloads so it's not like 5-10k is anywhere near a small amount they would reject.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
If Apple wants to doublespeak their way to victory, then their old 1984 commercial is rather sad. Next they'll be telling us that Firefox and Chrome weren't "up to snuff" rather than them just being scared shitless of some healthy competition in their walled garden. Next they'll be telling us that the intentionally crippled version of webkit they force competitors to use "had to be that way to protect the integrity of their ecosystem".
Also if they're free as in freedom.
With respect to he VLC media player ... Apple didn't care it was GPL, the developer was OK with the App Store, but a 3rd party threatened to sue Apple so Apple pulled the app.
... In a follow-up VideoLAN mailing list post, VideoLAN association president Jean-Baptiste Kempf wrote, "With 'friends' like you, we don't need any enemies. If I understand correctly, the FSF new policy is to blow up communities?""
"The iOS VLC app was created by Applidium, a French mobile software company. In an Ars Technica interview, Applidium co-founder Romain Goyet said "The way I see it, we're not violating anyone's freedom. We worked for free, opened all our source code, and the app is available for free for anyone to download. People are enjoying a nice free and open source video player on the AppStore, and some people are trying to ruin it in the name of 'freedom.'"
http://www.zdnet.com/blog/open...
The FSF argues that Apple prohibits modifying and/or redistributing the app. That is a somewhat bogus argument. The binary is digitally signed, it won't run if modified or transferred to another device lacking the appropriate key. However the source code is available. A user is free to modify and distribute in terms of source code. They can submit their modified alternative binary to the app store. They can give a few friends binaries via ad hoc distribution. Yes, this costs money. The GPL doesn't prohibit things costing money, you can charge for distribution if you like and people are free to ignore your distribution and go to the source code. Nor does the GPL doesn't mandate a free developer environment.
Its seems the FSF has far more to do with GPL apps not being on iOS than Apple.
"Apple and our customers place a high value on simple, refined, creative, well thought through interfaces."
I'm looking at you, iTunes.
Of course apps are also rejected because they don't meet the arbitrary standards of puritanism that Apple applies, or allow the user to purchase content that doesn't meet those standards. Such as digital comics containing male nudity.
http://alternatives.rzero.com/
Contrary to what the UX shitbags thing.
Apple's UI design is shit and the interface is crippled because they demand that you to do things their way.
bigest difference between M$ and Apple?
I can actually buy software that makes Windows usable.
Then why is Space Team in the app store?
My controls always end up with green goo, and are swinging around. Very difficult to use.
[The disproof of Turing completeness using Russian roulette is] a joke right?
Sort of. I've been trying to describe the rules of a few different games, and it turned out that Russian roulette and Hi Ho! Cherry-O are in the same family. I made a Russian roulette homebrew game for the NES as a quick-and-dirty test for reading the trigger switch on an NES Zapper. It lets the player pull the trigger to roll a virtual d6 and be eliminated on a roll of 1. The development process inspired me to make a pencil drawing of six figures gambling with a toy gun.
Someone else on the NESdev forum ported an NES emulator for Mac called "Macifom" to iOS so that the developer of an NES homebrew game can sell the game on the App Store by including it with Macifom in an app. My thought process might have been as follows: "Would Russian Roulette in Macifom be rejected? If so, why? What would need to be cut out? And what useful theorems can I prove from this in order to make points on Slashdot about iOS not being for everyone?" I guess the question becomes how much like Russian roulette a game would have to be in order to get rejected for violating Guideline 15.5.
Because fuck you, that's why.
See, this is why I entitled the post "amateur hour". $99 is not an unreasonable spend to evaluate a business idea
The disenfranchisement of hobbyists, the assumption that everything must be a "business idea", is part of the problem. Would you still be calling it cheap if it were $5000 plus a lease on a dedicated office, as it has been for several other platforms?
The device has power constraints, resolution constraints, memory constraints, storage constraints, but somehow business constraints are unmanageable?
I imagine that Slashdot users tend to be attracted to technical puzzles. Fewer of us are attracted to business puzzles, especially because of their frequent connection to the birth lottery (that is, inherited wealth) and the spoils of past anticompetitive behavior.
you must realize that they have fairly good reasons to forbid porn, excessive violence (which *allows* games like GTA), and WiFi hacking tools
The term "hacking" ascribes unwarranted malicious intent to the developers of MozStumbler. How should the developers of applications like MozStumbler "really try[] hard to work around the restrictions" in your opinion?