The opposition between the requirements of the customer and the rules for placing mobile applications on the platform itself is often turned into a headache for programmers. Indeed, the App Store contains many limitations and nuances. Here are listed the features that most often cause discussions between the customer and the performer and are the reason for refusing to publish applications.

Specificity of development of iOS-applications
The App Store guides contain much obvious for the developers and incomprehensible to the customer’s conditions. Here are some common limitations.

Adaptive authentication.
Deviations are subject to iOS programs where personal information (birth date, phone number, e-mail) is requested to register and activate the account. It is preferable to personalize users through manually entered logins or generators.

A unique solution.
The rules prohibit the placement of clones of existing applications. Only with a unique idea, enhanced functionality or narrowly specific features, the mobile product has a place to be and spread on the platform.

Convenient intuitive interface.
With all the wealth of features, you do not need to save on this part of the development. Each potential user must get access to the function without complex schemes. The interface must comply with the requirements of the Human Interface Guidelines, and the use of non-standard buttons, panels, etc. Not welcome.

Full versions of applications.
“Beta”, “tests” and demonstration options are subject to rejection. Free access for evaluation can be provided with a version of Lite with limited functionality.

Rational use of multitasking.
Additional channels can use background services for their intended purpose: audio playback, VoIP. You can specify location and delivery of local notifications. The program must complete the current tasks in a timely manner, without delays or use of flows for the implementation of other goals.

Acquisition of content.
Payment for services must be made through an In-App Purchase system. This service is not used outside the application, even if it belongs to the online store. Payment for online goods, in this case, is carried out by the usual methods of electronic commerce.

Matches in the names.
To avoid duplication of system names, longer names with prefixes (prefixes) are used inside the application.

Compliance with the description.
The application must solve the tasks that are stated by the developer. If there are hidden or undocumented functions that are not suitable for description, then such application will not be moderated.