The main mistakes when publishing a mobile app to the AppStore

If you have ever created a mobile app, you know that it is much easier to publish it on Google Play than on Apple. Clients of Sopa BlackOut often ask to publish an app developed for them. In this article, our specialists will tell what mistakes developers make when trying to place their application in the AppStore.

Insufficient meta-data

This reason for rejection will most likely be due to the fact that you did not provide really important information about your app, or for some reason the information does not correspond to reality. Correct the data, check that all links are correct.

There is no privacy policy

If your app requires registration, it will be a prerequisite for posting the app, it will be necessary to publish a privacy policy. We recommend doing this both in the app itself and in the app store by publishing a link to it.

Errors in the application

Strange as it may seem, very often the reason for not publishing is a serious error in the code of a mobile application. Before posting an app to the store, be sure to test it as thoroughly as possible.

The app doesn’t comply with Apple’s guides

Read the AppStoreReviewGuidelines carefully before publishing the app. If something doesn’t follow the guidelines in the guidelines, your mobile app probably won’t pass inspection. Features can be interpreted differently, so if necessary, you should make changes to the functionality so you don’t run into problems.

The configuration file does not specify background functionality

The configuration file should clearly reflect the functionality used in the mobile application. If there is a discrepancy in the information, there is a chance that the app will not be published.

Only ask for really necessary data

If it turns out during the publishing process that your app is requesting access to too much data unreasonably, but the mobile app will be denied placement in the store. For example, it would be strange if a calculator needed access to the camera or contacts.

Video previews should only show functions

Previews use only screen captures, voice, text, and design elements. Be sure to use iPhone and iPad frames when designing screenshots of the app.

Test data in the app

Strictly check that there is no fishy text, user test data, or other dummy data left in the app.


Moderation of user-generated content

If your mobile app has the ability to post user-generated content, there should definitely be an option to filter that content. For example, the possibility to hide the content of a certain user or complain about it to moderators.