# Apple CarKey UI: What You Build and What Apple Handles > By Lawrence Arya, Founder & CEO of VP0. Published 2026-05-31, updated 2026-06-02. 4 min read. > Source: https://vp0.com/blogs/apple-carkey-ui-template-figma The secure part of a digital car key is Apple's and the automaker's: your job is the calm, clear companion around it. **TL;DR.** Apple CarKey stores a digital car key in Apple Wallet, provisioned by the automaker, so users can unlock and start a supported car with their iPhone or Apple Watch. You do not build the secure NFC key, Apple and the automaker do. Your companion app designs the pairing, status, sharing, and remote-feature UI around it. Build that from a free VP0 design, and be clear about what is Apple's responsibility versus yours. Apple CarKey lets a supported car be unlocked and started with an iPhone or Apple Watch, with the key living securely in Apple Wallet. The short answer: the secure digital key itself is provisioned by the automaker and handled by Apple Wallet, you do not build the cryptography or NFC security. Your companion app designs the experience around it: pairing, status, key sharing, and remote features. Build that from a free VP0 design, and be honest about the boundary. Digital car keys are a growing space, the market is projected past [$4](https://www.statista.com/) billion, but most of the security is Apple's and the automaker's, not yours. ## Know the boundary The most important thing to understand is what you own. The digital key, its provisioning, secure storage in the Secure Element, and NFC unlock, is Apple Wallet and the automaker's domain. Trying to reinvent any of that is both impossible and unsafe. What your companion app designs is everything around the key: onboarding and pairing the car, showing vehicle status (locked, charge, location if supported), sharing a key with family (and revoking it), and any remote features the car exposes through the automaker's SDK. Apple's [Wallet and PassKit](https://developer.apple.com/documentation/passkit) patterns show how key cards should feel, and Apple's [car keys support](https://support.apple.com/guide/iphone/use-car-keys-iph192bf2f5a/ios) explains the user experience. ## Build the companion, not the key VP0 is a free iOS design library for AI builders. Pick onboarding, status, and sharing designs, copy their links, and have Cursor or Claude Code rebuild them in SwiftUI. Design a clear pairing flow, a calm vehicle-status screen, and a careful key-sharing flow, sharing a car key is high-stakes, so make granting and revoking access explicit and obvious. Surface remote features (if the car supports them) through the automaker's SDK, and gate sensitive actions behind device authentication. Be transparent in copy about what the app does versus what Apple Wallet handles. For the Wallet pass pattern, see [Apple Wallet pass UI template free](/blogs/apple-wallet-pass-ui-template-free/), and for a related connected-device dashboard, see [smart home IoT dashboard mobile UI](/blogs/smart-home-iot-dashboard-mobile-ui/). ## CarKey companion building blocks You design these; Apple handles the key. | Part | Job | Whose job | |---|---|---| | The digital key | Unlock and start | Apple Wallet and automaker | | Pairing | Set up the car | Your companion app | | Vehicle status | Locked, charge, location | Your app, via the SDK | | Key sharing | Grant and revoke access | Your app, explicit and clear | | Remote features | Climate, horn, etc. | Your app, via the SDK | ## Common mistakes The first mistake is thinking you build the secure key, you do not; it is Apple and the automaker's. The second is a confusing or careless key-sharing flow, where granting or revoking access is unclear, a real safety issue. The third is overpromising features the car's SDK does not support. The fourth is not gating sensitive actions behind authentication. The fifth is vague copy that blurs what Apple Wallet handles versus your app. Own your part clearly and let Apple own the security. ## A worked example Say you build a companion app for a CarKey-supported vehicle. Your VP0-built app guides pairing, then shows a calm status screen (locked, charge level, last location). Sharing a key with a family member is an explicit flow with a clear grant and an obvious revoke, gated behind Face ID. Remote climate control surfaces through the automaker's SDK. The actual unlock uses the key in Apple Wallet, which your app does not touch. The copy makes that boundary clear. For the QR-payment cousin, see [WeChat Pay QR code scanner UI](/blogs/wechat-pay-qr-code-scanner-ui/), and for a nomad-living vertical next, see [co-living space booking app UI](/blogs/co-living-space-booking-app-ui/). ## Key takeaways - Apple CarKey stores a car key in Wallet, provisioned by the automaker. - You do not build the secure key; Apple and the automaker handle that. - Your companion app designs pairing, status, sharing, and remote features. - Make key sharing explicit, with clear grant and revoke, behind authentication. - Be transparent about what Apple Wallet handles versus what your app does. ## Frequently asked questions What does a CarKey companion app actually build? Everything around the key: pairing the car, vehicle status, key sharing (grant and revoke), and remote features via the automaker's SDK. The secure digital key itself lives in Apple Wallet. Do I build the digital car key's security? No. The key, its secure storage, and NFC unlock are handled by Apple Wallet and the automaker. You design the companion experience, not the cryptography. How should key sharing work? As an explicit, clear flow: granting access and revoking it must be obvious and gated behind device authentication, because sharing access to a car is high-stakes. Where does the unlock actually happen? Through the key stored in Apple Wallet and the car's NFC system, handled by Apple and the automaker. Your app surfaces status and features but does not perform the secure unlock itself. ## Frequently asked questions ### What does a CarKey companion app actually build? Everything around the key: pairing the car, vehicle status, key sharing (grant and revoke), and remote features via the automaker's SDK. The secure digital key itself lives in Apple Wallet. ### Do I build the digital car key's security? No. The key, its secure storage, and NFC unlock are handled by Apple Wallet and the automaker. You design the companion experience, not the cryptography. ### How should key sharing work? As an explicit, clear flow: granting access and revoking it must be obvious and gated behind device authentication, because sharing access to a car is high-stakes. ### Where does the unlock actually happen? Through the key stored in Apple Wallet and the car's NFC system, handled by Apple and the automaker. Your app surfaces status and features but does not perform the secure unlock itself. --- *Published on the [VP0 Journal](https://vp0.com/blogs). Free to read, index and cite with attribution.*