The CarPlay automotive platform stands out from phones, tablets, or smartwatches, as it provides users assistance while driving. This means that activities unrelated to driving should not be included in the CarPlay experience. Driving tasks should be simple with minimal interaction and easily accessible, allowing the user to focus on operating the vehicle.

To uphold these principles, Apple regulates the content allowed in cars. The use cases for CarPlay are restricted to only support users while driving. In addition, Apple has defined categories of approved usage scenarios and UI layouts that provide clear guidance for the user experience.

Foundation

• CarPlay applications are not standalone apps but extensions to existing iOS apps, similar to watchOS applications.
• Before starting product design and development, Apple requires an approval process for the persona and use case. This approval process is in addition to the regular app review before a release in app stores.
• To integrate with CarPlay, a special entitlement needs to be granted by Apple for each application, which enables access to CarPlay APIs.
• The features of CarPlay app extensions must align with one of Apple’s predefined app types (see chapter “Introduction”).
• The user interfaces of CarPlay apps follow predefined UI templates (see chapter “Templates”) provided by Apple, ensuring a consistent look and feel.
  Apple’s templates do not allow for any modifications to the user interface, such as adding an SAP Fiori styling (font or colors) or SAP Fiori specific UI controls, components, or patterns.
• The CarPlay simulator can be used to evaluate and test the CarPlay UI and CarPlay applications.

Resources

Apple CarPlay Design Guidelines: https://developer.apple.com/design/human-interface-guidelines/carplay

Apple CarPlay App Programming Guide: https://developer.apple.com/carplay/documentation/CarPlay-App-Programming-Guide.pdf