Integrating Live Streaming into a Mobile App

When trying to add live streaming to a fitness app, our client faced a delay of over 20 seconds on HLS. The trainer performed an exercise, but viewers saw his actions with a lag — destroying interactivity. We proposed an alternative: WebRTC with 500 ms latency and HLS for recording. WebRTC provides 30x lower delay than HLS. In 4 weeks, we deployed a system that handled 10,000 concurrent viewers. Request an audit of your app — we will determine the optimal architecture.

Main Technical Problems

Latency and buffering. HLS chops the stream into 6-second segments, resulting in 15–30 s delay. For interactivity (voting, chat), this is unacceptable. LL-HLS reduces to 2–5 s, but requires server support and iOS 14+. WebRTC solves the problem radically but is harder to scale.

Audio/video synchronization. When encoding on a mobile device, it is important to set GOP size and bitrate. In our project on Android, we used MediaCodec with a fixed GOP=2 and bitrate of 2 Mbps — this gave a stable picture even when speed dropped to 1 Mbps.

Media server scaling. One Wowza server handles up to 1000 connections. For 10,000 viewers, we configured a cluster of 4 nodes with load balancing via AWS ALB. Cloudflare Stream removes this pain but is more expensive.

How We Do It: Stack and Configurations

We start with an audit of requirements: target latency, expected audience, budget. For MVP, choose RTMP → HLS. For production low latency, choose WebRTC + LL-HLS fallback.

iOS streaming. Basic stack: Swift 5.9, HaishinKit (RTMP/SRT/HLS). Example configuration:

let rtmpStream = RTMPStream(connection: RTMPConnection())
rtmpStream.videoSettings = VideoCodecSettings(
    videoSize: CGSize(width: 1280, height: 720),
    bitRate: 2_000_000,
    frameInterval: 2,
    frameRate: 30
)
rtmpStream.audioSettings = AudioCodecSettings(bitRate: 128_000)

Android streaming. Streampack or custom code on CameraX + MediaCodec + RTMP client.

val streamer = CameraStreamer(context, enableAudio = true)
streamer.configure(
    AudioConfig(startBitrate = 128_000, sampleRate = 44100, channelConfig = CHANNEL_IN_STEREO),
    VideoConfig(startBitrate = 2_000_000, resolution = Size(1280, 720), fps = 30)
)

Media server. Use Wowza Streaming Engine or Ant Media Server. For WebRTC — Ant Media or Janus.

How to Reduce Stream Latency to 500 ms?

Switching to WebRTC is the only way to get latency < 1 s. Key steps:

1. Deploy a signaling server (e.g., Node.js + Socket.io).
2. Set up a TURN server (coturn) for NAT traversal.
3. Choose a media server that supports WHIP ingest (Cloudflare Stream, Ant Media 2.x).
4. On the mobile client, use WebRTC.org SDK (Google for Android, native for iOS).

For mass viewing (1000+ viewers), WebRTC overloads the server — use an SFU (Selective Forwarding Unit). Ant Media and Janus support SFU. Source: WebRTC

Why WebRTC Is Not Always Suitable for Mass Broadcasts?

WebRTC requires a persistent P2P connection or SFU. Each viewer consumes about 2 Mbps downstream. For 10,000 viewers, you need 20 Gbps — expensive. Alternative: transcode the stream to HLS on the server and distribute via CDN. This increases latency but saves resources. We use a hybrid scheme: interactive scenarios (voting) via WebRTC for a small group, mass viewing via HLS.

Protocol Comparison

Media Server Comparison

Process

1. Analytics — measure latency requirements, audience size, device types. Determine protocol and server.
2. Design — client-server architecture, stream flow, media server configuration.
3. Implementation — write code in Swift/Kotlin/Flutter, configure server, test on real devices.
4. Testing — load testing (up to 10,000 virtual viewers) and network testing (3G, 4G, Wi-Fi).
5. Deployment — CI/CD, monitoring (Prometheus + Grafana), documentation.

