HLS/DASH Adaptive Video Streaming in Mobile Apps
When a mobile app streams video over unstable LTE, standard MP4 files cause pixelation and perpetual buffering. We’ve faced this dozens of times and built a robust player architecture. The solution is adaptive streaming via HLS (HTTP Live Streaming) or DASH (Dynamic Adaptive Streaming over HTTP). The player loads a manifest (.m3u8 for HLS, .mpd for DASH) describing video segments at different bitrates. By dynamically switching quality based on available bandwidth, we achieve smooth playback even on poor connections.
Our track record: 5+ years building custom video players from scratch, with over 20 completed projects for iOS and Android. We guarantee stable playback even on low-bandwidth networks. Contact us to evaluate your project—we’ll recommend the optimal stack for your requirements.
HLS vs DASH: Which One to Choose
| Parameter |
HLS |
DASH |
| Native iOS support |
Yes (AVFoundation) |
No (needs third-party library) |
| Native Android support |
No (needs ExoPlayer) |
No (needs ExoPlayer) |
| Latency (standard) |
6–30 s |
2–10 s |
| Low-Latency |
LL-HLS: ~2 s |
LL-DASH: ~1–3 s |
| DRM support |
FairPlay (iOS), Widevine |
Widevine, PlayReady |
In practice: if your audience is iOS‑dominant and DRM is not required, HLS needs no third‑party library. For cross‑platform apps with minimal latency, DASH via ExoPlayer is the way to go. ExoPlayer documentation: https://exoplayer.dev
Why AVPlayer Beats Third‑Party Players on iOS
AVPlayer is built into the system—it uses hardware decoding and manages buffering automatically. For HLS, it offers the best performance, providing a 2–3× faster startup time compared to custom solutions built on top of third‑party SDKs. Initialization example:
let asset = AVURLAsset(url: hlsURL, options: [
"AVURLAssetHTTPHeaderFieldsKey": ["Authorization": "Bearer \(token)"]
])
let item = AVPlayerItem(asset: asset)
player = AVPlayer(playerItem: item)
Monitor buffering via KVO on item.isPlaybackLikelyToKeepUp and item.loadedTimeRanges. When isPlaybackLikelyToKeepUp == false—show a spinner; when true—hide it.
Preload the next video by creating an AVPlayerItem in advance and adding it to an AVQueuePlayer; the first segment of the next video starts downloading in the background.
Important: AVPlayer supports LL-HLS starting from iOS 12. To enable low-latency, set playerItem.preferredForwardBufferDuration = 1.0. This reduces the buffer to 1 second but increases the risk of interruptions. We recommend this value only for stable networks.
How ExoPlayer Handles HLS and DASH on Android
ExoPlayer is Google’s recommended library. It automatically selects the source based on the URL extension. Example code:
val player = ExoPlayer.Builder(context).build()
// HLS
val hlsItem = MediaItem.Builder()
.setUri("https://example.com/stream.m3u8")
.build()
// DASH
val dashItem = MediaItem.Builder()
.setUri("https://example.com/manifest.mpd")
.build()
player.setMediaItem(hlsItem)
player.prepare()
player.play()
For custom headers:
val dataSourceFactory = DefaultHttpDataSource.Factory()
.setDefaultRequestProperties(mapOf("Authorization" to "Bearer $token"))
val hlsSource = HlsMediaSource.Factory(dataSourceFactory)
.createMediaSource(MediaItem.fromUri(uri))
Adaptive Bitrate
By default, ExoPlayer uses AdaptiveTrackSelection—it switches quality at segment boundaries (typically every 2–10 s). To set a minimum quality:
val trackSelector = DefaultTrackSelector(context)
trackSelector.parameters = trackSelector.buildUponParameters()
.setMaxVideoSizeSd() // never above 480p on weak devices
.build()
On iOS, AVPlayerItem.preferredPeakBitRate = 2_000_000 caps the upper bitrate; this can save up to 40% data usage.
How to Configure Low‑Latency HLS
Low‑Latency HLS (LL‑HLS) reduces latency to ~2 seconds using partial segments and HTTP/2 push.
- On iOS: set
playerItem.preferredForwardBufferDuration = 1.0 and player.automaticallyPreservesTimeOffsetFromLive = true.
- On Android (ExoPlayer 2.12+): create a
LiveConfiguration with targetOffsetMs = 2000 and pass it to MediaItem.Builder().setLiveConfiguration(...).
- Ensure your CDN supports partial segments (e.g., AWS MediaTailor or Akamai LL‑HLS).
- Test on real devices—playback should start in ~2 seconds.
| Parameter |
LL‑HLS |
LL‑DASH |
| Latency |
2–3 s |
1–3 s |
| iOS support |
Yes (iOS 12+) |
No |
| Android support |
ExoPlayer 2.12+ |
ExoPlayer 2.12+ |
| Implementation complexity |
Medium |
High |
Network Error Handling
The network is unreliable—a segment fails to load, the manifest returns 403, the CDN responds with 5xx. ExoPlayer automatically retries with exponential backoff (DefaultLoadErrorHandlingPolicy). Custom policy:
class RetryPolicy : DefaultLoadErrorHandlingPolicy() {
override fun getRetryDelayMsFor(loadErrorInfo: LoadErrorInfo) =
if (loadErrorInfo.errorCount < 5) 1000L * loadErrorInfo.errorCount else RETRY_DELAY_UNSET
}
On iOS: AVPlayerItem.status == .failed → player.currentItem?.error—read the NSError, show a “Retry” button. Important: after an error, discard the old AVPlayerItem and create a new one; otherwise, a retry might not work.
Case Study: Live Sports Streaming App
For a client’s live sports streaming app, we reduced initial buffering from 8 seconds to 1.2 seconds by implementing LL‑HLS on iOS and optimizing segment size to 2 seconds. On Android, we used ExoPlayer with a custom LoadErrorHandlingPolicy that reduced rebuffering events by 60% during peak traffic. This resulted in a 30% increase in user retention.
What’s Included in the Work
- Requirements analysis and protocol selection (HLS/DASH)
- Player development with ABR, caching, and DRM (FairPlay/Widevine)
- Analytics integration (buffering events, errors)
- API documentation and deployment guide
- Testing on real devices with various network speeds
- Post‑release support (1 month)
Common DRM Integration Mistakes
- Incorrect
AVAssetResourceLoaderDelegate setup for FairPlay—missing SPC certificate.
- For Widevine on Android—not providing the license in
MediaItem.Builder().setDrmConfiguration(...).
- Forgetting to check DRM support on the device: on Android—
DrmSessionManager, on iOS—AVAssetResourceLoadingRequest.
Estimated Timelines
HLS player on one platform with ABR and error handling—from 2 days. Cross‑platform (iOS + Android) with DASH, DRM, and manual quality selection—4 to 5 days. If LL‑HLS or a specific DRM integration is required, the timeline may increase by 1–2 days. Get a consultation—we’ll calculate the exact timeline for your project.
Order custom video player development: we guarantee stability and low latency. We’ll evaluate your project for free.
Apple HLS Authoring Specification: https://developer.apple.com/documentation/http_live_streaming
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).
| Protocol |
Latency |
Application |
| RTMP |
2–5 sec |
Streaming to YouTube/Twitch |
| HLS |
6–30 sec |
VOD, broadcast |
| DASH |
6–30 sec |
VOD with adaptive bitrate |
| WebRTC |
< 500 ms |
Video calls, P2P |
| SRT |
1–4 sec |
Professional streaming |
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
- Define requirements: target latency, number of concurrent users, need for P2P.
- Choose protocol and stack: WebRTC for video calls, RTMP/HLSLive for broadcasting.
- Set up signaling (SIP, WebSocket, MQTT) and TURN server.
- Implement publishing/viewing via native API or cross-platform plugin.
- Test on real devices with different cameras and network conditions.
- Optimize bitrate and resolution based on bandwidth.
Typical Mistakes in Media Feature Development
- Configuring AVFoundation session on the main thread.
- Missing AudioFocus Loss handling on Android.
- Ignoring
MediaCodec limitations on cheap devices.
- Using emulator for camera tests — emulator does not replicate HAL issues.
- Memory leaks when recreating media players without a pool.
What is Included in the Work
| Deliverable |
Description |
| Requirements analysis |
Stack selection, priorities, test devices |
| Design |
Architecture, data flow diagrams, API selection |
| Implementation |
Code using chosen tools |
| Backend integration |
GraphQL/REST, DRM, WebRTC signaling |
| Testing |
On real devices (at least 5 models) |
| Documentation |
API documentation, build instructions |
| Post-release support |
1 month incident support, team training |
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.
