WatchKit, HealthKit, ApplePay, HomeKit, App Store Review Guide

[[145146]]

The WatchKit, HealthKit, ApplePay and HomeKit sections in the previous App Store review guidelines have been sorted and extracted.

10. User Interface

10.1 Applications must comply with all terms and conditions of Apple's iOS Human Interface Guidelines.

10.2 Apps that look and feel similar to native apps on iOS or Watch OS devices (such as the App Store, iTunes Store, and iBooks Store) 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 alternative 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 and ring/silent will be rejected.

10.6 Apple and our customers highly value simple, elegant, creative, and well-designed interfaces. It takes more effort, but it is worth it. Apple sets a high bar. If your user interface is too complex or not of a high standard, it may be rejected.

10.7 Watch Apps whose main function is to tell time will be rejected.

26. HomeKit

26.1 Applications using the HomeKit framework must have a primary purpose of providing home automation services.

26.2 Applications that use the HomeKit framework must explain their usage in their marketing text and must provide a privacy policy, otherwise they will be rejected.

26.3 Applications are not allowed 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. HealthKit

27.1 Applications that use the HealthKit framework or conduct human biology research must comply with applicable laws in their region and terms 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 Applications that use the HealthKit framework and store user health information in iCloud will be rejected.

27.4 Applications are not allowed to disclose user data obtained through the HealthKit API or health-related human biology research to third parties, and cannot be used for advertising or usage-based data mining purposes other than for the purpose of improving health or conducting medical research.

27.5 Apps that share user data obtained through the HealthKit API with third parties without user 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.

(Editor's note: This is inconsistent with the HealthKit section of the iOS Human Interface Guidelines, where Apple says: Don't use the term "HealthKit" in your UI. HealthKit is a developer term that refers to the technical framework you use to access health data stored in the Health app. If you need to state how your app uses health data, use the term "Health app." For example, you might specify "the app saves information to the Health app" or "uses health data in the Health app.")

27.7 Apps that use the HealthKit framework or conduct human biology research must provide a privacy policy or they will be rejected.

27.8 Apps that provide diagnostic or treatment advice or control hardware to diagnose or treat disease will be rejected without written regulatory approval upon request.

27.9 Apps that conduct human biological research must obtain the consent of the participants. If the participant is a minor, then the consent of their parents or guardians is required. The consent content includes: (a) the nature, purpose and duration; (b) the participation procedures, risks and benefits; (c) information confidentiality and data processing (including any data sharing with third parties); (d) a point of contact for participant questions; (e) withdrawal process.

27.10 Apps for health-related human biological research must be approved by an independent ethical review committee and proof of review must be provided upon request.

29. Apple Pay

29.1 Applications using Apple Pay must provide users with all material purchase information before selling any goods or services, otherwise they will be rejected. Applications using Apple Pay for recurring payments must provide a minimum renewal period, that payments will continue until canceled, the amount of each period, who is paying the fees, and how to cancel.

29.2 Applications that use Apple Pay must correctly use the Apple Pay logos and user interface elements in the Apple Pay Identity Guidelines, otherwise they will be rejected.

29.3 The goods or services provided by applications using Apple Pay as a purchase mechanism must not violate the laws of any place of delivery and cannot be used for any illegal purpose.

29.4 Applications that use Apple Pay must provide a privacy policy or they will be rejected.

29.5 Applications 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.