What's Included

• Audit of the current app and architecture selection.
• Streaming integration on one platform (iOS or Android) with RTMP.
• Media server deployment (Wowza or Ant Media).
• WebSocket/Firebase chat with basic moderation.
• Load testing and optimization.
• Instructions for developers and administrators.

Estimated Timeline

• MVP (one protocol, one platform, no chat) — 2–3 weeks.
• Full system (two platforms, LL-HLS/WebRTC, chat, recording) — 2–3 months.

The cost is calculated individually after the audit. Contact us for an accurate quote.

Typical Mistakes

• Using HLS for interactivity — latency kills UX.
• Not setting GOP — packet loss causes artifacts.
• Forgetting the TURN server for WebRTC — clients behind NAT won't connect.
• Skimping on the media server — as audience grows, everything crashes.

Contact us for a consultation — we will select the optimal solution for your budget and timeline. We guarantee stable operation even under peak loads.

How to Choose a Camera Approach on Mobile Platforms?

Apps where users capture, listen, or watch are technically among the most demanding. We deal with this every day. Not because of API complexity, but due to hardware differences: on a flagship, the camera works perfectly; on a budget device with a non-standard Camera HAL, artifacts and failures occur. On iOS, stabilization differs between generations. Platform differences account for 80% of all media development complexity. Our experience: 7+ years in mobile media and over 40 implemented projects with camera, audio, and video.

What are the Differences Between CameraX, Camera2, and AVFoundation?

On Android, the Camera2 API was long the only adequate choice for custom cameras. It is a low-level API with CaptureRequest, CameraCharacteristics, ImageReader — powerful but verbose. Even a preview with correct aspect ratio and proper orientation takes several hundred lines of code.

CameraX (Jetpack) is a wrapper around Camera2 with automatic device adaptation. Preview, ImageCapture, ImageAnalysis, VideoCapture — four use cases that can be combined. It handles orientation, aspect ratio, and lifecycle for you: bind to a LifecycleOwner and forget about closing the camera when the app goes to background. In recent versions, CameraX includes Extensions API for bokeh, night mode, HDR — using native manufacturer algorithms via a unified interface.

When is Camera2 needed directly?: RAW capture via ImageFormat.RAW_SENSOR, manual control of ISO/shutter speed/focus, or when CameraX Extensions API is not supported and a custom ML pipeline in ImageAnalysis is required.

On iOS, AVFoundation is the only path for a custom camera. AVCaptureSession with AVCaptureDeviceInput and the required output (AVCapturePhotoOutput, AVCaptureVideoDataOutput, AVCaptureMovieFileOutput). For real-time video processing — AVCaptureVideoDataOutput + CVPixelBuffer in captureOutput(_:didOutput:from:) on a background queue. This is where CoreML models receive frames for inference.

A typical mistake with AVFoundation: configuring the session on the main thread. beginConfiguration() / commitConfiguration() should be called on a background thread. Otherwise, the preview freezes, and the user sees a frozen UI. This mistake appears in 70% of the projects we have audited.

Why is AudioFocus Critical for Android Apps?

Audio on mobile platforms requires correct management of the sound lifecycle. AudioFocus is a coordination mechanism between apps. AudioManager.requestAudioFocus() with OnAudioFocusChangeListener. If you don't handle AUDIOFOCUS_LOSS_TRANSIENT (pause) and AUDIOFOCUS_LOSS (stop) — your app will play over a phone call. That guarantees a bad review on Google Play. Android Developer Guide: AudioFocus

On iOS, AudioSession categories define behavior: playback — for players (continues playing when screen is locked), record — for recording, muting other sources, playAndRecord — for voice messages. Wrong category — the app mutes the user's background music on start.

