How to make sure your app is not rejected
With a lot of application entries, we have experienced different types
of Apple App Store endorsement process challenges. It’s a procedure much
more entangled than presenting an application to Google Play. One of
the greatest dissatisfaction for designers and customers is the point at
which a submitted application is rejected in the endorsement process
before going live in the App Store. You ought to begin by checking out
the App Store Review Guidelines and take after these or examine the
reasons that Apple records as the most widely recognized application
dismissal reasons before presenting your application. However, here are
some of the rules as reviewed by various reviewers (some more strict
than others) and every now and again change after some time.
Below are the 10 most exemplary reasons why Apps are rejected by the
App Store Review Team that we, and our associates in other application
advancement organizations, regularly encounter:
1. Missing privacy policy
If your app requires the users to register an account or login to an
existing account, you have to provide a privacy policy either in your
app or as a link inside the App Store listing. Including both is highly
recommended for good measure.
2. Missing demo accounts
If your app requires user to login always, make sure you provide the
App Store Review team with a working demo account. If you app’s core
functionality consists of users following or sending something to each
other, it will be a good idea to provide two demo accounts that are
connected. We also found out that providing a video when two devices are
required to demonstrate functionality helps app store approval.
3. Lack of app meta-data
Even though the lack of app meta-data is an easy fix, it should never be
why you are rejected. In most cases, when an app is rejected due to
meta-data it can be if you have not provided substantial information and
that the information is incorrect. Always make sure to check you have
provided the correct information and all links are working, otherwise if
rejected you will need to submit again.
4. Major bugs in the app
It may seem obvious, but if you app contains any major bugs that prevent
the App Store Review team from reviewing your app, it will immediately
be rejected. Make sure you thoroughly test your app before submitting
for approval.
5. Only ask for personal information for app-related purposes
If you app requires users to provide personal information such as email
address, date of birth and gender without it being used for a specific
reason, the app will be rejected. For example, if you are making a ToDo
app, asking for the user’s country, zip code or birthday is not directly
linked to the apps core functionality. You can have these fields but
make sure you do not make them mandatory.
6. The Concept or Functionality of the app is against Apple guidelines
Submitting an app with features that are against Apple’s App Store
guidelines will most likely not be approved. For example, submitting an
app where you use IAP to buy physical products is not allowed. If a
feature can be perceived as both against and pro App Store Guidelines,
try to rethink the feature as you are likely to be rejected at some
point, even if it is not the first or second time. We always advise our
clients to stay in a neutral area when it comes to App store guidelines.
7. The app configuration (.plist) file not specifying correct
background functionality (audio control, background location, etc.) If
your app has functionality which can be used while the app is in
background mode, make sure your plist files contain the right
information. For example, if your app enables you to play music in the
background, make sure the plist file (an apps configurations file) only
enables tasks that your app supports. Recently we have seen the App
Store Review Team pay more attention to which background tasks the app
is providing.
8. Dummy data still in the app
When submitting your app to App Store Review, it’s important that it
does not contain any dummy data, broken or dead links or Lorem Ipsum
texts. It can be a good idea to have staging and live environment so you
never end up with submitting an app with dummy data.
9. Moderating user-generated content
If your app displays user-generated content, you must include a feature
that can filter objectionable material, such as a mechanism for users to
flag offensive content, and the ability to block abusive users from the
app. For example, if your app contains a personal feed of images that
are uploaded by other users you follow, you must give the user to option
to block or report that image and user. It might not be easy to find,
but if you look closely you will see that all major social network apps
have this feature. The rule is somewhat new and we believe Apple is
paying close attention to apps that do not have this feature.
10. Make sure your video preview sticks to functionality only
According to Apple, “App previews may only use video screen captures of
the app, voice-overs, and textual and design overlays.” So be careful
when trying to make your video quirky with animations and do not use
iPhone or iPad frame devices.
Also make sure you have an appropriate system that can sort and respond to all of these reports.
We can assure you that if you can cross these 10 things mentioned above,
you will be a step closer to having your app successfully approved and
go live on the App Store for sure.