How To Get Rejected From the App Store
snydeq writes "Fatal Exception's Neil McAllister catalogs 12 sure-fire ways to get your app rejected from Apple's notoriously fickle App Store. From executing interpreted code, to using Apple's APIs without permission, to designing your UI, each transgression has been abstracted from real-life rejections — for the most part because Apple seems to be making up the rules as it goes along. 'It'd be nice for Apple to make conditions for rejection clear,' McAllister writes. 'Apple has been tinkering with the language of its iPhone SDK license agreement lately, but that hasn't done much to clarify the rules — unless you're Adobe. For everyone else, the App Store's requirements seem as vague and capricious as ever.'"
with the current open ended terms, there is no way this book could be a complete set... "just 'cause" will always still be an option for apple.
No one is making anyone buy an iPhone. No one is making anyone develop for an iPhone.
This isn't the 90's and Apple isn't MS. They don't have to open up their hardware or software to anyone else, and no court is going to make them. You want to compete so bad? Go make your own phone or pad.
SJW: Someone who has run out of real oppression, and has to fake it.
Make something innovative enough, Apple will co-opt it (cut-paste, tethering) and forget what they said previously about it and then delete your app from the store.
It probably would be better to have a plan to offer it to jailbroken iPhones to at least reduce losses.
Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
Didn't Micro$oft have API's that they used and didn't want anyone else to use? Didn't they get lambasted for that?
Twin or more? ITA
Apache/Spring/La
Could we PLEASE try to go even a single day without some apple-based story? My god, there's more to the world of science and technology than a single company!
Canada attempting to pass a bill to put filesharing along the same lines as in the USA?
Info on the oil leak?
Hewlett-Packard cutting 9000 jobs?
To hell with all of that, someone somewhere posted something about Apple!
Planet Zebeth - Metroid with a twist
They used to have a game called Calvinball where the rules were made up as they played the game and ever changing. Dealing with Apple (or even thier bedmate ATT) is a lot like playing CB....sigh
sig loading.......
If your app does anything that might make it bigger than The Phone, then you screwed up. Apple wants their customers to always have in mind that they're using an iPhone; not your apps on an iPhone. Same reason Valentino Rossi won't get to race on a Ducati.
I swear to God...I swear to God! That is NOT how you treat your human!
The reality distortion field that Jobs invented works well. Too bad Microsoft never got one.
Great Intellect...
*gasp* You mean a an article by McAllister might twists facts around in an article for nothing more than to drive hits to his blog? Say it ain't so!!!!
Look and feel is why we buy Apple. We expect to do certain things in certain ways. There are some things that will always be wanted. It is like cup holders. Just because some consumers buy cars based on cup holders does not mean that we should all have to drive car with 23 cup holders.
It is a flawed analogy. No-one is asking for that. What people want is the ability to add extra cupholders to their car in case they need them (and apparently many people do!). But Apple only lets you install anything into your machine in its own service centers, and they only offer a limited range of options.
Also, "iTunes sync over WiFi" = "cupholder", seriously?
This has been discussed ad infintum. I think battery life should take precedence over developers wanting to take the easy way out. I pay for code to be good.
The Flash aspect has been discussed ad infinitum. However, there isn't any good reason why a user cannot run an application which is an interpreter (and advertised as such), rather than uses an interpreter internally (and does not advertise it).
I mean, seriously, what does a HyperCard implementation - which the user would have to explicitly feed code to run - have to do with battery life?
I have no idea on this one. I think if people had not felt they had a god given right to infinite bandwidth ATT would still be selling unlimited plans.
Bandwidth usage is something that should be strictly between the user and his mobile provider. Then, of course, if Internet radio is a serious network strain, then iPhone "3G" is a misnomer.
When Apple posted GPL content and then removed it, the general rational EFF cried foul, even though Apple really did nothing wrong. People assume that if it is in the Apple store, then Apple can be blamed.
A GPL violation is a definite copyright infringement, though; there's no shady ground here. But a BitTorrent client? They're not illegal. And the app in question isn't even that - it's simply an UI to control a BitTorrent client running on a computer remotely.
I certainly totally hate it when some useful app vanishes or new rules pop up out of nothing, but on the other hand I can somehow understand that Apple has to make the rules as it goes along. I mean, if they'd put up clear rules and would stick to these, developers would instantly start to find loopholes and to work around them, naturally. And for Apple the iPhone/iPad platform is what they bet their future on. And this platform is still at a very early stage. They do not want to be the dog with which the tail waggles.
Apple (and the Mac and OS X) has more than once suffered from others having too much control over things. Like Adobe with taking ages to port their apps to Intel Macs because they did not use XCode in the first place. Imagine Apple allowing Flash and any kind of programming language and compilers and middleware and then, 4 or 6 years on, they try to go to a totally different hardware platform (which *will* happen sooner or later, be assured). Suddenly they'd have a large amount of apps they couldn't offer any migration tools for then and be at the whim of some third party (or worse, hundreds of them). Look at Microsoft -- Windows and all its apps are married to Intel and the flood of ARM platforms for tablets is totally out of bounds for MS here. There is absolutely no way to port Windows and all applications to another platform. Trapped.
For Google, Android itself and its apps is still a minor thing. Google does not sell systems. As long as they get your data and your eyes, they can allow Android apps to go whereever they go. They don't actually care.
Really, I'm somewhat happy that there's more than one way. All of this is a large experiment and attacking the problems from more than one angle is good. Freedom is not when everyone does the same.
You got what you deserved for working with oligarchs. What did you expect?
A little life advice, you know that girl you call every 2-3 days for 2 weeks, but never actually meet? Well, she's just not that into you. Apple'a App store is a pretty similar situation. You should either (a) get a job writing an app for people who have the clout, like say a newspaper, or (b) just changing fucking platforms.
Maemo and MeeGo are kinda a moving target right now, but one might try expanding GnuSTEP to aid porting iPhone apps. Or, if your really crazy, try writing tools to help port iPhone apps to Qt. I'm sure many iPhone developers would love having their apps run natively on Symbian phones.
Btw, GnuSTEP was originally developed by SLAC to help port HippoDraw away from the dying NeXT platform, but they eventually gave up on Objective C and NeXTSTEP's, instead choosing Qt.
The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
Well,
I have no doubt that there are issues with the way Apple handles this. However I consider this article as bad journalism. About much stuff I have a clue, and the article makes no attempt to give any explanations on how or what is going on and what is so bad about it.
However articles like this one: http://infoworld.com/d/developer-world/how-get-rejected-the-app-store-854?page=0,0/ only lead to confusion and are not really helpful (as half the claims there are arguable wrong)
I work down the list as presented in said article.
1. we all agree that (crashing) software like that has nothing to do on my mobile device, I assume? ... that sounds like bullshit to me.
2. I agree with Apple. Why should they allow to have several Mail, SMS and what ever programs on the device that ruin the platform look and feel?
3. Well, neither the article, not the linked article make clear what this is about. So I would call this bad journalism. Again: what exactly is the Wi-Fi synch thing wee are talking about here? You want to tell me if I want to synch my iPhone with my Mac it wont work over Wi-Fi? Are you sure? And Apps that make this possible get rejected? Are you really sure? If that is the case, we have a point here, but if that is truly the case what is so hard in making this explicit for noobs like me?
4. Execute interpreted code. Your comments are wrong. It has absolutely nothing to do with "interpreted" or "not interpreted". Apple considers the iPhone an End-User-Device. You can not program on it, and you should not. That is their stand of view. It has nothing to do with interpreted. Imagine a C64 Emulator that has access to the Mac OS X API and is able to "format" the "HD" of the iPhone. Nightmare!
5. Use too much bandwidth. The whole explanation makes no sense at all. First of all internet radio streams only us 2 or 3 times the bandwidth a phone call does. Secondly, a provider like AT&T perfectly knows which connections over his network do what. So instead of dropping a phone call because of network saturation the provider easily can drop a true bandwidth hogger. Blocking an App because it might use bandwidth makes no sense
6. No idea about this. All I can find about this is pretty weird. I had expected that the author of this article had worked on that so we as his readers get an ida what is really going on. However: The App Store is no democracy, which might be why Apple doesn't feel inclined to support free speech. First off all: Free speech or not free speech is something different. Supposed there is a ruler and some citizen says: "that ruler sucks." In a society honouring free speech that citizen can say this unharmed. In a society not honouring free speech the ruler might call for his head. Why do you want to imply that an App that does not get published, for what reason ever, is somehow violating "free speech principles"? Claims like that are a slap into the face of people all over the world that fight for free speech in their countries. You dare to compare a not published App in a Store that belongs to Apple, where Apple has all rights to do what they ever want (not rights: privileges even) with "free speech issues"? Hello, get a real live man!
7. Use Apple's APIs (without permission). Oh my god. The biggest bullshit in this article. First of all the (without permission) part. It implies that some Programmers have the permission to use those APIs. If you have an App on your iPhone, you expect it to continue to work after a system upgrade, or not? If that App uses a "secret API" and that API got changed during the upgrade, the App will likely crash, or not? Whom do you blame? The stupid moron who used secret/unofficial/undocumented APIs or the System Upgrade? Stuff like this bullshit only one who has no clue about programming can write.
8. Use someone else's stuff. No comment about this but I doubt the
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
Apple is trying to create a walled garden and are desperate to own the content because they know that pretty soon everyone is going to catch up with OS X in terms of usability and then they will just be another also choice. I give it another 5 maybe 10 years at the outside until most OSes are pretty much the same in terms of look and feel and usability, baring anything stupid in terms of software patents.
So Apple knows that since its days are numbered they need to own or control the content. Which is why the do everything they do. They don't care about the OS any more, they care about owning and controlling the content now.
As for the walled garden, we all know how well that worked out for AOL and other similar companies. The walled garden approach almost never works because there ends up always being something outside of the walled garden that people want. Walled gardens will never work in the long term.
I think Apple is just scared to death of the future repeating itself and Apple being a nothing on it last legs in 5+ years, like it was 5-10 years ago. So they are willing to do anything to try and make that not happen, including doing stupid things that make it happen faster.
If it is all about the OS then Linux is going to eat Apple's lunch given enough time, and every time. There is very little that OS X has currently that isn't available in Linux. Plus Linux being open source and free means more and more companies who don't want to pay an OS tax are using it. Linux is showing up everywhere on every kind of device you can think of, and neither Apple or Microsoft can hire enough programmers to combat that level adoption or features being added by so many companies and developers. Is Linux perfect? No, but it gets better all the time, and what is clear is that Linux is good enough for a lot of things currently. Perhaps Linux isn't prefect for everything, at least not yet, but that will change in time.
Steve Jobs knows he won't be at the head of Apple forever and probably won't be around after another 10 years, so he has to do whatever he thinks he can to make Apple be able to survive when he is gone so they don't have a repeat of what he sees as the past failures while he was gone. In the end the more he or anyone else tries to put a tight grip on things to control them, the more they lose control of the very thing they want to control.
Microsoft learned long ago, you want your platform to succeed then you need to win the minds of developers. It seems Apple never really learned this, or at least not well. The more Apple pisses off developers the faster they will become an also or a has-been.
Comment removed based on user account deletion
Developers are still writing apps for the platform, aren't they?
Here's the deal. You get access to the iPod and iPhone user base ... maybe ... for as long as it pleases Apple for you to have that. You take the calculated risk that Apple will accept your app, and continue accepting that app long enough for you to recoup your investment. There are no guarantees that it will please Apple to continuing doing so, any more than there are guarantees that users will buy your app.
I don't understand why people agonize over this like its some kind of betrayal, or like Apple owes them something. As far as Apple is concerned they own not only the platform, but the customers for that platform and every aspect of the user experience. What part of that hasn't been made abundantly clear yet? Oh, there are certain well known things you can do to avoid getting your app banned, but Apple could decide tomorrow to change the rules. They could even ban your app because they decide it's not consistent with the image they want to project.
As long as there are plenty of app developers who willing to develop on those terms (basically nothing is guaranteed), and Apple has never pretended otherwise, why should Apple do anything for you? It'd be different if they'd promised you anything like control over your own destiny, or openness, or transparency, or even a fair shake. But they haven't. They promised you a crapshoot, and that's what you get. It's their rules, and those rules are "what we say goes, and we don't owe you any explanation." The only people who might in some conceivable scenario have any cause for complaint are the stockholders, but those circumstances haven't arisen yet.
So, iPhone developers, if you don't like Apple's terms, eat it, or move on. Apple never forced you to develop for the platform, and they aren't forcing you to stay.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.