Background music in a mobile game may play for 40 minutes straight; the player pauses at any moment, and the budget for the soundtrack is part of the whole, always limited. The gaming market requires license-clean music that adapts to gameplay with a minimal build size. Our team is mobile audio engineers with 8+ years of experience and over 50 projects shipped on App Store and Google Play.
The standard approach — one track looped via AudioSource.loop = true. After 10–15 minutes the player disables it in settings. This is not a volume issue — it's psychoacoustics. The brain detects the pattern and starts anticipating it, causing irritation.
We apply three proven solutions to avoid this problem: long loops with internal variations, horizontal layers (layered adaptive), and stingers with transitions. These techniques keep the player's attention 2x longer compared to a linear track — based on internal tests.
Why does background music quickly become tiresome?
The standard approach — one track looped via AudioSource.loop = true. After 10–15 minutes the player disables it in settings. This is not a volume issue — it's psychoacoustics. The brain detects the pattern and starts anticipating it, causing irritation. Solutions that work:
Long Loops with Internal Variations
A track 3–5 minutes long instead of 90 seconds. The longer the cycle, the later the brain recognizes it. Inside the track — arrangement changes: one instrumental layer removed for 30 seconds, a rhythmic pattern change, a new melodic phrase. The listener perceives it as development, not repetition.
Horizontal layers (layered adaptive)
The track is split into independent layers: drums, bass, melody, atmosphere. In calm gameplay — only atmosphere and bass. In intense combat — all four layers. Wwise and FMOD implement this via Music Switch Container and Music Blend Container. In Unity without middleware — AudioMixer with multiple AudioSource, whose levels are changed via AudioMixer.SetFloat.
Stingers and Transitions
Short musical phrases (2–8 bars) that insert at the right moment: level victory, enemy detection, reward collection. The stinger plays on top of the main track — compatible keys and BPM are required.
Genre and Atmosphere Determine Instrumentation
For a casual puzzle — light, positive themes with no strong percussion, ambient textures, piano, and melodic synthesizers. BPM 80–100. Forgiving of repetition better than energetic music.
For action/RPG — orchestral elements (strings, brass, percussion) or hybrid orchestra (live instruments + synthetic). Spitfire LABS, Cinematic Studio Strings as virtual instruments. The sound scale must match the game scale — orchestral soundtrack in a casual puzzle will feel out of place.
For retro/pixel art games — chiptune via synthesis (Famitracker, LSDJ, DefleMask) or plugins (TripleOscillator, 8BitSFX). FM synthesis emulation of Yamaha OPL for YM2612 Genesis sound.
Seamless Loop Points
The most technical aspect — correctly placing loop points. WAV file with loop start/end markers: in Reaper via Region, in Adobe Audition via Loop. In Unity — via AudioClip.SetData or import with Loop in settings. Two requirements for the loop point: musically logical (start of a bar or phrase) and click-free (zero crossing points or a 5–10 ms fadeout/fadein).
Click at the loop seam is the most frequent complaint. It occurs when the waveform at the loop point is not at zero crossing. AudioUnit on iOS and AudioFlinger on Android do not perform automatic crossfade — responsibility lies on the audio layer of the engine or middleware.
What is better: adaptive music or linear track?
Adaptive music holds the player's attention 2x longer compared to a linear track (internal test data). Additionally, it reduces the feeling of monotony and allows finer tuning of emotional response. However, it requires more resources to implement — proper layer architecture and integration with gameplay.
The soundtrack creation process includes the following stages:
- Analysis of GDD and references
- Writing the theme (melody, harmony, arrangement)
- Creating stems and adaptive layers for middleware
- Placing loop points, testing on target devices
- Exporting WAV masters + stems + integration instructions
- Support during integration into the engine (Unity/Unreal/other)
Checklist of Typical Mistakes
- No fade at loop seam (click)
- Key mismatch between stinger and main track
- Too loud compared to UI sounds
- Use of unlicensed samples (violation of App Store Review Guidelines Section 4.2)
Scope and Timelines
| Game Scale |
Tracks |
Duration |
Timelines |
| Hyper-casual |
1–2 |
90s – 3min |
1 week |
| Casual / Puzzle |
3–5 |
2–4 min each |
2–4 weeks |
| Mid-core / RPG |
8–15 |
3–6 min + stingers |
1–3 months |
| Delivery Type |
Composition |
Timeline |
| Minimal |
WAV masters |
Included above |
| Extended |
+ stems + layers for Wwise/FMOD |
+2–3 days |
| Full |
+ adaptive presets + consultation |
+1 week |
Delivery: WAV masters + stems (separate instrumental layers) for adaptive integration. Cost is calculated individually after requirement analysis. Contact us to discuss your project — we will estimate scope and budget within 2 business days. Order music for your game now.
We apply psychoacoustic principles and use Wwise for adaptive solutions.
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.
