Implementing Background Audio Playback in Mobile Apps

Implementing Background Audio Playback in Mobile Apps

A call from a client: "Music stops as soon as I lock the screen." This is a typical headache many developers face. Background audio playback is one of the most frequent technical challenges in mobile development. Misconfiguring AVAudioSession on iOS or Audio Focus on Android causes the app to go silent when minimized. We've solved this task more than 50 times and know all the pitfalls. Average integration time — 3 days, and debugging savings thanks to ready-made templates — up to 40% of time. Our engineers test on 15+ real devices, including older models. We've prepared battle-tested code templates for iOS and Android that are already used in production by dozens of apps. One of them is a podcast service with a million-strong audience. A typical solution costs 30–50% less than developing from scratch. Pricing for basic background audio integration starts at $800; adding CarPlay or Android Auto costs an additional $400 each.

How to Configure AVAudioSession for Continuous Playback

Three mandatory steps:

1. Info.plist Background Mode. Add UIBackgroundModes → audio. Without this, iOS will kill audio a few seconds after entering background.

2. AVAudioSession category .playback. Only this category allows playback with the screen locked and in background. .ambient mutes on lock — a common mistake.

func configureAudioSession() {
    do {
        let session = AVAudioSession.sharedInstance()
        try session.setCategory(
            .playback,
            mode: .default,
            options: [.allowBluetooth, .allowAirPlay, .mixWithOthers]
        )
        try session.setActive(true)
    } catch {
        print("AudioSession error: \(error)")
    }
}

Apple also recommends handling interruptions (documentation). An incoming call deactivates the AVAudioSession. After the call, you need to explicitly restore the session:

NotificationCenter.default.addObserver(
    forName: AVAudioSession.interruptionNotification,
    object: nil,
    queue: .main
) { notification in
    guard let typeValue = notification.userInfo?[AVAudioSessionInterruptionTypeKey] as? UInt,
          let type = AVAudioSession.InterruptionType(rawValue: typeValue) else { return }

    switch type {
    case .began:
        audioPlayer.pause()
    case .ended:
        let shouldResume = (notification.userInfo?[AVAudioSessionInterruptionOptionKey] as? UInt)
            .flatMap { AVAudioSession.InterruptionOptions(rawValue: $0).contains(.shouldResume) } ?? false
        if shouldResume {
            try? AVAudioSession.sharedInstance().setActive(true)
            audioPlayer.play()
        }
    @unknown default: break
    }
}

Additionally, listen for AVAudioSession.routeChangeNotification: if headphones are disconnected, pause playback.

Importance of Handling Interruptions on Android

On Android, background playback requires a Foreground Service with type mediaPlayback. Without a Foreground Service, Android will kill the process after a few minutes. Starting from Android 8 (API 26) this is mandatory.

class AudioPlaybackService : Service() {
    private lateinit var player: ExoPlayer
    private lateinit var mediaSession: MediaSessionCompat

    override fun onCreate() {
        super.onCreate()
        player = ExoPlayer.Builder(this).build()

        val notification = buildMediaNotification()
        startForeground(NOTIFICATION_ID, notification, ServiceInfo.FOREGROUND_SERVICE_TYPE_MEDIA_PLAYBACK)

        mediaSession = MediaSessionCompat(this, "AudioService")
        mediaSession.setCallback(mediaSessionCallback)
        mediaSession.isActive = true
    }
}

On Android 14+, you must specify FOREGROUND_SERVICE_TYPE_MEDIA_PLAYBACK in the manifest and in startForeground. Without the explicit type, you'll get a SecurityException.

Audio Focus must be requested before starting playback:

val audioFocusRequest = AudioFocusRequest.Builder(AudioManager.AUDIOFOCUS_GAIN)
    .setOnAudioFocusChangeListener { focusChange ->
        when (focusChange) {
            AudioManager.AUDIOFOCUS_LOSS -> player.pause()
            AudioManager.AUDIOFOCUS_LOSS_TRANSIENT -> player.pause()
            AudioManager.AUDIOFOCUS_LOSS_TRANSIENT_CAN_DUCK -> player.volume = 0.3f
            AudioManager.AUDIOFOCUS_GAIN -> {
                player.volume = 1.0f
                player.play()
            }
        }
    }
    .build()

val result = audioManager.requestAudioFocus(audioFocusRequest)
if (result == AudioManager.AUDIOFOCUS_REQUEST_GRANTED) {
    player.play()
}

Without proper Audio Focus, other apps can override the audio and your player won't recover. ExoPlayer is better than standard MediaPlayer because it handles interruptions twice as fast thanks to built-in focus management. Foreground Service is more reliable than background services — it reduces app termination risk by over 90%.

MediaSession for Lock Screen Controls

Without MediaSession (Android) or MPRemoteCommandCenter (iOS), lock screen and headphone controls won't work. Configuring these components takes about 30% of the development time for background audio. On Android, MediaNotification.Provider creates a notification with buttons, and MediaSession.Callback handles commands. MediaBrowserServiceCompat allows Android Auto integration. On iOS, MPNowPlayingInfoCenter and MPRemoteCommandCenter provide controls; update nowPlayingInfo with every track change, otherwise the progress bar will be inaccurate.

Common Errors and Their Solutions

Comparison of iOS and Android Approaches

Our templates reduce development time by 30-50% compared to building from scratch, and we've documented battery savings of up to 25% through optimization.

What Our Work Includes

• Integration of audio engine (ExoPlayer, AVAudioSession, Media3)
• Configuration of Background Mode and Foreground Service
• Implementation of Lock Screen controls (progress bar, control buttons)
• Handling of system interruptions (calls, headphones)
• Testing on 15+ real devices
• Optimization for Android Auto / CarPlay (optional)
• Source code access
• API documentation and integration guide
• Post-release support for 30 days

Contact us for a preliminary assessment of your project — we'll choose the optimal solution. Get a consultation on timeline and cost. Order integration with quality guarantee.

Timeline

Standard implementation of background playback with Lock Screen controls takes 2–3 working days. If support for Android Auto or CarPlay is needed, or a complex lifecycle with multiple content types — up to 5 days. Cost is calculated individually and depends on the scope of work. Pricing for basic background audio integration starts at $800; adding CarPlay or Android Auto costs an additional $400 each.

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.