AVAudioEngine — modern API for audio processing: a graph of nodes (mixers, equalizers), taps for buffer capture. For real-time speech — SFSpeechRecognizer + inputNode.installTap.

On Android for recording with noise suppression — NoiseSuppressor.isAvailable() + create(audioRecord.audioSessionId). Works not on all devices, need a fallback.

Video: Playback and Streaming

ExoPlayer (Media3) — standard for Android. Supports HLS, DASH, SmoothStreaming, progressive playback. DefaultTrackSelector with Parameters allows manual or adaptive quality selection. DRM via DefaultDrmSessionManager with Widevine L1/L3.

Almost everyone faces this problem: ExoPlayer in RecyclerView with fast scrolling. Need a PlayerPool — a pool of reusable players. Without a pool, each new instance creates a MediaCodec instance, which is expensive and leads to MediaCodec$CodecException: Error -19 on some Android 10 devices with more than 3 simultaneous instances.

AVPlayer / AVPlayerViewController on iOS — for playback. For custom UI — AVPlayerLayer + custom controls. HLS works natively via AVPlayer(url:) with m3u8. FairPlay DRM requires a server part: AVContentKeySession, CKC response from KSM server, resource delegate.

For Flutter — video_player as a base layer, chewie for UI. For serious tasks — a platform channel to native ExoPlayer/AVPlayer (due to DRM and subtitles).

WebRTC on mobile — via native frameworks or flutter_webrtc. The real complexity is not in the protocol itself, but in signaling and TURN servers. Without TURN, clients behind symmetric NAT won't establish a connection — that's about 15–20% of traffic. Coturn is the standard open-source server.

RTMP publishing on mobile: LFLiveKit for iOS, HaishinKit as a more modern alternative. On Android — rtmp-rtsp-stream-client-java or via FFmpeg with JNI. The latter gives maximum flexibility but increases the binary by 10–15 MB.

Media Processing: Compression and Transcoding

ProRes video can take up to 6 GB/minute. Compression is needed before upload. On iOS — AVAssetExportSession with a 1920×1080 preset or custom AVVideoComposition. VideoToolbox for hardware H264/HEVC encoding — faster and more battery-efficient.

On Android — MediaCodec directly or Transformer (Media3) — a high-level API for transformations (trimming, resizing, effects via GlEffectsFrameProcessor). For images — BitmapFactory.Options.inSampleSize for downsampling, Glide / Coil for caching. Coil on Coroutines fits well with Compose. Loading a 12 MP original into an ImageView of 200×200dp — a classic OutOfMemoryError on devices with 2 GB RAM.

How to Implement Streaming on Mobile Devices: Step-by-Step Plan

1. Define requirements: target latency, number of concurrent users, need for P2P.
2. Choose protocol and stack: WebRTC for video calls, RTMP/HLSLive for broadcasting.
3. Set up signaling (SIP, WebSocket, MQTT) and TURN server.
4. Implement publishing/viewing via native API or cross-platform plugin.
5. Test on real devices with different cameras and network conditions.
6. Optimize bitrate and resolution based on bandwidth.

What is Included in the Work

Development Process for Media Functionality

Complexity is non-linear: basic video playback — 1–2 days, custom camera with frame processing and streaming — 3–5 weeks. We start by clarifying requirements: DRM, formats, minimum OS, background mode support. Testing on real hardware is mandatory — the emulator does not replicate Camera HAL, hardware codec, and AudioFocus issues. Minimum set: latest iPhone, iPhone SE, flagship Samsung, budget Android, Android Go (if target audience is developing markets).

Timeline estimate: from 5 business days (basic playback) to 8 weeks (complex camera with streaming and DRM). Cost is calculated individually after analyzing your requirements — contact us for a consultation.

Our service: "Mobile Media Integration" — this is our expertise. Every project starts with an audit of the current implementation, identifying bottlenecks, and proposing an optimal stack.

Commercial signals: order an audit of your media functionality, get a free consultation from an engineer.