CallKit Implementation for iOS (Integration with System Calls)

We have encountered situations where a VoIP app receives an incoming call, but the user misses it because the system notification looks like a regular banner. The result: lost calls and unhappy clients. CallKit solves this by turning an app call into a full system call with a large screen, buttons, and history entry. In this article, we will explain how to set up CallKit from scratch, avoid common mistakes, and increase the answer rate.

How CallKit Changes the User Experience for Incoming Calls

Without CallKit, an incoming VoIP call appears as a push notification. With CallKit, it displays full-screen with the contact’s name and photo, and options to answer or decline. According to statistics, this format boosts successful connection rates by 3–4 times compared to a standard push notification.

Architecture: CXProvider and CXCallController

The central class is CXProvider. It is the communication point between the app and the system: through it we report an incoming call, update information, and end the call. The second class is CXCallController, through which the app initiates and manages outgoing calls.

let providerConfiguration = CXProviderConfiguration()
providerConfiguration.supportsVideo = true
providerConfiguration.maximumCallsPerCallGroup = 1
providerConfiguration.supportedHandleTypes = [.phoneNumber, .emailAddress, .generic]
provider = CXProvider(configuration: providerConfiguration)
provider.setDelegate(self, queue: nil)

Incoming Call. It arrives via a VoIP push (PushKit, not APNs). This is important: a regular APNs push does not support CallKit calls since iOS 13 — Apple requires using PKPushType.voIP and in the delegate PKPushRegistryDelegate.pushRegistry(_:didReceiveIncomingPushWith:) immediately call reportNewIncomingCall. Any delay between the push and the reportNewIncomingCall call will cause the system to terminate the app.

func reportIncomingCall(uuid: UUID, handle: String, hasVideo: Bool) {
    let update = CXCallUpdate()
    update.remoteHandle = CXHandle(type: .generic, value: handle)
    update.hasVideo = hasVideo
    provider.reportNewIncomingCall(with: uuid, update: update) { error in
        // if error != nil — the system rejected the call (e.g., DND)
    }
}

Answer/Decline.

The system calls CXProviderDelegate methods: provider(_:perform:) with CXAnswerCallAction or CXEndCallAction. In response to the Answer action, you need to connect the audio — start a WebRTC session or connect your VoIP SDK (Twilio Voice, Agora, Daily).

WebRTC and Audio Session

CallKit manages the system’s audio session. You must not configure AVAudioSession yourself — that is CallKit’s responsibility. When the call is answered, the system activates the audio session and calls provider(_:didActivate:). At that moment, connect the WebRTC audio stream to the AVAudioSession. When the call ends, provider(_:didDeactivate:) is called, and you disconnect.

If you call AVAudioSession.setActive(true) before this moment, the call may drop or audio may not work. This is a common bug in first-time integrations.

Twilio Voice SDK: TwilioVoice.handleNotification → call.accept(with: delegate) → in callDidConnect activate audio through CallKit. The SDK encapsulates part of this logic, but you still need your own CXProvider.

Call History and Siri

After the call ends, call provider.reportCall(with: uuid, endedAt: Date(), reason: .remoteEnded). iOS automatically adds a record to the Phone app’s call history with the name and duration. The user can call back from the Phone app — this will open a call through your app if the CXHandle of type .generic matches the identifier.

Siri Shortcuts for calls: through INStartCallIntent (iOS 13+), the app registers the intent. “Call Ivan using MyApp” — Siri starts a call via CallKit.

Common Problems

Duplicate Calls.

The UUID must be unique for each call and must not change between the push and the answer. If a push arrives twice (retry), check the UUID — do not create a second CXCallUpdate for the same UUID.

Stuck Call in History. If the app crashes without calling reportCall(endedAt:), the call remains as “active” in the history. Solution: at next app launch, check CXCallObserver.calls — if there are unfinished calls, end them.

VoIP Push on iOS 13+.

PKPushRegistry must be initialized in application(_:didFinishLaunchingWithOptions:), not lazily. Apple checks this and may terminate the app.

Comparison: CallKit vs Regular Push

Statistics are based on Apple CallKit documentation and real-world cases.

How Long Does CallKit Integration Take?

Basic implementation of incoming/outgoing calls with one VoIP SDK: 2–3 days. With group calls, video, Siri Shortcuts, and custom UI: 4–5 days. The cost is determined after analyzing your VoIP infrastructure and requirements. Contact us — we will evaluate your project and propose the optimal solution.

What Is Included in the Work

• Setup of CXProvider and CXCallController with configuration tailored to the app’s needs
• Integration of PushKit for VoIP push
• Handlers for answer, decline, end, hold, mute
• Connection to WebRTC/VoIP SDK (Twilio Voice, Agora, Daily, Vonage)
• Audio session management through CallKit lifecycle
• Call history recording
• Crash scenario handling and unfinished call cleanup

We guarantee correct CallKit operation in accordance with Apple documentation. Over 5+ years, we have implemented more than 30 projects with VoIP and CallKit, so we know all the pitfalls.

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.