Skip to content

Roadmap ​

Callx grows in small, verified steps. Each milestone ships when it passes automated, emulator and device checks; dates depend on device coverage and funding. Vote or comment on items in GitHub Discussions.

Available today ​

The shared Swift and Kotlin core, Flutter and React Native packages with the Expo plugin, push ingress with CallKit and Core-Telecom, durable recovery, the LiveKit adapter with audio and video, native video views, picture-in-picture (experimental on iOS), the optional call overlay and mini-call, native Android lock-screen controls, phone features (audio routes, DTMF, caller-name updates, call back from Recents, Siri and missed-call notifications) and the testkit. Release-by-release detail is in the changelog; what has been proven is on the status page.

Presentation roadmap ​

ItemStatusScope
Custom Dart/TypeScript call screensAvailableExisting snapshots, commands and native video views
Supplied overlay, call screen and mini-callAvailableBranding, custom controls and presentation slots
Unified native/custom/supplied UI configurationPlannedConfigure incoming presentation separately from the accepted-call screen; prevent duplicate foreground incoming UI
Native call UI configuration from Dart/TypeScriptPlannedDefine supported appearance options and platform limits; Android presenter hooks currently require Kotlin
iOS system PiPExperimental; physical acceptance pendingAVKit native surfaces, shared framework APIs; integration requirements

Custom presentation retains native call ownership and the required system integration.

Guided integration and native SDKs ​

ItemStatusScope
Interactive setup guideImplemented in docsSelect framework, OS, presentation, media, backend and migration path; generate copyable Dart/TypeScript starter files, native fragments and integration checkpoints
Detailed migration journeysImplemented in docsCallKeep and flutter_callkit_incoming: ownership, backend routing, staged rollout and rollback
Standalone Android SDKIn development; not publishedLocal Maven packaging and independent consumer compile check; Kotlin API and runnable native example pending; optional Compose UI to be scoped
Standalone iOS SDKIn development; not publishedRoot Swift package and independent iOS consumer compile check; Swift API and runnable native example pending; optional SwiftUI UI to be scoped
Callx hosted backend serviceFuture direction; unavailableA separate optional service; authentication, signaling, push delivery, operations and pricing need their own design

Standalone SDKs must reuse the same native core and contract as Flutter and React Native. Native host APIs already exist inside the framework packages; they are not yet a separately published Kotlin/Swift product. Hosted service work has no release date. Callx remains usable with your own backend and media without a Callx account or hosted-service dependency.

Remaining core work ​

ItemWhy
Physical-device acceptance across iPhone, Pixel, Samsung and XiaomiThe gate every feature above still has to pass (status)
Emulator matrix and community device results published for every releaseTrust comes from evidence, not claims
iOS conformance on a real iPhone, automated where possibleParity with Android's conformance run
Android Direct BootRing before the first unlock after a reboot
Android system call logSelf-managed calls in the Phone app's history; needs an API Core-Telecom does not expose yet
Per-call ringtoneCommon request; Android channels and CallKit fix the sound per app today

Providers, in order ​

Callx grows provider by provider. Each one ships for Flutter and React Native together and passes conformance before release. Physical-device acceptance remains a release gate; development and emulator checks can proceed while those trials are pending.

#ProviderStatusScopeDepends on
1LiveKitAvailableAudio and video; physical/iOS video verification pendingVideo in the core: done, contract 0.2
2TwilioPlanned next; not implementedTwilio Video (media) and Twilio Programmable Voice (signaling: Twilio owns invitations and push)Video in the core; the signaling adapter interface
3Zoom Video SDKPlanned; not implementedAudio and videoVideo in the core
4AgoraPlanned; not implementedAudio and videoVideo in the core

Only LiveKit currently has an installable Callx adapter. Planned providers have no release date; the order above is a development priority, not a shipping commitment.

Queued, by demand: Daily, Vonage, 100ms, Stream Video, Amazon Chime SDK, Telnyx, Plivo, Sinch and SIP stacks. Tell us what you need in GitHub Discussions.

Later ​

ItemDepends on
Multiple calls: call waiting, hold-and-swapA future contract extension; contract 0.3 still allows one live call
@bear-block/callx-server: payload builders and push helpers for Node.js backendsStable invitation schema

Not planned ​

  • A mandatory hosted-service dependency inside the library. Any future hosted backend is a separate, optional product.
  • Telemetry of any kind in the library.
  • Web calling (browsers have no system call UI to integrate with).

Have a use case that is not here? Start a discussion.

Released under the MIT License. No telemetry, in the library or on this site.