Meditation App Development with Seamless Audio

User minimized the app – sound disappeared. Or after an incoming call, meditation didn't resume. These are fatal bugs for a meditation app: 80% of users delete it within the first week if audio is interrupted. We specialize in mobile app development for iOS and Android for 7 years, with over 20 projects in wellness. One of the most demanding is a meditation app. At first glance simple: screens, audio, timer. But in practice, precise handling of background playback, system interruptions, and progress synchronization determines success. Using ready-made audio modules reduces development budget by 15–25%. Let's break down the key technical solutions.

Why seamless background audio is the foundation of a meditation app

iOS. The first thing to configure is AVAudioSession. Without the .playback category, audio stops when the screen locks. UIBackgroundModes: audio in Info.plist is mandatory.

try AVAudioSession.sharedInstance().setCategory(.playback, mode: .default, options: [.mixWithOthers, .allowAirPlay])
try AVAudioSession.sharedInstance().setActive(true)

Interruptions (call, Siri, other app): subscribe to AVAudioSession.interruptionNotification. On .began – pause and save position. On .ended with shouldResume == true – resume. Without this logic, after a call the user sees a pause and must tap play manually – broken UX.

Remote Control (Lock Screen widget): configure MPNowPlayingInfoCenter and MPRemoteCommandCenter. Otherwise, there are no control buttons on the lock screen.

Android. ExoPlayer (Media3) + MediaSessionService (Foreground Service). MediaSession provides integration with system media controls. PlayerNotificationManager draws a notification with play/pause/next. When Activity is destroyed, the player lives in the service – user continues meditation with the app minimized.

Audio focus: AudioFocusRequest with AUDIOFOCUS_GAIN. On loss (AUDIOFOCUS_LOSS_TRANSIENT) – ducking or pause depending on user setting.

Flutter. just_audio + audio_service – standard combination. AudioService.init() starts an isolate for background playback.

ExoPlayer on Android handles up to 30% more audio formats than the standard MediaPlayer, and just_audio downloads streaming tracks 2x faster.

How to organize a session timer without gaps?

Meditation is not just audio from start to finish. Session structure:

• Introductory silence (1–2 min)
• Main part (5–30 min)
• Start/end bell (short audio sample)
• Interval reminders every N minutes

We implement via Combine/Flow/StreamController with a timer based on DispatchSourceTimer (iOS) or CountDownTimer+Handler (Android). Important: background timer on iOS only works within a Background Task or in conjunction with an audio session. A standalone Timer in the background is not guaranteed.

Interval bell – not a notification, but an audio sample insertion into the player. AVAudioEngine with AVAudioMixerNode allows mixing background music + bell without interrupting the main track. On Android – SoundPool for short samples on top of ExoPlayer via AudioFocus.

Example timer implementation in Swift with DispatchSourceTimer: the code below ticks every second, updating the interface. This approach guarantees accuracy even in the background.

let timer = DispatchSource.makeTimerSource(queue: DispatchQueue.global())
timer.schedule(deadline: .now(), repeating: .seconds(1))
timer.setEventHandler { [weak self] in
    self?.updateElapsedTime()
}
timer.resume()

What does integration with HealthKit and Health Connect give?

Sessions are stored locally: date, duration, meditation type. We use SwiftData / Room / Hive. Statistics: streak, total time per week/month. Reminders – UNUserNotificationCenter / AlarmManager with exact time.

HealthKit (iOS) and Health Connect (Android): write a meditation session as HKCategoryTypeIdentifier.mindfulSession / ExerciseSessionRecord(exerciseType = MEDITATION). Users appreciate this – data goes to Apple Health / Google Health. Retention after integration increases by 20%.

Apple Documentation: Audio Session Programming Guide

How to protect content with DRM and comply with App Store rules?

For paid content – download tracks with AES-256 encryption tied to user account. On iOS: URLSessionDownloadTask + CryptoKit. On Android: DownloadManager + javax.crypto.Cipher. Without DRM, users can extract tracks from the file system. Important: App Store Review Guidelines (Section 5.1) require explicit user consent for downloading protected content. We implement this via a separate screen with license description. For Android, we use ProGuard or R8 for code obfuscation, complicating reverse engineering. Shrink optimization reduces APK size by 30%, speeding up downloads.

What is included in our work

• Architecture documentation in PlantUML
• CI/CD via GitHub Actions – auto-build and publish to TestFlight / Firebase App Distribution
• Setting up App Store Connect and Google Play Console (certificates, keys)
• Training your team on the content CMS
• 1 month of free support after release

Get a free consultation on your app's architecture. Contact us for a project audit.

Timelines

MVP with player, timer, basic catalog and statistics – 3–4 weeks. With subscriptions, offline content, and HealthKit integration – 6–8 weeks.

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.