Is the MFi programme free?

Application to the MFi (Made for iPhone, iPad, iPod, Mac, Vision, Watch) programme on developer.apple.com is free, but acceptance is at Apple's discretion and not guaranteed. Once admitted, members are subject to Apple's MFi fee schedule (annual programme charges, per-product royalties, per-unit authentication coprocessor costs), whose detail is confidential and made available only to enrolled members under NDA. Manufacturers should budget on the basis of the contractual schedule received from Apple, not on third-party estimates circulating online.

Does a Lightning or USB-C cable always require MFi certification?

It depends on the function. A simple USB-C power-only cable does not invoke the Apple Authentication Coprocessor and falls outside MFi, although it must still respect the USB-IF specification and the EU Common Charger requirement. A cable carrying iAP2 traffic, data sync, CarPlay-over-USB-C or any function gated by Apple's authentication chain requires MFi membership and integration of an Apple Authentication Coprocessor. A Lightning accessory always requires MFi, since the Lightning connector itself is protected by the programme.

What does the Apple Authentication Coprocessor do?

The Apple Authentication Coprocessor (sometimes called the MFi chip) is a small secure element that the accessory presents to the iOS or iPadOS host during enumeration. The host verifies the chip's identity against Apple's authentication service, and only then unlocks the protected features (iAP2 messaging, CarPlay, digital audio for Lightning headsets, certain HomeKit BLE flows). Without a valid authentication exchange, the accessory is treated as unauthorised and protected features are disabled. Specific part numbers and pricing are Apple-confidential and available to enrolled members only.

Is MFi enough, or do I still need FCC and CE certification?

MFi only covers Apple's brand and ecosystem licence. A wireless accessory (AirPlay speaker, HomeKit hub, MagSafe charger, wireless CarPlay receiver) still needs RED article 3.2 compliance in the EU, FCC Part 15 in the US, Bluetooth SIG qualification where Bluetooth is used, Wi-Fi Alliance certification where the Wi-Fi mark is displayed, and the relevant local radio certifications in each target country. MFi is added on top of, never in place of, the radio regulatory regime.

How does HomeKit relate to Matter?

HomeKit (HAP, Home Accessory Protocol) is Apple's native accessory protocol, governed by the MFi programme. Matter is a cross-vendor standard published by the Connectivity Standards Alliance, supported by Apple Home, Google Home, Amazon Alexa and Samsung SmartThings. An accessory can ship as a HomeKit-only product (HAP, Wi-Fi or BLE or Thread), as a Matter-only product (CSA certification, no MFi required for the Matter side) or as a dual-stack device that exposes both. Apple's Home app accepts Matter accessories without a HAP-specific MFi route, but Matter accessories that also want to use brand assets like "Works with Apple Home" remain subject to Apple's brand rules.

What does wireless CarPlay require on top of wired CarPlay?

Wireless CarPlay adds a Wi-Fi 5 GHz interface and a Bluetooth pairing channel on top of the wired CarPlay stack. The head unit must be enrolled in the CarPlay MFi programme, integrate an Apple-approved Wi-Fi chain (Wi-Fi 5 GHz, often Wi-Fi 6), and respect the wireless pairing and switchover requirements documented for MFi members. Certification involves Apple-recognised labs on the radio side and the wired CarPlay protocol side, plus interoperability tests with the latest iOS versions. The "next generation CarPlay" announced in 2022 is rolled out by car OEMs separately, with extended display protocol coverage.

Can I use the "Made for iPhone" badge before final approval?

No. The badge artwork, typography, clear-space rules and placement on packaging and product are released to MFi members only after the accessory has passed self-test, Apple lab review and Self-On-Record (SOR) registration. Using the badge or any "Made for ..." wording before that point violates the licence, can trigger a takedown by Apple Legal and removes the product from Apple retail and major marketplaces. Region-specific badges (English-only versus localised) follow Apple's brand guidelines shipped to members.

What are the most frequent reasons an MFi accessory fails?

Five recur: assuming the MFi authentication chip removes any need for FCC, RED or local radio certification; mis-sized AirPlay 2 audio buffers leading to drop-outs on multi-room playback; HomeKit Wi-Fi accessories that lose pairing after an iOS update because of mDNS or HAP version handling; under-estimating the Apple-controlled lead time on authentication coprocessor allocation, especially for high-volume programmes; and badge rejection at SOR for typography, colour or clear-space violations on the printed packaging.

