Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

xArtx

macrumors 6502a
Original poster
Mar 30, 2012
764
1
Hi Guys,
I am looking for some Apple document concerning App Store compliance
if any such thing exists. I have Googled, but maybe "compliance" is the
wrong word for "not getting rejected".
What I mean is the most exhaustive list of reasons why an app or game
might be rejected by Apple.

I have read about it a lot over time whether it be right or wrong:

NSLog commands should be cleared from distribution builds because they are
slow to execute

Apps may support only landscape, or only portrait orientations for valid reasons,
but if they do, they should rotate to their supported orientation in both directions.

Obviously no use of undocumented calls.

I'm sure the list goes on...

-------

One question which program authors here might have tested is regarding Apple's flexibility.

What if there's a valid reason to break one of these guidelines?

Say a game like Tilt Maze (a tilt controlled ball in a maze) lacked any touch
interface at all, and recognised button pushes by the user rolling the ball
over on-screen buttons which would keep with the theme of the game?

Or a game is camera controlled, and the author locked orientation to
landscape right to keep the camera at the top of the iPhone?

-------

Can any members here give examples of apps that were approved where
one or more of these issues were overlooked because there was merit in doing so?

I'm working on my first app intended for App Store, and it is very different.
Cheers, Art.
 
I believe you have to have to be a paying member to look at this list, but here's the link to it:

https://developer.apple.com/appstore/resources/approval/guidelines.html

But take note of the end of the list which basically says that the review team reserves the right to throw out that list and reject your app for any other reason they conceive of or to accept it despite it violating something on the list.

I've read over the entire list once before, but I really don't bother anymore... just make a nice app and don't program things in thinking that you can sneak them by Apple.

Edit: Darn! I took a whole 7 minutes longer than Dejo to write a response whose meat was the same freaking link?
 
That's kind of what I wanted to hear.
If they think the program has merit, they might overlook some things
if there's a valid reason.

One thing I need to do is turn off the idle timer.
Both examples above would also require this.

I am a paid developer, and am due my next $99 in March, but up till now
it was just personal programming.. to play with.

Man, you've both linked to it, and I'm afraid to read it :D
 
One thing I need to do is turn off the idle timer.

There's nothing wrong with this so long as you have a reason (IE, because the app is expected to be visual output mainly - with minimal user input, such as a clock app or an app for playing movies.)
 
There's nothing wrong with this so long as you have a reason (IE, because the app is expected to be visual output mainly - with minimal user input, such as a clock app or an app for playing movies.)

Thanks, that sounds about right.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.