Apple App Store’s latest review rules for 2016!

serial number	Chinese content
1.1	When developing programs for the App Store, developers must comply with the Program License Agreement (PLA), the Human Interface Guidelines (HIG), and any agreements and contracts signed between the developer and Apple. The following rules and examples are intended to help developers get their programs
2.1	Programs that crash will be rejected.
2.2	Programs with errors will be rejected.
2.3	Programs that do not match what the developer advertises will be rejected.
2.4	Programs without application documentation or with hidden features that do not match the description will be rejected.
2.5	Programs that use non-public APIs will be rejected.
2.6	Programs that attempt to read or write data outside of the specified container will be denied.
2.7	Programs that attempt to download code in any manner or form will be rejected.
2.8	Programs that install or run other executable code will be denied.
2.9	Beta, demo, trial, and test versions of programs will be rejected.
2.1	iPhone apps must run unmodified on the iPad at iPhone resolution and at twice the resolution of the iPhone 3GS.
2.11	Apps that duplicate existing apps on the App Store may be rejected, especially if there are a large number of them, such as a flashlight app and a Kama Sutra app.
2.12	Apps that are not obviously useful, unique, or simply bundled with a website may be rejected; programs that do not provide any lasting entertainment value may be rejected.
2.13	Programs that are primarily used for marketing or advertising will be rejected.
2.14	Apps that provide deceptive or false functionality without clear labeling will be rejected.
2.15	Apps larger than 100MB (green was originally 50MB) cannot be downloaded over cellular networks (the App Store will automatically ban them).
2.16	Multitasking applications use background services for only a few purposes: VoIP, audio playback, geolocation, task completion, and local reminders.
2.17	Apps are only allowed to browse web content using the iOS WebKit framework and WebKit JavaScript .
2.18	Programs that encourage alcohol or illegal drug use, or that entice young people to drink or smoke will be rejected.
2.19	Apps that provide false system diagnostics or device data will be rejected.
2.2	Developers who upload large numbers of similar versions of their apps to the App Store will be removed from the iOS Developer Program.
2.21	Simple song or movie apps should be submitted to the iTunes store, and book apps should be submitted to the iBookstore.
2.22	Apps that arbitrarily restrict user usage based on context (such as location or carrier ) will be rejected.
2.23	Apps must comply with the iOS Data Storage Guidelines or they will be rejected.
2.24	Applications stored on Newsstand must comply with Table 1, Table 2, and Table 3 of the Developer Program License Agreement, otherwise the application will be rejected.
2.24		2.25	Similar to the App Store, apps that display other apps for purchase or promotional purposes will be rejected, unless they are specially reviewed and approved (such as health management, aviation, and other accessibility needs, etc.), or are apps that provide significant added value to special groups of users.
2.26	Only when app collection is for special review needs, can the app display and recommend other applications besides itself, such as health management, aviation, and accessibility needs, otherwise the app will be rejected. (New)
3.1	Apps or metadata mentioning any other mobile platforms will be rejected.
3.2	Programs with placeholder text will be rejected
3.3	Apps with descriptions that contain information irrelevant to the app's content and functionality will be rejected.
3.4	To avoid confusing users, the app name in iTunes Connect should be consistent with the app name displayed on the device.
3.5	App icons of different sizes should be consistent, otherwise it will cause confusion.
3.6	Apps whose icons and screenshots do not meet the 4+ age rating will be rejected.
3.7	Programs whose categories and types are inappropriate for the program content will be rejected.
3.7		3.8	Developers are responsible for assigning appropriate ratings to their programs. Inappropriate ratings may be modified by Apple.
3.9	It is the developer's responsibility to specify appropriate keywords for their programs. Inappropriate keywords may be modified/deleted by Apple.
3.1	Developers who engage in the following behaviors will be removed from the iOS Developer Program by Apple: attempting to manipulate or deceive user ratings, forging or paying for ratings, and other disproportionate behavior.
3.11	Apps that recommend users to restart their iOS devices before installing a download will be rejected.
3.12	During the review submission process, your app should include functional URLs, such as a support URL and a privacy policy URL.
3.13	Apps will be rejected if their screenshots and marketing text do not clearly identify content or items that require additional, separate purchases (such as using IAP).
3.14	App previews can only use video screen captured from the app, narration, text, and design overlays, otherwise the app will be rejected.
3.15	Apps that add app previews and display real-person personal information without permission will be rejected.
3.16	App previews may include only music that is licensed for use for this purpose in all selected territories.
3.17	Apps whose app previews contain unlicensed content played through the app (such as iTunes playlists and YouTube streams) will be rejected.
4.1	Programs that do not notify and obtain user consent before collecting, transmitting, or using location data will be rejected.
4.2	Apps that use location-based APIs to automatically control vehicles, aircraft, or other devices will be rejected.
4.3	Apps that use location-based APIs for dispatch, fleet management, or emergency services will be rejected.
4.4	Location data may be used when closely related to the app’s functionality or service, or for authorized advertising.
4.4		5.1	Apps that do not use the Apple Push Notification (APN) API to provide push notifications will be rejected.
5.2	Apps that do not use the Apple Push Notification (APN) API to provide push notifications will be rejected.
5.3	Apps that do not obtain user permission before sending a push message for the first time or require push notifications to run will be rejected.
5.3		5.4	Apps that use push notifications to send sensitive personal or confidential information will be rejected.
5.5	Programs that use push notifications to send unsolicited messages or for phishing or bulk spam purposes will be rejected.
5.6	Apps may not use push notifications to send advertisements, promotions, or direct marketing messages of any type.
5.7	Apps may not charge users for using push notification services.
5.8	Apps that use push notifications that utilize excessive network traffic or bandwidth of the APN service or that place an excessive burden on the device will be rejected.
5.9	Apps that transmit viruses, files, computer code, or programs that damage or disrupt the normal operation of the APN Services will be rejected.
6.1	Programs that display player IDs to end users or any third party will be rejected.
6.2	Any use of the Player ID for any purpose not approved by the Game Center Terms will be rejected.
6.3	Developers who attempt to reverse lookup, track, correlate, mine, harvest or exploit player IDs, aliases, or other information obtained through Game Center will be removed from the iOS Developer Program.
6.4	Game Center information (such as leaderboard scores) is only available in your app through Game Center.
6.5	Programs that use the Game Center service to send unsolicited messages or are used for phishing or bulk spamming will be rejected.
6.6	Programs that use Game Center to consume too much network traffic or bandwidth will be rejected.
6.7	Programs that are capable of transmitting viruses, files, computer codes or programs that could damage or disrupt the normal operation of the Game Center service will be rejected.
7.1	Applications that artificially increase ad views or ad click-through rates will be rejected.
7.2	Apps containing empty iAd ads will be rejected.
7.3	Apps designed primarily to display advertising will be rejected.
8.1	Apps must comply with all terms and conditions described in the Guidelines for Using Apple Trademarks and Copyrights and the Apple Trademark List.
8.2	Any app that misleads or implies that Apple is the source or provider of the app, or that Apple in any way endorses its quality or functionality will be rejected.
8.3	Apps that appear similar or confusingly similar to existing Apple products or advertising themes will be rejected.
8.4	Apps that misspell Apple product names in their app names (e.g., GPS for Iphone, iTunz) will be rejected.
8.5	Use of protected third-party material (trademarks, copyrights, trade secrets, other proprietary content) requires a textual copyright acknowledgment at the time of application.
8.6	If the downloaded music or video uses resources provided by a third party without authorization (such as tube, soundcloud, vimeo, etc.), the application will be rejected.
9.1	Apps that do not use the MediaPlayer Framework to access media content in the music library will be rejected.
9.2	Apps whose user interface mimics any iPod interface will be rejected.
9.3	Audio streaming content over cellular networks must not exceed 5MB per 5 minutes.
9.4	Video streaming content longer than 10 minutes over a cellular network requires HTTP Live Streaming and includes a baseline audio HTTP Live Streaming of 64kbps.
10.1	Apps must comply with all terms and conditions of Apple's iOS Human Interface Guidelines.
10.2	Apps that look and feel similar to native iPhone apps (such as the App Store, iTunes Store, and iBookstore) will be rejected.
10.3	Apps that fail to properly use system-provided items (such as buttons and icons) as described in Apple's iOS Human Interface Guidelines will be rejected.
10.4	Apps that create multiple desktop/home screen environments or simulate a multi-App widget experience will be rejected.
10.5	Apps that modify the functionality of standard switches, such as volume levels and ring/silent switches, will be rejected.
10.6	Apple and our customers highly value simple, elegant, creative, and well-designed interfaces. Although it requires more effort, it is well worth it. Apple has set the bar high. If your user interface is too complex or not of a high standard, it may be rejected.
10.7	Apps whose primary function is just to tell the time will be rejected.
11.1	Apps that use channels other than the App Store to unlock or enable additional features and functionality will be rejected.
11.2	Apps that use systems other than in-app payment (IAP) to purchase content, features, or services will be rejected.
11.3	Apps that use IAP to purchase physical goods and services not intended for use with the app will be rejected.
11.4	Applications that use IAP to purchase credits or other currencies must consume them within the application.
11.5	Applications that use IAP to purchase expired credits or other currencies will be rejected.
11.6	Content purchased using IAP must last for at least 7 days and can be shared between the user's other iOS devices.
11.7	Applications that use IAP to purchase items must be assigned to the correct purchase type.
11.8	Apps that use IAP to purchase iOS built-in features (such as camera, gyroscope) will be rejected.
11.9	Apps that contain content or services that have exceeded a certain time limit will be rejected, except for specially approved content (such as films, TV shows, music, and books).
11.1	Insurance apps must be free, comply with the laws of the region in which they are released, and cannot use IAP.
11.11	In general, the more expensive your application, the more thorough our review will be.
11.12	Apps that provide subscription functions must use IAP, and Apple will share the revenue with developers in a 30/70 ratio as agreed in the Developer Program License Agreement.
11.13	Apps that use links within the app to external purchases or subscriptions will be rejected, such as a "buy" button that jumps to a web page to purchase an e-book.
11.14	Apple allows these apps to read or display approved content purchased or subscribed outside the app (specifically magazines, newspapers, books, audio, music, video, and cloud storage content) as long as there are no buttons or links within the app to external purchases or subscriptions. Apple only gets a portion of the revenue from in-app purchases.
11.15	Apps can only use auto-renewing subscription periodicals (newspapers, magazines), business apps (enterprise, efficiency, professional creativity, and cloud storage), and media apps (video, audio, sound), otherwise the app will be rejected.
11.16	Apps may use approved accessory functionality when used in conjunction with certain approved physical products (such as toys) as long as the additional functionality is entirely dependent on the hardware product (such as an app for controlling a telescope) or the app can be used without the physical product, such as as a reward for success or using IAP.
11.17	Apps may be used to facilitate the circulation of recognized virtual currencies if the app’s functionality complies with state and federal law. (New)
12.1	Apps that scrape any information from Apple websites (such as apple.com, iTunes Store, App Store, iTunes Connect, and Apple Developer Programs) or use Apple website content and services for ranking will be rejected.
12.2	Applications can use approved Apple RSS feeds, such as the iTunes Store RSS feed.
12.3	Applications that simply scrape web pages, aggregate content, or collect links may be rejected.
13.1	Apps that encourage users to use their Apple devices in a way that could cause harm will be rejected.
13.2	Apps that quickly drain the device's battery or generate excessive heat will be rejected.
13.3	Apps that can cause personal harm to users will be rejected (new)
14.1	Apps that contain defamatory, personally offensive, petty or mean-spirited content or that attack specific individuals or organizations will be rejected.
14.2	Professional political satirists and humorists are exempt from this provision.
14.3	EULA: Apps with user-generated content must include content filtering, user-generated marking and blocking, and blacklisting functions.
15.1	Applications that contain realistic images of people or animals being killed, maimed, shot, stabbed, tortured, or otherwise injured will be rejected.
15.2	Apps that contain content such as depictions of violence or child abuse will be rejected.
15.3	The "enemies" that appear in the game cannot refer to a specific race, culture, a real government, company or any other real entity.
15.4	Apps that realistically depict weapons in a way that encourages the illegal use or misuse of those weapons will be rejected.
15.5	Games containing Russian roulette gambling content will be rejected.
16.1	Applications containing excessively offensive or vulgar content will be rejected.
16.2	Apps designed to irritate users or be offensive will be rejected.
17.1	Apps cannot transmit user data without the user's prior permission or without informing the user how and where the information will be used.
17.2	Apps that require users to provide private information such as email addresses and dates of birth to use their features will be rejected.
17.3	Apps may request the user’s date of birth (or use other age-gating mechanisms) solely for the purpose of complying with applicable child privacy laws, but must include some useful functionality or entertainment value regardless of the user’s age.
17.4	Applications that collect, transmit, and share personal information of underage users (such as name, address, email, location, photos, videos, drawings, chats, and other personal data, or persistent identifiers related to the above) must comply with applicable child privacy regulations and must include privacy terms.
17.5	Apps that include account registration or access a user's existing account must include a privacy policy or they will be rejected.
18.1	Apps that contain pornographic material, which is defined by the Merriam-Webster Dictionary as "explicit descriptions or displays of sexual organs or sexual acts intended to arouse sensuality, without regard to aesthetic or emotional feelings," will be rejected.
18.2	Applications that frequently provide users with pornographic content (such as the former Chat Roulette program) will be rejected.
19.1	Apps that contain references or comments about religious, cultural, or ethnic groups that are defamatory, offensive, or intolerant, or that could expose a particular group to harm or violence, will be rejected.
19.2	Programs may include or quote religious texts, provided that the quotations or translations provided by the program are accurate and not misleading. Comments should be educational and eye-opening, not inflammatory.
20.1	Gambling and competitions must be initiated by the app developer or the company to which the app belongs.
20.2	Apps must display the official rules of gambling and contests and state that Apple is not the sponsor and is not involved in the activity in any way.
20.3	Developers must obtain legal permission to operate a sweepstakes app, and the sweepstakes app must have the following features: rewards, opportunities, and prizes.
20.4	Apps that allow users to purchase lottery tickets or lotteries directly within the app will be rejected.
20.5	Apps that offer real money gaming (such as sports betting, poker, casino games, and horse racing) must have the necessary local licenses and permissions in the areas where the app is used, must be restricted to those areas, and must be available for free download from the App Store.
20.6	Apps that use IAP to purchase credits or currency and integrate real money gaming will be rejected.
21.1	Apps that include functionality to donate to certified charities must be free.
21.2	Donations must be collected through the Safari browser or by text messaging.
22.1	Apps must comply with local laws in all published areas. Developers are obliged to understand and comply with all local laws.
22.2	Applications containing false, fraudulent or misleading statements will be rejected.
22.3	Any application that solicits, promotes or encourages criminal or patently reckless behavior will be rejected.
22.4	Programs that support illegal file sharing will be rejected.
22.5	Apps designed to be used as tools for illegal gambling (including card counting) will be rejected.
22.6	Apps that have the ability to make anonymous or prank calls or send similar SMS/MMS features will be rejected.
22.7	Any developer who develops an application that secretly collects user passwords or private user data will be removed from the iOS Developer Program.
22.8	Apps that contain DUI checkpoint information not issued by law enforcement agencies, or encourage/assist drunk driving will be rejected.
22.9	Any application that calculates drug dosages must be submitted to the drug manufacturer or an approved agency (such as a hospital, insurance company, or university).
22.1	Apps that use iTunes music previews without authorization will be rejected.
23.1	Passbook Passes can be used to make or receive payments, transmit commercial information or provide verification (such as movie tickets, airline tickets, coupons, etc.), and applications that use Passbook Passes for other purposes may be rejected and their Passbook certificates revoked.
23.2	Passes must contain valid contact information of the pass issuer, otherwise the app will be rejected and the Passbook certificate will be revoked.
23.3	Passes must be signed by the entity and distributed based on its name, trademark or brand, otherwise the application will be rejected and the Passbook certificate may be revoked.
24.1	Apps that are primarily intended for children must include a privacy policy that complies with children’s privacy laws applicable to the app.
24.2	Apps primarily intended for children are not allowed to include behavioral advertising (such as ads based on a user’s in-app activity), and any contextual advertising displayed within the app must be appropriate for children.
24.3	Apps primarily intended for children must obtain parental permission or use a parental gate to link outside the app or conduct transactions.
24.4	Apps in the children's category must be marked "Under 5, 6-8, or 9-11."
25.1	Apps that contain extensions must follow the App Extension Programming Guide (Chinese version, English version).
25.2	Apps containing extensions must provide certain functionality (secondary screen, additional settings) or they will be rejected.
25.3	If an extension's views contain marketing , advertising, or IAP content, the app containing the extension will be rejected.
25.4	Keyboard extensions must provide a way to switch to the next keyboard.
25.5	Keyboard extensions must have offline access or they will be rejected.
25.6	Keyboard extensions must provide numeric and decimal keyboard types consistent with the descriptions in the App Extension Programming Guide or they will be rejected.
25.7	Apps that provide keyboard extensions must have a basic functional classification and privacy policy, otherwise they will be rejected.
25.8	Apps that provide keyboard extensions are only allowed to collect user activity to enhance the functionality of the keyboard extension on iOS devices, otherwise they will be rejected.
26.1	Applications that use the HomeKit framework must have a primary purpose of providing home automation services.
26.2	Applications that use the HomeKit framework must state their purpose in marketing text and must provide a privacy policy, otherwise they will be rejected.
26.3	Apps are not permitted to use data collected from the HomeKit API for advertising or other usage-based data mining.
26.4	Apps that use data collected from the HomeKit API for purposes other than improving the user experience or hardware/software performance of home automation features will be rejected.
27.1	Applications that use the HealthKit framework must comply with applicable laws in the region in which they are located, as well as clauses 3.3.28 and 3.39 of the iOS Developer Program License Agreement.
27.2	Apps that write false or erroneous data to HealthKit will be rejected.
27.3	Apps that use the HealthKit framework to store user health information in iCloud will be rejected.
27.4	Apps are not allowed to use user data collected through the HealthKit API for advertising or usage-based data mining purposes, except for the purposes of improving health, medical treatment, health management, and medical research.
27.5	27.5 Apps that share user data obtained through the HealthKit API with third parties without the user's permission will be rejected.
27.6	Apps that use the HealthKit framework must state the integration with the Health app in their marketing text and must clearly explain HealthKit functionality in the app user interface.
27.7	Apps that use the HealthKit framework must provide a privacy policy or they will be rejected.
27.8	Apps that provide diagnostics or treatment recommendations or control hardware to diagnose or treat disease will be rejected without written regulatory approval upon request.
27.9	Research involving human health must obtain the consent of the participants or the consent of the minor's parents or guardians, including (1) the nature, purpose, and duration of the research; (2) the procedures, risks, and benefits to the participants; (3) the confidentiality of information and the handling of data (including sharing of information with third parties); (4) contact with participants if they have any questions; and (5) the withdrawal process.
27.1	Applications related to human health research must be approved by an ethical review committee and provide proof.
28.1	Apps may only use TestFlight for beta testing of apps intended for public release and must comply with the full App Review Guidelines.
28.2	Apps using TestFlight must be submitted for review when there are significant changes in the content or functionality included in a release.
28.3	Apps using TestFlight may not be distributed to testers for compensation of any kind.
29.1	Apps using Apple Pay must provide users with all material purchase information before selling any goods or services, otherwise they will be rejected.
29.2	Apps that use Apple Pay must properly use the Apple Pay logo and user interface elements in the Apple Pay Human Interface Guidelines or they will be rejected.
29.3	Applications using Apple Pay may not offer goods or services for delivery that violates any law in any jurisdiction, nor may they be used for any illegal purpose.
29.4	Apps that use Apple Pay must provide a privacy policy or they will be rejected.
29.5	Apps using Apple Pay may share data obtained through Apple Pay with third parties only to facilitate or enhance the delivery of goods and services, or as required by law.
x.2	“You” and “Your” means the individual or legal entity (including a company, organization, educational institution, or government agency or department) using the Apple Software or exercising rights under this Agreement. You can authorize your contractors to develop apps on your behalf, but the apps they develop must be submitted under your developer account. If you are publishing apps on behalf of a client, your client can join the iOS Developer Program and add you to their developer team, which will allow you to submit apps under their account.
		x.3	If your app (and third parties that provide advertising) want to call IDFA or include IDFA-related information, you must place ads in your app. If a user resets their IDFA, you cannot associate the reset IDFA with the pre-reset IDFA.

If you want your APP to become more popular, please click on the link: Introduction to ASO optimization service

This article is compiled and published by (APP Top Promotion). Reprinting this article must be approved by Top Promotion , and please attach the link to this article!

<<: 7 Tips to Optimize Your Amazon PPC Ads

>>: Summary of high-quality marketing channels for APP promotion!