App review guidelines updated by Apple

Apple recently announced significant updates to its App Review Guidelines, Apple Developer Program License Agreement, and Apple Developer Agreement. These changes are intended to align with updated policies, introduce upcoming features, and provide greater clarity for developers.

Apple updates iOS app review guidelines and developer agreements

One of the notable updates in the App Review Guidelines includes the addition of Notarization under section 2.1(a). This addition emphasizes the importance of ensuring that apps are properly verified and secure. Another significant change is in section 2.1(b), which now requires developers to explain in their review notes why certain configured in-app items may not be found or reviewed in their app. This addition aims to streamline the app review process by providing reviewers with a clearer understanding of app functionalities and configurations.

Section 2.5.8 of the guidelines has also been updated. Previously, apps that simulated multi-app widget experiences faced rejection. However, with the new update, such apps will no longer be automatically rejected, provided they adhere to other guidelines. This change opens up new possibilities for developers to create more interactive and versatile app experiences.

Additionally, Apple has removed guideline 4.6, simplifying the review process and potentially reducing the number of reasons for app rejection. The removal of this guideline is part of Apple's broader effort to make the app review process more transparent and less restrictive.

Updates to the Apple Developer Agreement

The Apple Developer Agreement has undergone several key updates. Notably, sections 1 and 6(B) have been revised to change the terminology from "Apple ID" to "Apple Account." This change is consistent across all updated documents and reflects Apple's intent to standardize terminology and reduce confusion.

Section 16(A) has been updated to clarify export compliance requirements, ensuring that developers understand and adhere to international regulations regarding the distribution of software and services. This update is crucial for developers who distribute their apps globally, as it helps them navigate complex legal landscapes.

In section 18, Apple has updated terminology related to government end users, providing clearer guidance for developers who create apps intended for government use. This change aims to enhance compliance and ensure that apps meet specific regulatory requirements.

Revisions to the Developer Program License Agreement

The Developer Program License Agreement has seen a comprehensive update across several sections. Like the Developer Agreement, the terminology has been standardized, with "Apple ID" being replaced by "Apple Account" in various sections, including Definitions, Section 2.1, 3.3.6(C), 3.3.10(A), 14.2(C), Attachment 9, and Schedules 1-3.

One of the key updates in the Definitions section is the clarification of the Apple Maps Service definition. This clarification ensures that developers have a precise understanding of the service and how it can be used in their apps.

Sections 3.3.6(F) and 3.3.8(F) introduce new terms for using the Apple Music Feed API and the Now Playing API, respectively. These updates provide developers with guidelines on how to integrate these APIs into their apps, allowing for more innovative and interactive music experiences.

Section 3.2(h) has added terms for the use of Apple Software and Services, providing developers with a comprehensive framework for utilizing Apple's resources in their apps. Additionally, Section 6.5 introduces new terms for using TestFlight, Apple's platform for beta testing apps. This update aims to enhance the beta testing process and improve app quality before public release.

Section 7.7 now includes terms regarding the customization of icons, offering developers more flexibility in designing their app icons while adhering to Apple's design principles.

Finally, Section 11.2(f) and 14.8(A) clarify export compliance requirements, aligning with the changes in the Developer Agreement. Section 14.9 updates the terminology for government end users, similar to the Developer Agreement, to ensure consistent language and compliance.

Attachment 5, Section 3.1 introduces terms for using Wallet pass templates, providing developers with the tools and guidelines necessary to create and manage Wallet passes effectively.