For CarPlay certification, the entry path for aftermarket head units and factory‑fitted front‑load systems is not the same route. Many people mix the two systems together – causing selection errors from the start. First, distinguish the paths.

1. CarPlay Certification – Two Access Channels, Do Not Mix

·Aftermarket products (aftermarket head units, wireless CarPlay adapters) – follow the standard MFi Accessory Programme – MFi security chip is mandatory – testing via Facets.

·Factory‑fitted front‑load head units – follow the Apple Automotive Partner Programme – not the MFi Accessory Programme. Access rules, chip solutions, commercial terms, and test systems are all different. Automotive OEM clients – do not be led into the MFi Accessory Programme.

  2. MFi Membership ≠ CarPlay Access

Corporate qualification review: 4–6 weeks. Business licence, development capability evidence, and quality system documentation must be complete – Apple assesses whether the company can operate in ongoing compliance. After approval, the MFi Licence Agreement is signed – account and system access granted.

However: MFi membership does not automatically grant CarPlay certification access. After the account is active, you must separately apply for CarPlay‑specific authorisation – an independent approval step. Many manufacturers register for MFi and prepare samples – only to be blocked at the special authorisation stage.

The MFi Licence Agreement includes a strict NDA – all specification documents are prohibited from external distribution.

  3. iAP2 Protocol – Not AirPlay

This is the most important section. Wired CarPlay's underlying protocol is iAP2 (iPod Accessory Protocol 2) – it does not rely on AirPlay. There is no such thing as a "CarPlay‑specific AirPlay SDK."

Wireless CarPlay architecture:

·iAP2 handles Bluetooth pairing, Wi‑Fi negotiation, and control signalling.

·AirPlay is used only for the audio/video transport layer.

Do not loosely define CarPlay as an "AirPlay protocol family." The MFi Portal provides iAP2 (AIS) specifications and the CarPlay Addendum – there is no publicly available CarPlay‑specific AirPlay SDK. R&D teams – do not search for the wrong documents.

  4. Code Integration and Self‑Testing

Integrate the iAP2 protocol stack into the head unit – covering USB communication, touch, Siri, and audio/video interaction. After integration, self‑test using Apple's Facets test suite. Facets is the official self‑test and formal test framework for CarPlay MFi. The Self Certification Tool is for ordinary audio/charging MFi accessories – not applicable to CarPlay.

Self‑testing: 2–8 weeks – depending on team familiarity with iAP2 and head‑unit architecture adaptation complexity. Wireless CarPlay protocol debugging and multi‑device compatibility integration often push the timeline beyond the upper bound.

  5. ATC Testing – Facets Automation

CarPlay certification testing is performed at Apple‑authorised ATC labs – Apple does not accept testing directly. Formal testing is unified based on the Facets automated test suite – functional, performance, and compatibility tests all run on Facets.

Wired and wireless CarPlay test case scopes differ significantly. Wireless adds Wi‑Fi/Bluetooth stability and roaming reconnection tests – timeline is considerably longer.

Audio latency and video frame rate have quantitative performance thresholds – below standard = direct fail. USB iAP2 handshake, touch, Siri, and audio/video interaction are core test items.

ATC slots must be booked in advance – global labs with CarPlay Facets capability are limited – peak‑season wait times can extend significantly.

  6. Compatibility Testing and PPID

Apple provides a compatibility test matrix covering multiple iOS versions and device model combinations. When new iOS versions are released, the matrix is updated – but Apple does not force existing products to proactively retest against new iOS versions. Only when applying for model extensions, or when hardware/protocol‑stack major changes occur – must the latest test matrix be applied.

Each independent hardware model has a separate PPID – certificates are issued per PPID. Whole products reusing a certified CarPlay module can use the derivation path – test scope significantly reduced. This derivation rule is not explicitly covered elsewhere – but it is the most time‑saving route.

  7. MFi Chip Rules – Boundaries

Aftermarket MFi accessories must use Apple MFi‑certified chips – chips run iAP2 for authentication with iOS devices. Non‑MFi chips cannot complete iAP2 handshake – CarPlay cannot be activated. Chip purchase volumes must be reported to Apple – capacity changes must be synchronised.

Factory‑fitted front‑load projects – hardware authentication schemes are separately agreed between Apple and the OEM – they do not use standard MFi co‑processor chips. Do not apply aftermarket chip rules to automotive OEM clients.

  8. Review and Change Management

After the ATC report is issued, submit it to Apple's MFi system for review – review cycle: 2–4 weeks. Issues with the report are sent back to the ATC for supplementary testing or correction. After review approval, Apple issues the product certification record – you receive an MFi certification number and enter mass production.

Software changes: focus on the iAP2 protocol stack. Apple's PPID change rules distinguish Minor and Major changes. Minor UI/parameter adjustments – submit change documentation for assessment – retesting may be exempt – not all software changes require regression testing. Major hardware changes (main chip, audio chip replacement) require assessment for potential partial retesting.

In mass production, nameplate and logo design must comply with Apple specifications.

For CarPlay certification steps, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.