Calling UI Framework

The EnableX Calling UI Framework minimises the coding effort required to present a native, telecom-grade calling screen in your mobile app. Rather than building incoming and outgoing call UIs from scratch, you drop in the framework, pass caller details, and handle three callback methods — the platform takes care of everything in between.

The framework sits between your push notification handler and the EnableX Video SDK. When a VoIP push arrives on the device, you hand the caller information to the framework; it renders a system-native calling screen. When the user accepts, you start the EnableX video session. When they decline or the call times out, you clean up — the framework has already dismissed its UI.

Pair with the UI Kit. The Calling UI Framework handles the incoming-call screen. The Video UI Kit handles the in-call video room UI. Together, they give you a full app-to-app calling experience without writing custom UI code.

What It Does

The Calling UI Framework takes care of the following for you:

Incoming call screen — Presents a native-looking calling UI when a VoIP push arrives, showing the caller name and avatar.
Accept / Decline actions — Captures the user's response and fires the appropriate callback to your code.
Auto-timeout — If the user does not respond within 45 seconds, the screen auto-dismisses and your timeout callback fires.
Call hold (iOS) — Exposes a hold callback when the user places the call on hold via the system calling screen.
End call — Provides a programmatic method to close the calling UI from your code (e.g. when the remote side ends the call).

Choose Your Platform

The Calling UI Framework is available for Android and iOS native development:

Android Calling UI SDK

Native Android calling interface built on the platform notification API. Uses EnxCallKitView with three callbacks — answer, reject, timeout.

v1.0 · June 2022

iOS Calling UI SDK

iOS native calling interface built on the Apple system calling infrastructure. Uses EnxCallKit with five callbacks — answer, reject, timeout, hold, end.

v1.0.3 · February 2024

How a Call Works End-to-End

The Calling UI Framework slots into the following flow. Steps 1–2 are your responsibility; steps 3–6 are handled by the framework:

Caller initiates — The remote caller triggers an action on your signalling server.
Push notification delivered — Your server sends a VoIP push to the callee's device via APNs (iOS) or FCM (Android).
App receives push — Your push handler wakes up and calls the Calling UI Framework with the caller details.
Calling UI renders — The framework presents the native incoming-call screen on the device.
User responds — The framework fires callAnswer(), callReject(), or callTimeOut() to your code.
Session connects — On answer, your code starts the EnableX video session using the Video SDK or UI Kit.

EnableX does not provide a push notification service. You must integrate your own (Apple PushKit / Firebase Cloud Messaging) to deliver incoming-call signals to the device. The Calling UI Framework cannot operate without a notification trigger.

Also See

Video UI Kit — Pre-built in-call UI for Android, iOS, Flutter, and React Native. Pair with the Calling UI Framework for end-to-end calling.
Video SDK — The underlying SDK for building fully custom video room UIs.