How LIVDEK actually works
Not a marketing list — the real pipeline, the real security model, and the real limits of what runs on a phone.
One encoder, several independent publishers.
Most phone streaming tools that support more than one destination run a separate encode per platform — that's real CPU/GPU and battery cost multiplied by however many places you're streaming to. LIVDEK encodes the composited scene once in hardware, then hands the same encoded packets to a publisher per destination, each on its own bounded queue.
- Destinations: YouTube, Twitch, Facebook, Kick, or any custom RTMP/RTMPS server
- A slow or failed destination never blocks the renderer, encoder, or the other destinations
- Free: 1 destination at a time · Pro: up to 6 simultaneous destinations
Mic and game audio, mixed independently.
Microphone input and device/game audio (captured via AudioPlaybackCapture) are two separate channels with their own gain, mute state, and live peak meter — not a single blended "volume" slider. You can duck your mic without touching game audio, or mute game audio entirely while keeping commentary live, and it applies the same way whether you're streaming or recording.
- Per-channel gain (0–200%), muting, and live clipping/silence detection
- Settings persist across sessions — set it once, it stays set
- Some apps block playback capture for DRM/anti-cheat reasons; that channel goes silent by design, not a bug
Capture → composite → encode, all on the phone.
The pipeline is MediaProjection → VirtualDisplay → SurfaceTexture → an EGL/GLES3 compositor → MediaCodec (H.264 + AAC) → a packet distributor → one RTMP/RTMPS publisher per destination. Every stage runs on the phone's own GPU and hardware encoder — the same shape of pipeline desktop streaming software uses, just without the desktop.
- Scene compositing (gameplay + camera overlay + screen capture) happens in real time on the GPU
- One encoder, shared across every active destination, per output profile
- Nothing is transcoded or re-encoded per platform
What never leaves your phone
Stream keys never leave the device
Stream keys and RTMP URLs are encrypted on-device with Android Keystore (AES-256-GCM, a non-exportable key) and redacted from logs, crash reports, and diagnostics — including when they're embedded in the URL itself.
Live video is never stored or relayed by us
LIVDEK's backend is a control plane only — accounts, entitlements, support chat. It never receives your media. Your stream goes from your device directly to the platforms you configure.
Recordings stay on your device
Record Screen is the one exception to "nothing is stored": it writes to Movies/LIVDEK on your own phone via Android's MediaStore. That file-writing code is isolated to a single package and has no network access.