MFi (Made for iPhone), Apple accessory certification

Author Hugues Orgitello Last updated 27 May 2026 ~16 min read

Guide, MFi (Made for iPhone)

The MFi programme (Made for iPhone, iPad, iPod, Mac, Vision, Watch) is Apple's contractual gateway for any third party that wants to design accessories interacting deeply with the Apple ecosystem. It is not a regulatory framework: no public authority enforces it. It is a private licensing programme, governed by a confidential agreement, that lets manufacturers integrate Apple's authentication chain, ship Lightning or USB-C cables and adapters carrying iAP2 traffic, build AirPlay receivers, HomeKit devices, CarPlay head units, MagSafe chargers, Find My network tags, Apple Watch wireless chargers and the emerging Vision Pro accessory category. This page sets out the programme's structure, the four main hardware tracks (Lightning, USB-C, AirPlay, HomeKit), the wireless protocols layered on top (CarPlay, Find My, MagSafe, Watch charging), the relationship with regulatory certifications that MFi never replaces, the badge and marketing rules, and the pitfalls recurring across consumer accessory programmes.

How the MFi programme works

The MFi programme is operated end to end by Apple. Membership is requested on developer.apple.com/programs/mfi/, application is free, but acceptance is at Apple's sole discretion and not all applicants are admitted. Once accepted, the manufacturer enters into a confidential agreement that governs every later action: technical access, hardware allocation, lab routing, badge use, distribution.

Programme tracks

MFi is not a single programme but a family of tracks, each with its own access criteria, technical specification and authentication requirements. The main tracks visible to enrolled members are:

Accessory connectors (Lightning, USB-C with Apple authentication, the legacy 30-pin dock connector for service spares),
AirPlay (audio receivers, video receivers, AirPlay 2 with multi-room and stereo pairing),
HomeKit / Apple Home (HAP, the Home Accessory Protocol, including the Matter-compatible bridge model),
CarPlay (wired and wireless),
Find My network accessory programme (separate enrolment),
MagSafe for iPhone (15 W magnetic charging with NFC alignment),
Apple Watch wireless chargers (proprietary coil and authentication),
Vision Pro accessories (emerging since 2024, rolled out per Apple developer announcements).

Each track sets which technical documents the member can download from the MFi portal, which authentication coprocessor (if any) must be integrated, which test plan applies and which badge artwork the finished product is allowed to display.

Confidentiality

The MFi agreement covers the technical specifications, fee schedule, test plans and badge files under NDA. This page only references the publicly available pages of developer.apple.com, Apple press releases and third-party reporting. Manufacturers should not act on rumoured fees or leaked datasheets: the only authoritative source for an enrolled member is the MFi portal once login has been opened.

Fees and timing

Apple's MFi fee schedule covers annual programme participation, per-product royalties and per-unit authentication coprocessor cost. Specific figures, MFi chip part numbers, acceptance rates, internal lead times and lab queue lengths are confidential and provided to members on enrolment. Manufacturers should plan a margin of several months between programme acceptance and first commercial shipment, especially for products that depend on authentication chip allocation from Apple's silicon supply chain.

Connectors, Lightning and USB-C

Lightning, Apple's proprietary connector

Lightning remains protected by MFi for every accessory using it, regardless of function. Cables, adapters, docks, headsets, microphones, card readers, vehicle integration accessories: all are subject to MFi enrolment and must integrate an Apple-provided MFi authentication IC. The chip is sourced through Apple, not from the open market, and its allocation is controlled by Apple as part of programme membership.

Historically, two main generations of the Lightning authentication coprocessor have circulated under MFi, sometimes labelled MFi 2.0 and MFi 3.0 in the trade press. The two generations are not always interchangeable: a host running a recent iOS may require the more recent generation, while a legacy accessory built around the older generation may still be functional but no longer producible. Apple's technical bulletins to MFi members are the only authoritative reference; manufacturers should not rely on third-party part-number tables.

USB-C, post-2023 iPhone and Mac

Since the iPhone 15 (2023), Apple has moved iPhone to USB-C, aligning with the iPad and Mac lines that had already switched. The transition is in part a response to the EU Common Charger requirement under 2022/2380/EU, the directive amending the Radio Equipment Directive ( 2014/53/EU ) to mandate USB-C on a range of portable electronics by the end of 2024.

