Skip to main content
RingKit is a Capacitor plugin that owns the whole incoming-call cycle, not just the call screen: VoIP push → wake from a killed app → native call UI → answer routed back into your app. It works with the push you already send (raw FCM/APNs, OneSignal, or SIP), owns the in-call audio session so calls “just work”, and ships an Android reliability layer for the strict-OEM long tail.

Quickstart

Install, register, and present your first call in a few minutes.

iOS setup

Capabilities, Info.plist, and sending the VoIP push.

Android setup

Deliver the wake push — RingKit’s FCM service or your own handler.

Android reliability

Ringing across the OEM zoo — the watchdog and the helpers you wire.

In-call audio

The one rule that fixes the WKWebView dead-microphone bug.

API reference

Every method and event, with payloads.

​
What you get

  • The killed-app path, owned end to end — the VoIP token, the push→wake, the native screen, and the answer surviving a cold start. Not just a call UI.
  • Reliability across Android OEMs — a hybrid Telecom + full-screen presentation with a silent-failure watchdog, plus battery/autostart helpers to guide users on MIUI/EMUI/ColorOS.
  • Provider-agnostic — raw and onesignal payload presets plus dot-path key overrides, so no backend rewrite is required.
  • In-call audio handled — routing, proximity, hold, and the dead-microphone fix, or an observe mode when your media SDK owns the session.

​
License

RingKit is closed-source commercial software: the repository is private, and a subscription — $99/yr per app — is what grants access to it along with the right to ship the plugin. Full terms on the License page; buy at ringkit.dev.