Apple has updated its App Store review guidelines. According to Apple’s official notice, the changes include: review responses, saturated App categories, push notifications, sign-in via Apple, data collection and storage, and mobile device management.
Table of Content
Apple App Store Review New Guideline
App Store Reviews
User reviews in the App Store are an essential part of the App experience, so you should be respectful when responding to user reviews.
Use the provided API to prompt users to view the app; this feature allows customers to provide an App Store rating and review without leaving the App, and we do not allow custom review prompts.
Note: This addition of 5.6.1 App Store Reviews to the original guideline 5.6 Developer Code of Conduct is a further indication of the importance Apple places on user reviews of developer products. At the same time, recently, due to working from home, online classes and other reasons, many products have one star and poor reviews from users. Here it is also recommended that developers first appeal to Apple to explain the reason for the matter, and secondly, they can also publish interesting short videos and segments with the help of operations and other means to redeem their image in front of users.
In addition, this rule also indicates that henceforth users can directly star-rate and rate the product in the App, and users no longer need to jump to the App Store interface, which is a very good situation for the product.
New section in guideline 4.5.4: Push notifications
Push notifications must not be required by the App and must not be used to send sensitive personal or confidential information. Push notifications may not be used for advertising, promotional or direct marketing purposes unless the customer has explicitly opted in to receive push notifications via the consent language displayed in the app UI, and a method must be provided in the app for users to opt out of receiving such messages. Improper use of these services may result in revocation of your permission.
Note: This time, when Apple set this requirement, it was a direct indication of what was prohibited in push notifications and did not mention whether or not it was allowed. This change to the push notification terms not only explicitly prohibits developers from using push notifications to post sensitive personal or confidential information. At the same time, it also says that developers can add a new push notification to the App, and as long as users choose to agree to receive such messages, it does not count as a violation of the terms and conditions, but only requires the addition of a rejection option to ensure user autonomy.
New Guideline Data Collection and Storage
Data collection and storage
(ix) Applications that provide services in highly regulated areas (e.g., banking and financial services, healthcare, and air travel) or require sensitive user information should be submitted by the legal entity providing the service, not by individual developers.
Note: The collection and storage of user information data has always been a major concern for Apple, and this new clause 5.1.1(ix) is specifically set by Apple for banking, financial, medical, and travel products, etc. The collection and storage of data in these areas will be more directly and closely related to user privacy and life, so if such products need to collect and store user personal information, it should be submitted by the legal entity providing the If such products need to collect and store users’ personal information, it should be submitted by the legal entity providing the service, not by individual developers.
New section of Guideline
Mobile Device Management
MDM Apps that provide mobile device management (MDM) services must request this functionality from Apple. Such apps may only be provided by commercial enterprises (such as business organizations, educational institutions, or government agencies) or, in limited cases, by companies that use MDM to provide parental control services. You must clearly state on the App screen what user data will be collected and how it will be used before a user takes any action to purchase or otherwise use the service.
Note: Among the additions to this change, Apple has added a new possibility for data collection for mobile device management, which allows developers to collect or transmit data about the performance of developers’ MDM apps on devices and profile apps for third-party analysis, but under this requirement, users, their devices, and other apps on the device cannot be collected or transmitted. The requirement is that the user, the user’s device, and other applications on the device cannot be collected or transmitted.
Refinement Updates Offering Sign in with Apple
Require people to sign in in exchange for value. For example, people may need to create an account to personalize their experience in the app, access additional features, or sync data.
Consider using Apple Sign in for every version of your app and website. To create a consistent sign-in experience, you can offer “Sign in with Apple” for your apps and websites across all platforms, including non-Apple platforms and the web.
Delay sign-in whenever possible. People often abandon apps when they’re forced to sign in before they can do anything useful. Give them a chance to familiarize themselves with your app before making a commitment. For example, live streaming apps allow people to browse available content before logging in.
In commerce apps, wait until people make a purchase before asking them to create an account. If you support a guest checkout system, provide a way for people to quickly create an account after the transaction is complete. For example, if you support Apple Pay, have people create an account on the order confirmation page. If people have already provided their name and email address during the Apple Pay transaction, there is no need to ask for this information.
Explain the benefits of signing in. If your app requires a login account, display a short, friendly note on the login screen that explains the reason for the request and its benefits. Also, remember that not everyone uses your app from the start.
Mobile Device Management
Consider allowing people to link an existing account to use the Apple login. When you support this type of linking, people can get the convenience of using Apple Sign In while maintaining access to the information in the account they have set up. You can provide a link to an account before or after a user logs into their existing account. For example.
If people share an email address through Sign in with Apple and that email address matches an address in an existing account, you can suggest that they link Sign in with Apple to that account.
If people sign in with an existing username and password, an account association suggestion can be displayed in their account’s settings view or other logical location.
Note: This time, Apple not only made it clear in App Store Review Guidelines Section 4.8 Sign in with Apple that developers need to add a way to sign in via Apple to the App sign-in screen, but also updated the Human Interface Guidelines page to help developers set up sign-in via Apple in a better, more comprehensive way. The Human Interface Guidelines page has also been updated to help developers set up sign-in via Apple in a better and more comprehensive way for users. This requirement begins on April 30, 2020, and all apps that want to hit the App Store, and those that want to update, will need to follow these guidelines. This is a one-month extension from the previous requirement of April.
New saturated App categories
Note: The App Store will add “Software Development Tools” and “Graphics and Design” categories, and the macOS App Store will add “Books,” “Food and Drink,” and “App Store. “Food and Drink”, “Newspapers and Magazines”, “Navigation” and “Shopping” categories. “Photography” and “Video” were merged into the “Photography & Video” category, and games no longer include the “Kids” subcategory. Games no longer includes the “Kids” subcategory.