USB-C is a public industry standard governed by USB-IF (see USB-IF USB-C certification). Apple's USB-C accessories therefore live in a more nuanced regime than Lightning:

Function	MFi required?	Authentication coprocessor
Power-only USB-C charging	No, USB-IF and USB-PD are sufficient	None for MFi purposes
iAP2 or proprietary Apple data over USB-C	Yes	Apple Authentication Coprocessor 3 (or successor)
CarPlay-over-USB-C	Yes, CarPlay MFi track	Authentication required per CarPlay spec
High-bandwidth video out (Thunderbolt, DisplayPort Alt Mode)	Mixed: USB-IF for the connector, MFi for Apple-specific features	Per Apple bulletin
Find My accessory connected by USB-C	Yes, Find My MFi track	Find My-specific authentication

A common pitfall is to assume that switching from Lightning to USB-C removes any MFi obligation. It does for pure charging, but every Apple-specific function layered over USB-C still goes through MFi.

USB-C lab interactions

USB-C electrical and protocol compliance is tested under USB-IF (USB 2.0, USB 3.2, USB4 depending on the cable), USB-PD for power delivery, and USB-C connector compliance. Apple's MFi tests add Apple-specific protocol checks on top, especially around iAP2 and CarPlay. The two test campaigns are conducted in parallel and never substitute for each other.

AirPlay, audio and video

AirPlay is Apple's wireless audio and video protocol, available in two generations relevant for new accessory designs:

AirPlay 1: legacy audio streaming, still found in installed equipment, no longer the recommended target for new development.
AirPlay 2: multi-room audio, stereo pairing, HomePod integration, low-latency buffers, end-to-end encryption.

AirPlay 2 audio

Designing an AirPlay 2 receiver involves the MFi-licensed AirPlay 2 SDK, integration with the host's Wi-Fi and Bluetooth stack, careful management of clock synchronisation across multi-room groups, and tight control of audio buffer sizing. Mis-sized buffers are a frequent source of audible drop-outs on multi-room playback, especially under network congestion.

The SDK is shipped under NDA to MFi members on the AirPlay track. Reference designs published by Apple-recognised silicon vendors integrate Wi-Fi (Wi-Fi 5 or Wi-Fi 6), Bluetooth (often used for initial setup), the AirPlay 2 stack and the authentication chain.

AirPlay video

AirPlay video extends the audio stack with H.264 / HEVC video streaming, primarily for connected TVs, projectors and external receivers. AirPlay 2 receivers in this category are common in the smart TV market and integrate the protocol either through an MFi-licensed SoC or through a software stack licensed by the TV manufacturer. The MFi route remains mandatory.

Network and security

AirPlay 2 carries encrypted streams over Wi-Fi and relies on mDNS / Bonjour for discovery. A frequent post-iOS-update failure mode is mDNS misbehaviour after an OS upgrade, when an accessory's mDNS responder no longer matches the host's expectations. Apple regularly updates the protocol; AirPlay receivers must follow Apple's technical bulletins through their MFi membership and roll firmware updates accordingly. See Wi-Fi Alliance certification for the underlying Wi-Fi mark requirements.

HomeKit and Apple Home

HAP, the Home Accessory Protocol

HomeKit accessories speak HAP (Home Accessory Protocol), Apple's native smart-home protocol, available in two implementation tiers.

Tier	Transport	Authentication	Typical examples
Software-authenticated HAP	Wi-Fi / IP	Shared secret derived during setup, no dedicated chip	Wi-Fi cameras, IP lighting bridges, plug-in smart outlets
Hardware-authenticated HAP	Bluetooth LE, Thread	MFi authentication coprocessor required	Door locks, BLE sensors, Thread border-routed accessories

Software-authenticated HAP, sometimes called the iOS Authentication scheme, removed the hardware authentication coprocessor requirement for Wi-Fi accessories. Hardware-authenticated HAP remains the rule for BLE and Thread devices, where the MFi chip provides the cryptographic root.

Thread and 802.15.4

A growing share of HomeKit accessories are designed around the 802.15.4 / Thread radio (Nordic nRF52840, Silicon Labs EFR32MG, NXP K32W and so on). Such accessories need:

Thread Group certification of the 802.15.4 stack and the Thread protocol,
MFi HomeKit approval for the HAP layer on top, with the hardware authentication coprocessor.

