Problem: Player Disappears During Navigation
You are developing a music app and notice: when navigating from the track list to the settings screen, the player disappears — it gets recreated along with the ViewController. The user loses playback context and often abandons the listening session. Over 5 years of work, we have encountered this in dozens of projects and developed a solution — a mini-player with a persistent overlay that lives outside the navigation stack. Our team of certified iOS and Android developers has implemented such mini-players in over 100 projects, reducing progress desynchronization bugs by 80% in one case.
How Does a Mini-Player Solve the Context Loss Problem?
A mini-player is a lightweight view anchored at the window or root container level. It does not depend on screen changes and remains visible during any transitions. On iOS, we place it above the tabBar; on Android, in a root Box. This architecture ensures the user always sees the current track and can control playback without being distracted from content.
Why Is State Synchronization Critical?
If the mini-player is not synchronized with the main player, progress and playback state diverge. The user sees one track but hears another. A single source of truth — a singleton PlayerViewModel (iOS) or StateFlow (Android). The mini-player subscribes to changes via @Published or collectAsState(). In one project, this approach reduced progress desynchronization bugs by 80%.
How We Implement the Mini-Player
iOS (UIKit)
We add the mini-player as a subview over the tabBar in a custom UITabBarController. Shifting additionalSafeAreaInsets.bottom compensates for the player's height in child controllers.
// In custom UITabBarController
override func viewDidLoad() {
super.viewDidLoad()
miniPlayerView = MiniPlayerView()
view.addSubview(miniPlayerView)
NSLayoutConstraint.activate([
miniPlayerView.bottomAnchor.constraint(equalTo: tabBar.topAnchor),
miniPlayerView.leadingAnchor.constraint(equalTo: view.leadingAnchor),
miniPlayerView.trailingAnchor.constraint(equalTo: view.trailingAnchor),
miniPlayerView.heightAnchor.constraint(equalToConstant: 64)
])
// Shift safe area for child VCs
additionalSafeAreaInsets.bottom = 64
}
iOS (SwiftUI)
Use .overlay(alignment: .bottom) on the root TabView. The player state is a singleton @EnvironmentObject. Expansion animation uses matchedGeometryEffect for smooth transition — this reduces code by 1.5x compared to UIKit.
Android (Jetpack Compose)
Place the mini-player in a root Box above NavHost. For gestures, use anchoredDraggable with COLLAPSED and EXPANDED anchors. ModalBottomSheet with sheetPeekHeight sets the mini-player height. Development time — 2–3 days.
React Native
The mini-player is an absolute component with position: absolute and bottom equal to the tab bar height. Animation uses Animated.View with PanResponder. Suitable for cross-platform projects but offers less animation flexibility.
Stages of Mini-Player Integration
| Stage |
Description |
Duration |
| Analysis |
Study current navigation and audio player architecture |
1 day |
| Design |
Determine overlay layer and synchronization method |
0.5 day |
| Implementation |
Develop mini-player with animations and gestures |
2-3 days |
| Integration |
Connect to existing player and test |
1 day |
| Deployment |
Publish to App Store / Google Play |
0.5 day |
Approach Comparison: UIKit vs SwiftUI vs Compose
| Platform |
Reliability |
Development Time |
Animation Flexibility |
| UIKit |
High |
2-3 days |
Medium (UIViewPropertyAnimator) |
| SwiftUI |
Medium |
1-2 days |
High (matchedGeometryEffect) |
| Compose |
High |
2-3 days |
High (animate*AsState) |
| React Native |
Medium |
2-3 days |
Medium (Animated API) |
SwiftUI is faster to develop but less reliable for complex gestures. Compose combines high reliability and flexibility.
Gestures and Accessibility
Swipe up to expand, swipe down to collapse. On iOS — UIGestureRecognizer with threshold translation.y > 100. On Android Compose — swipeable with anchors. VoiceOver/TalkBack: accessibilityLabel and accessibilityHint. The pause button is a separate element.
Common Implementation Mistakes
| Mistake |
Solution |
| Keyboard overlap |
Fix bottom by considering keyboard insets |
| Ignoring safeAreaInsets on iPhone X+ |
Use safeAreaLayoutGuide in UIKit or WindowInsets in Compose |
| No synchronization during background loading |
Apply BackgroundTask on iOS or WorkManager on Android |
What Is Included in the Work
- Analysis of current navigation architecture
- Design of the overlay component tailored to your needs
- Implementation of the mini-player with expand/collapse animation
- Integration with existing audio player (AVPlayer, ExoPlayer)
- Gesture and accessibility setup
- Testing on devices with different OS versions
Timelines and Pricing
Development of a mini-player on a single platform — 2-3 days. For two platforms with gesture control — 3-4 days. Pricing is calculated individually, depending on animation complexity and backend integration. Our team has 5+ years of experience and consists of certified iOS and Android developers. If you need a mini-player with custom animations, contact us for a discussion. Order a mini-player development turnkey and get a consultation.
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.
