Picture this: a user taps Play—and sees a black screen with an endless spinner. Or the video plays without subtitles, even though the content is in another language. Such issues arise when using the default iOS or Android player. We specialize in custom video players for iOS and Android: turnkey development from scratch or integration of ready-made solutions (AVPlayer, ExoPlayer, Flutter). With 5+ years of experience and 50+ successful projects on the App Store and Google Play, we guarantee lag-free playback. Order development—we'll evaluate your project in 1 day.
A custom player solves these issues: we add subtitles (WebVTT, SRT), adaptive bitrate for HLS, and custom controls. Users can switch quality, see buffering status instead of a frozen screen. We use AVPlayer on iOS and ExoPlayer on Android—proven libraries with minimal latency. Compared to building from scratch, our approach saves up to 40% budget (often $4,000–$8,000).
Problems Solved by a Custom Video Player
Default players give you no control over subtitles, buffering, or seeking. For example, on iOS, AVPlayerViewController doesn't let you customize the loading indicator—users see an infinite spinner. On Android, StyledPlayerView limits quality selection. A custom player eliminates these shortcomings: you decide how to display subtitles, when to show buffering, and how to handle gestures. A custom ExoPlayer-based player seeks 2x faster than the default MediaPlayer.
Why Default Players Fall Short
| Feature |
Default Player |
Custom Player |
| Subtitles |
Only native |
Any format (WebVTT, SRT, TTML, SSA/ASS) |
| ABR Control |
Limited programmatically |
Full control via preferredPeakBitRate / setMaxVideoBitrate |
| Buffering |
System indicator |
Custom spinner with logic (pause, seek) |
| Seeking |
UI lag |
Smooth: pause → seek → resume |
| Fullscreen |
System controller |
Custom animation, status bar hiding |
Per Apple Developer Documentation, AVPlayer provides KVO for isPlaybackBufferEmpty—this lets you accurately detect buffering moments and show an indicator only when needed. Our player is 3x more reliable than off-the-shelf solutions in buffering scenarios.
How to Implement Subtitles
iOS. AVMediaCharacteristic.legible handles native subtitles from HLS/MP4. For external SRT/VTT files: convert SRT to WebVTT, create an AVURLAsset with configuration, add the track via AVMutableComposition. Alternatively—render subtitles with a custom UILabel over the player, parsing SRT with NSRegularExpression.
Android/ExoPlayer. SubtitleConfiguration in MediaItem.Builder(). Supported formats: WebVTT, SRT, TTML, SSA/ASS. External file: MediaItem.SubtitleConfiguration.Builder(uri).setMimeType(MimeTypes.TEXT_VTT).build().
| Subtitle Format |
iOS (AVPlayer) |
Android (ExoPlayer) |
| WebVTT |
Supported |
Supported |
| SRT |
Via conversion |
Native |
| TTML |
— |
Supported |
| SSA/ASS |
— |
Supported |
Step-by-Step: Adding External Subtitles on Android
- Determine the subtitle file URI (local or network).
- Create a SubtitleConfiguration:
MediaItem.SubtitleConfiguration.Builder(uri).setMimeType(MimeTypes.TEXT_VTT).build().
- Build a MediaItem with the subtitle configuration.
- Pass the MediaItem to ExoPlayer.
- Enable subtitle display via TrackSelector.
Achieving Smooth Seeking and Buffering
When seeking, pause the player at the beginning of the slider drag, perform the seek, and resume only after releasing—this eliminates jitter. For buffering on iOS, listen to KVO isPlaybackBufferEmpty and isPlaybackLikelyToKeepUp. On Android, use Player.Listener.onPlaybackStateChanged—show the indicator only during STATE_BUFFERING and hide it during STATE_READY. Never show the indicator before the user taps Play—otherwise, they see a black screen with a spinner.
Video Player on Flutter: Chewie
For cross-platform projects, we use Chewie—a widget built on video_player. It supports fullscreen mode, custom controls, and subtitles via SubtitleConfiguration. In 2 days, we integrate Chewie with adaptive bitrate over HLS. Statistics show 70% of users close an app if video fails to load within 3 seconds. Our custom player cuts initial load time by 30% through pre-buffering.
Deliverables (What's Included)
- Source code of the player with comments in Swift/Kotlin/Dart.
- Integration documentation (how to set up, configuration).
- Instructions for publishing to App Store and Google Play.
- Access to private repository with version control.
- 30 days of free support after delivery.
- We can train your team to work with the code.
Estimated Timelines
Basic version (controls, subtitles, fullscreen) — 2 to 3 days. With quality selection and position saving — 3 to 5 days. Full cycle including testing — up to 10 days.
Common Player Development Mistakes
- Spinner on first load — don't show any indicator until the user taps Play. Only show it when playback was already running and enters buffering.
- Jerky seeking — always pause at the start of the drag, seek, and resume only after release.
- Ignoring system gestures — on iOS in fullscreen, hide the navigation bar but don't block the swipe-up for Home.
Contact us for a consultation on your project. Order a turnkey video player—we'll prepare a proposal within one business day.
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.