The two certifications are independent and conducted in parallel. See Matter CSA certification for the broader 802.15.4 ecosystem context.

Matter compatibility

Matter, the cross-vendor smart-home standard published by the Connectivity Standards Alliance, is supported by Apple Home. A pure Matter accessory can interoperate with Apple Home without an MFi HAP-specific licence, since Apple operates Matter natively. Manufacturers therefore face a strategic choice:

HAP-only: tighter integration with Apple Home, but limited to the Apple ecosystem.
Matter-only: cross-vendor (Apple, Google, Amazon, Samsung), with Matter-defined feature sets only.
Dual stack (HAP + Matter): maximum coverage, double the certification effort.

Even in a Matter-only design, the use of Apple brand assets ("Works with Apple Home" and similar marks) remains subject to Apple's brand programme.

HomeKit pitfalls

Two failure modes dominate field reports. The first is mDNS / HAP-version mismatches after iOS updates, where a Wi-Fi HomeKit device drops out of the Apple Home app even though it is otherwise functional. The second is the under-estimation of background advertising and pairing requirements on BLE / Thread devices, leading to slow discovery or pairing failures on first-add. Both are addressed by following Apple's HAP technical bulletins through the MFi portal and updating firmware accordingly.

CarPlay

CarPlay is Apple's in-vehicle infotainment integration, available in two main forms.

Wired CarPlay

Wired CarPlay uses the USB connector (Lightning historically, USB-C since the iPhone 15) and runs an iAP2 control channel together with R-NDIS or Apple's CarPlay-specific data transport. The head unit is the MFi accessory and integrates the authentication chain. Wired CarPlay is the entry-level mandatory baseline for any CarPlay-licensed head unit.

Wireless CarPlay

Wireless CarPlay layers a Wi-Fi 5 GHz channel and a Bluetooth pairing channel on top. The user pairs the phone over Bluetooth at first use, then the session moves to the Wi-Fi 5 GHz channel for the high-bandwidth display traffic. The MFi-CarPlay licence covers both modes, but wireless CarPlay introduces additional lab work:

Wi-Fi 5 GHz coexistence: the in-vehicle radio environment is constrained, and Apple's wireless CarPlay specification sets requirements on Wi-Fi channel handling, switchover and concurrency.
Bluetooth pairing: handled by an MFi-qualified Bluetooth stack, with attention to LE Secure Connections.
Switchover from Bluetooth to Wi-Fi: timing constraints to keep the user experience seamless.

Next-generation CarPlay

In 2022 Apple announced "next-generation CarPlay", with deeper integration into vehicle instrument clusters, climate controls and multi-display layouts. Deployment is being rolled out by car OEMs in partnership with Apple from 2024 onward. The certification path for next-generation CarPlay is governed by Apple's CarPlay MFi track, with specific design guidelines and additional display protocol coverage. Member documentation is the only reliable reference.

Radio certification on top

A wireless CarPlay head unit is a Wi-Fi + Bluetooth radio in a vehicle environment, and remains subject to:

RED article 3.2 in the EU ( EN 300 328 and EN 301 893 for Wi-Fi), EN 301 489 for radio EMC, EN 62311 for SAR exposure,
FCC Part 15 in the US,
Automotive EMC requirements depending on the vehicle programme (ISO 11452, CISPR 25),
Local radio certifications in each target country, see for example India BIS, TEC and WPC, GCC, and the LATAM regional guide.

MFi-CarPlay never substitutes for these. A common pitfall is to plan the wireless CarPlay programme without the parallel radio campaign and discover the gap weeks before SOP.

Find My, MagSafe and Apple Watch chargers

Find My network accessory programme

The Find My network accessory programme lets third-party tags and trackers participate in Apple's crowdsourced Find My network, alongside AirTag. It is a separate MFi track with its own enrolment, its own technical specification and its own approval flow. Hardware-side, accessories use BLE for short-range discovery and may add UWB (in newer iPhones with the U1 / U2 chip) for fine-ranging. Cryptographic keys for the Find My exchange are managed by Apple in a privacy-preserving design that prevents trackers from being used to identify individuals.

A Find My accessory remains subject to BLE certification ( Bluetooth SIG qualification ) and to the radio certifications applicable in each target market (RED, FCC, local).

MagSafe for iPhone

