This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| CallKit | |
|---|---|
| Name | CallKit |
| Developer | Apple Inc. |
| Released | 2016 |
| Latest release version | iOS 16 / macOS Ventura (varies) |
| Programming language | Swift, Objective-C |
| Operating system | iOS, iPadOS, macOS |
| License | Proprietary |
CallKit
CallKit is a telephony framework introduced by Apple Inc. to provide a native calling interface and call-handling integration for third-party VoIP applications on iOS and related Apple platforms. It lets apps present system-standard incoming and outgoing call screens, manage audio routing with the AVFoundation stack, and interact with the device-wide call services used by Phone and FaceTime. CallKit was announced at the WWDC 2016 keynote and is intended to harmonize user experience across native and third-party calling services.
CallKit offers a set of programmatic interfaces for third-party developers to present incoming and ongoing calls using the same UI metaphors as native services like Phone and FaceTime. It abstracts call lifecycle events into a central controller that coordinates with the system AVAudioSession and CoreTelephony-adjacent behaviors to ensure consistent call audio and interruptions handling across apps such as WhatsApp, Skype, Viber, Google Voice, and Facebook Messenger. Because it integrates with system-level call management, it also ties into platform features like lock screen presentation, Control Center, and Notification Center interruptions.
CallKit centers around several core objects that map to system concepts and events. The CXProvider class supplies the system-visible call UI and reports updates to the framework; the CXCallController mediates transactional command requests such as start, end, hold, and mute. Actions are modeled as subclasses of CXAction, including CXAnswerCallAction, CXEndCallAction, CXStartCallAction, and CXSetHeldCallAction. Call directory functionality is provided by CXCallDirectoryProvider extensions that let apps supply phone number blocking and identification lists used during incoming telephony events. The framework works alongside AVAudioSession and AVRouteDetector for audio routing, and integrates with NSLocalizedString-based resources for localized call labels. Background execution and push notifications are coordinated via PushKit for VoIP pushes and UserNotifications for user-visible alerts.
Developers implement a CXProviderDelegate to receive callbacks for incoming and updated calls and use CXProviderConfiguration to define localized names, iconography, supported handle types (for example, CNContact-style numbers), and maximum call groups. To initiate outgoing calls, apps create a CXStartCallAction and submit it via a CXTransaction to CXCallController. In practice, integrations require implementing VoIP signaling stacks (SIP, WebRTC, or proprietary protocols used by apps like WhatsApp and Skype) alongside PushKit to wake the app for incoming calls. Proper error handling must accommodate transient network conditions, and developers frequently pair CallKit with Call Directory extensions to pre-populate caller ID and block lists using data sources like corporate directories or crowd-sourced databases analogous to services used by Truecaller.
CallKit is designed to present calls indistinguishably from native telephony, thereby interacting with Do Not Disturb modes, CarPlay, Siri, and Bluetooth hands-free profiles standardized by Bluetooth SIG. It cooperates with AVAudioSessionCategoryPlayAndRecord behaviors and responds to AVAudioSessionRouteChangeNotification to manage speaker, wired headset, and Bluetooth routing. On devices with cellular capabilities, CallKit coordinates with CoreTelephony to ensure proper treatment of simultaneous cellular and VoIP calls, and it appears alongside native call logs accessed by Phone if the app opts into call history reporting. Integration with SiriKit can allow voice-initiated calls, while CarPlay support allows hands-free invocation in automotive contexts.
Because CallKit surfaces caller identity and interacts with system call logs, it implicates privacy controls governed by Apple's platform policies and privacy APIs like Contacts permission for labeled handles. Use of Call Directory extensions to block or identify calls requires careful handling of personally identifiable information and adherence to App Store review guidelines. PushKit VoIP pushes and background execution have been tightened by Apple policies to prevent misuse for background data collection, and developers must follow best practices for secure signaling (TLS, DTLS, SRTP) and authentication (OAuth, certificate pinning) similar to enterprise-grade services such as Twilio and standards bodies like the Internet Engineering Task Force.
Introduced at WWDC 2016 with iOS 10, CallKit has evolved with subsequent iOS and macOS releases to refine PushKit behavior, Call Directory limits, and CarPlay interactions. Notable updates followed major releases such as iOS 11, iOS 13, iOS 14, and iOS 15, which adjusted background push handling and tightened privacy constraints in line with changes to App Store policies. macOS and iPadOS support have expanded with platform convergence efforts announced at events like WWDC 2020 and WWDC 2021, with developers targeting various SDKs and requiring compatibility testing across devices including iPhone, iPad, and MacBook Pro models.
CallKit rapidly became a de facto standard for third-party calling apps seeking native UX parity; major adopters include WhatsApp, Skype, Viber, Google Voice, and Facebook Messenger. By enabling system-level call presentation and unified audio routing, CallKit reduced user confusion, improved accessibility compliance, and streamlined interactions with peripherals such as AirPods and automotive infotainment systems from manufacturers like Tesla, Inc. and BMW. It also influenced backend and signaling design choices by encouraging reliable push delivery and secure media encryption patterns used by enterprise providers such as Zoom Video Communications and Microsoft Corporation's communications services. Overall, CallKit reshaped expectations for mobile calling UX and interoperability on Apple platforms.
Category:Apple APIs