Ask how long CarPlay certification takes and the first thing to settle is which line you are on. Aftermarket products - head units, external boxes - go through MFi accessory authorisation. Factory-installed head units run under a dedicated collaboration framework between the carmaker and Apple. The submission rules, the reviewing party and the timeline differ on each. The figure the industry quotes, ten to twelve months wired and eighteen months to two years wireless, covers the whole chain: development, firmware and certification together. Certification on its own is commonly put at around two months, with wireless projects running longer depending on the current queue. The two lines cannot be compared against each other, and borrowing an aftermarket schedule to estimate a factory programme produces a number with no meaning.
MFi membership review and a signed confidentiality agreement come first, and only then do you get access to file a product plan. Once submitted, Apple returns a plan number. That number belongs in your internal ledger and has to be reported along the supply chain; it is not something to file and forget. It does not appear on the product itself, but it travels with this hardware version.
On factory programmes, the authentication scheme is settled separately between Apple and the carmaker inside the collaboration framework. There is no authentication component cost of the kind the accessory line carries, so the chip rules from the accessory side should not be applied to carmaker customers.
Run your own testing in-house before submitting. The protocol layer is exercised with Apple's test tools and the hardware side is checked against real devices. Logs, version numbers and sample configurations all have to be traceable, since the same records carry you through later reviews and spot checks, and the laboratory stage goes more smoothly because of them.
The protocol layer is iAP2 on both lines. Where they fork is the authentication path: aftermarket products use the MFi-licensed authentication component, while factory programmes have it set within the collaboration framework.
Samples usually run to two sets or more, with wireless projects keeping extra units on hand, plus the matching test rigs. Apple's terms name two submission points: one when the first prototype is built, and one when the prototype reaches production-ready state, the latter no later than thirty days before production or sale begins. Firmware stays locked, and a board change means retesting.
Interoperability across phone models has to be run, with coverage prepared to the requirements in force at the time, and English documentation and packaging assets go in with the submission.
Protocol conformance and link establishment are the baseline, and the wired and wireless connection paths are exercised separately. From there it is audio and video path quality, basic voice assistant wake-up, and interoperability across different phone models - any of these can stall a project.
EMC, RF and cybersecurity are not on this list. Those belong to national market access, CE RED, FCC and SRRC, and the two sets of accounts should not be mixed.
Approval brings a product plan and authorisation qualification, and the product enters Apple's compatibility list. Channels and carmakers check that list when they select, so whether the number is right and whether the product is on it can be verified in one step. There is no paper certificate and no number printed on the product, but the product plan layer does exist.
Membership is maintained annually, and the plan and the membership are two separate lines. If the annual fee lapses, the plan does not disappear the same day, but the authorised product can no longer be produced or sold, and new plans and changes cannot be filed at all. Permissions follow the payment status, and how they are restored is a matter for Apple's current terms.
Factory programmes slow down on adaptation. CarPlay Ultra arrived on Aston Martin models in North America in May 2025, and in the same month Apple announced that Hyundai, Kia and Genesis would follow. Mercedes-Benz, Audi, Volvo, Polestar and Renault were later reported to have dropped the deep-integration programme. What they dropped is Ultra; standard CarPlay remains supported.
On the aftermarket side the variables are remediation and documents. A protocol or audio-video path problem is a software change of around a week; touching the main controller or the RF path means tested items largely start over. Settling the antenna and main controller selection before submission is easier than reworking afterwards.
A sample version that does not match the submitted documentation is a common reason for a rejection at review, and a rejection means going through the queue again. When schedules are tight, the leverage is in running laboratory and in-house testing in parallel; submitting before the previous step has finished puts rework straight onto the critical path. Packaging and promotional material must not carry marks that have not been approved, and the copy has to match the approved scope. In practice the test data rarely causes the trouble; what comes back for rework is mostly this class of material.
Apple adjusts its test scope and submission requirements, so where your own template and the current documents disagree, the current documents win. On these programmes BlueAsia lines up the current position first, and only then talks about dates.
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
Related News