MagSafe for iPhone is Apple's magnetic charging system, introduced with the iPhone 12 (2020). It combines a magnetic alignment array, a Qi-derived inductive coil and an NFC tag used by the iPhone to recognise MagSafe-certified accessories. The 15 W charging mode is reserved to MFi-certified MagSafe chargers; non-MFi Qi chargers fall back to standard Qi at lower power. The NFC-based authentication is part of the MFi MagSafe track.

The 2023 announcement of Qi2, the Wireless Power Consortium standard that embeds Apple's Magnetic Power Profile, changes the landscape: Qi2 chargers can use the magnetic alignment system under WPC certification. The MFi MagSafe track remains the route for branded "MagSafe" accessories and for the 15 W mode where Apple gates that level.

Apple Watch wireless chargers

Apple Watch wireless chargers use a proprietary Apple coil format (not standard Qi geometry) together with an authentication exchange. The MFi Watch charger track is separate from the MagSafe track and from generic Qi: a charger licensed to display "Made for Apple Watch" must integrate the Apple-specified coil and authentication chain. Combination chargers (iPhone + Apple Watch in a single dock) stack the two tracks.

Vision Pro

The Vision Pro line, launched in 2024, opens a new accessory category covered by the MFi programme. Apple's developer documentation rolls out the technical specifications for compatible accessories progressively. As of 2026, the public information is limited; manufacturers interested in this segment should follow Apple developer announcements and enrol on the relevant MFi track.

Testing, badges and lab interactions

Self-test and SOR

Every MFi accessory goes through a structured test campaign before commercial release:

Self-test by the manufacturer on Apple-provided tools. The MFi portal ships software utilities (iAP traffic dissector for Wireshark, MFi test kit utilities, AirPlay test client, HomeKit verification harness depending on the track). The manufacturer documents the results.
Apple-approved lab testing for the parts that require independent measurement: radio (where applicable), thermal, interoperability with current iOS / iPadOS / macOS / watchOS / visionOS versions. The Apple-approved lab list is provided to members.
Self-On-Record (SOR) submission. The manufacturer files the dossier in the MFi portal, declares the product on the relevant track, attaches the test reports and the proposed packaging artwork.
Apple review and approval, after which the accessory is registered and the badge artwork released for production.

The whole sequence runs in parallel with regulatory certifications: a CE-marked, FCC-certified, Bluetooth-qualified product can still be blocked from commercial release if SOR is incomplete.

Marketing rules and the "Made for" badge

The "Made for iPhone" badge (and its variants "Made for iPad", "Made for Apple Watch", "Made for Mac", "Made for Vision", "Made for iPhone and iPad" and so on) is released to MFi members only after SOR approval. Apple ships brand guidelines under NDA that specify:

typography: exact font, size and weight rules,
clear space: minimum margins around the badge,
colour: approved variants on light and dark backgrounds,
placement on packaging, product, marketing material and websites,
region-specific badges: localised wording for the EU and other markets versus the English-only badge in others,
co-branding with other ecosystem badges (Bluetooth, Wi-Fi, USB-C, Qi).

Misuse of the badge is one of the most common rejection reasons at SOR re-review or at packaging spot-check. Engaging the brand team early in the packaging design, rather than after print, avoids re-tooling printed packaging at the last moment.

MFi never replaces regulatory certification

Aspect	MFi	Regulatory certification
Nature	Private Apple licensing programme	Public regulation (EU, US, national)
Body	Apple, sole discretion	EU Commission, FCC, national regulators
Subject	Brand, ecosystem integration, authentication	Radio, EMC, safety, energy, EMF exposure
Sanction	Licence revocation, badge takedown	Market withdrawal, fines, customs block
Documents	MFi portal records, SOR, badge release	DoC, FCC ID, test reports, certificates
Scope	"Made for iPhone" branded accessories only	Any product placed on the market

A connected accessory typically stacks CE + RED + FCC + Bluetooth SIG + Wi-Fi Alliance + MFi, with country-specific additions (BIS, IMDA, NBTC, ANATEL and so on per target market). MFi is added on top of all the others and is the last to clear, never the first. See EU + US dual certification for the parallel regulatory plan.

Step-by-step plan for an MFi project

The typical sequence for a manufacturer approaching MFi for the first time.

