1.
Avoid App Rejection
- Few tips for your app development

2.
NAGA HARISH M
Software engineer @ Anubavam
E: nagaharish.movva@gmail.com
W: www.shareourideas.com
facebook.com/shareourideas
twitter.com/nagaharishmovva

3.
Approve v/s Rejection..
• Comparing with other App stores, Apple store approval process is
very tough

4.
Normal App review process in Apple
store
Prepare For Upload
Waiting For Upload
Upload Received
• Appears as the first status for your app.
This status means that you should enter
or edit metadata, screenshots, pricing,
and so on, to prepare your app for
upload to the App Store.
• Appears when you’ve completed entering
your metadata and indicated that you are
ready to submit your binary, however,
you have not finished uploading your
binary through Application Loader.
• After you’ve completed uploading
app package from application
loader or Xcode. This status
message you will see (Just for few
seconds..)
Waiting For Review
In Review
Ready For Sale
• For this stage Apple side work..
Your app will be in queue for
review. If you want you can remove
from the Q. And start from first.
• This means you app is reviewing by
apple review team. If everything
good your app will be ready for
sale..
• Wow..!

5.
App review process in Apple store Rejected
Prepare For Upload
Waiting For Upload
• Appears as the first status for your app.
This status means that you should enter
or edit metadata, screenshots, pricing,
and so on, to prepare your app for upload
to the App Store.
• Appears when you’ve completed entering
your metadata and indicated that you are
ready to submit your binary, however, you
have not finished uploading your binary
through Application Loader.
Waiting For Review
In Review
• For this stage Apple side work..
Your app will be in queue for
review. If you want you can remove
from the Q. And start from first.
• This means you app is reviewing by
apple review team. If everything
good your app will be ready for
sale..
Upload Received
• After you’ve completed uploading
app package from application
loader or Xcode. This status
message you will see (Just for few
seconds..)
Rejected
• Appears when the binary has not
passed review. You receive a
communication from App Review in
the Resolution Center regarding the
reason for the rejection.

6.
Avoid creating Duplicate Apps
• Creating same System app, may get rejected.
• Avoid copying core functionality of pre-installed apps
• Don’t use Private APIs (undocumented methods)
• Be careful when your using 3rd party modules

7.
Follow Human Interface Guidelines
• We must follow HIG in App UI & UX
• Avoid making the platform look bad
• Button images must be consistent

8.
Improper app meta data information
• May sure you writing proper description, screenshots, icons and so
on.
• Please don’t use any other app names in Keywords or description
• Don’t refer your app availability in other market place (for example in
Apple store app description “We have same app for Android also, you
can download here http://...”)

9.
Don’t Publish a beta or unfinished App
(important for apple store)
• Don’t upload Demo apps and those without “minimum user
functionality”
• Uploading unfinished app would make users unhappy
• Don’t upload an app with version number less than 1.0
• Don’t Add any words (like Beta, Preview, Test)
• So, a simple version of your app at first will be the sensible thing to do
Tip :- Remember that the initial app approval process takes the most time. Once approved, future
updates are far easier to get done. So keep the advanced features for later releases of your app.

10.
Logos and digital content..
• Don’t use Apple icons or logos anywhere in your app
• Don’t use trademarked material
• Don’t use any 3rd party (website) content or images without their
permission.

11.
Be careful with content
• If you’re collecting user information, be sure to note it somewhere in
your app and make it clear
• Be careful with language and user-generated content
• No porn

12.
Avoid crashes
• Handle Network reachability
• Test the app in false cases before uploading to store.
• For example :- If user don’t grant access contact. You must handle that
• Take care of Long load time and need feedback on user action

13.
Windows phone Tips

14.
Avoid uploading Incorrect app
screenshots
• App screenshots should not include any emulator, frame rate
counters, or debug information. They should not be altered or be
transparent.

15.
Update App login details if needed (Apple
also)
• Many apps require login credentials to run. If your app requires an
existing account, make sure you create a test account that can be
used by the certification team during testing.

16.
Update App icons and tile images
• sometimes forget to replace default icons and tile images in an app
created from a Visual Studio template, App Studio and Apache
Cordova(PhoneGap).
YOUR APP ICON

17.
Avoid Incorrect use of the Back button
• The Back button behavior is narrowly defined. The Back button
should:
•
•
•
•
Close the app only if the app is on the main page
Go to the previous page only if not on the main page
Close an open dialog
Close the soft keyboard
• Two exceptions to this :- For Game apps and To confirm with the user
before close

18.
Test App in both light and dark phone
themes
• This requirement ensures your app displays properly in both light and
dark themes.
Tip : To do this, press Settings, and then press theme.

19.
Test App in both light and dark phone
themes
• This requirement ensures your app displays properly in both light and
dark themes.
Tip : To do this, press Settings, and then press theme.

20.
App store guidelines links
• Android - http://developer.android.com/guide/
• Apple https://developer.apple.com/appstore/resources/approval/guidelines.html
https://developer.apple.com/library/ios/documentation/userexperience/c
onceptual/mobilehig/
• Blackberry - http://docs.blackberry.com/en/developers/?userType=21
• Win Phone - http://msdn.microsoft.com/enus/library/windowsphone/develop/hh184843%28v=vs.105%29.aspx
https://blogs.windows.com/windows_phone/b/wpdev/archive/2014/01/1
0/top-windows-phone-app-certification-failures-and-how-to-avoidthem.aspx