DirectStream SDK · Android

Your app.
A little more human.

Bring one-to-one video calls to your Android app. DirectStream takes care of the call experience, from the first ring to the last goodbye, so a small team can stay focused on its app.

Android 11+ · Kotlin · Jetpack Compose · Apache 2.0

Two people connected in a one-to-one video call, illustrated as two linked Android screens.
Closer together. Less to build.

A complete call experience.

Incoming, waiting, and in-call Compose screens are ready to use. Audio routing, mute, camera controls, and the call lifecycle live in the SDK.

Made for your app.

Use your Material theme, replace the call content, or build a custom interface with observable state and focused APIs. Your accounts and contacts stay yours to design.

More than a video view.

Explicit call acceptance, incoming alerts, and Android system call integration connect the experience from invitation through hangup.

Device-aware by default

Different devices.
A common language.

VP8, H.264, VP9, and AV1 negotiation is built in. Auto mode checks what both devices can encode and decode, then prioritizes a mutually hardware-supported codec.

  • 01AV1
  • 02H.264
  • 03VP9
  • 04VP8

Auto priority when both devices report hardware support

Compatible first. Hardware-aware when available.

Availability comes from the bundled WebRTC engine on each device. Without a shared hardware option, Auto uses a compatible fallback. Software implementations may be used where exposed; every codec is not available on every device.

From invitation to conversation

A clear path between two people.

The default provider coordinates identity, approval, and signaling in the cloud. Once a call is accepted, WebRTC connects the media between devices, directly when possible.

Default provider call flow: Android apps use DirectStream SDK; Cloudflare Worker and D1 handle approval, Firebase handles identity, signaling and push hints; WebRTC carries direct media or uses an optional TURN relay.
Coordination and media take separate paths. Open full-size diagram
  1. Invite & accept

    Your app selects the recipient. The provider authorizes the request, and the other person chooses whether to accept.

  2. Find common ground

    The SDK exchanges signaling and codec capabilities. Both devices agree on a compatible media format before capture starts.

  3. Connect & talk

    ICE and STUN help find a direct route. A configured TURN relay can carry media when restrictive networks prevent a direct connection.

Easy to bring into your project

One SDK dependency.
The pieces, together.

The Maven Central starter brings the runtime, Compose call UI, and default Firebase provider together. Add DirectStream to an existing Android app without assembling each SDK module yourself.

View on Maven Central
Maven Central

DirectStream

io.github.orthoepiccrown0:directstream

  • Call runtime & WebRTC
  • Ready-made Compose screens
  • Default Firebase provider

Your host app supplies Compose and FCM dependencies. The default provider requires your Firebase and Cloudflare services; TURN is configured separately. The SDK also supports custom providers.

Make room for a conversation.

A calling feature for the app you’re already building.

Discover DirectStream