Define the product scope and identify the applicable MFi tracks (Lightning or USB-C accessory, AirPlay, HomeKit, CarPlay, Find My, MagSafe, Watch charger, Vision).
Apply to the MFi programme on developer.apple.com/programs/mfi/. Application is free, acceptance is at Apple's discretion. Plan several weeks for the review.
Sign the MFi agreement and open access to the technical portal, specifications, SDKs and brand assets corresponding to the targeted tracks.
Order Apple authentication coprocessors through the MFi supply channel where the track requires them (Lightning, hardware-authenticated HAP, MagSafe, Find My, CarPlay over the relevant transport, Apple Watch chargers).
Design the accessory to the MFi specification: schematic integration of the authentication chip, layout review, antenna design where wireless is involved, firmware integration of the relevant stack (HAP, AirPlay 2, iAP2, CarPlay, Find My, MagSafe NFC, AirPlay 2 SDK).
Run self-test with the Apple-provided tools and document the results internally.
Schedule Apple-approved lab work where required by the track (radio, thermal, interoperability with current OS versions).
Run regulatory certifications in parallel: CE-RED, FCC, Bluetooth SIG, Wi-Fi Alliance, Qi where applicable, plus country-specific certifications for export markets.
Prepare packaging artwork with the badge brand guidelines and submit for review.
File the SOR dossier on the MFi portal, await Apple approval, then release production.
Maintain compliance: monitor Apple developer bulletins, follow iOS / iPadOS / watchOS / macOS / visionOS releases, update firmware when Apple notifies a change, re-test on new OS versions, and re-engage MFi review for major hardware or firmware modifications.

For cross-cutting orders of magnitude per phase, see certification timeline and certification costs.

Frequent pitfalls

Pitfall	Consequence
"The MFi chip is enough", ignoring FCC, RED, Bluetooth SIG and Wi-Fi Alliance	Product MFi-approved but blocked from market placement on regulatory grounds
Mis-sized AirPlay 2 audio buffers	Drop-outs and audio glitches on multi-room playback, especially under congestion
HomeKit Wi-Fi accessory drops after iOS update because of mDNS / HAP version handling	Field returns, support load, requires a firmware rollout
Under-estimating Apple's authentication chip allocation lead time	Production slippage of weeks to months when ramping a high-volume programme
CarPlay wireless certification lab queue under-estimated	SOP delayed, vehicle OEM line rebalancing
"Made for iPhone" badge typography, colour or clear-space violation on printed packaging	SOR rejection, packaging re-print and tool re-cut
Treating USB-C as MFi-free for an iAP2 or CarPlay-over-USB-C function	Accessory enumeration fails on iOS, requires hardware re-spin
Conflating MagSafe MFi with generic Qi or with Qi2	Wrong charger geometry, mis-set 15 W mode, brand confusion
Releasing a Find My accessory without the Find My MFi track enrolment	Accessory cannot enrol in the Apple Find My network, no value to the user
Vision Pro accessory designed against rumours rather than Apple developer bulletins	Re-spin once the public specification is consolidated
Skipping interoperability testing on the latest iOS / iPadOS / visionOS minor version	Field failures after Apple's autumn OS release, fixed only by a firmware update
Ignoring the brand programme for Matter-only accessories that still want "Works with Apple Home" wording	Apple brand takedown of marketing material

Engineering support for MFi certification

Going further

Bluetooth SIG qualification: the parallel programme that all Bluetooth MFi accessories must clear
Wi-Fi Alliance certification: for AirPlay 2, wireless CarPlay and Wi-Fi HomeKit accessories
Matter certification: the cross-vendor alternative to HomeKit-only HAP
USB-IF and USB-C certification: for the connector and protocol layer under USB-C accessories
RED article 3.2: the EU radio regulation MFi never replaces
FCC scope: the US radio regulation MFi never replaces
Glossary: definitions of MFi, HAP, AirPlay 2, iAP2, CarPlay, MagSafe, Find My, SOR

Sources & references

Apple MFi Program overview , Apple developer.apple.com/programs/mfi/
Apple Home (HomeKit) for developers , Apple developer.apple.com/homekit/
Apple CarPlay for developers , Apple developer.apple.com/carplay/
Apple AirPlay for developers , Apple developer.apple.com/airplay/
Apple Find My network accessory programme , Apple developer.apple.com/find-my/
Matter, Connectivity Standards Alliance , Connectivity Standards Alliance csa-iot.org/all-solutions/matter/