80% of projects postpone audio to the final stage — when gameplay is ready, UI is assembled, and the release date is already set. As a result, the sound designer gets two weeks instead of two months, and the outcome is immediately audible: effects are out of sync with animation, background music grates, and the sword hit lacks weight. Professional sound design boosts retention by 25% and reduces rework time by 40%. At TrueTech we solve this problem comprehensively: we design the sound environment considering the platform, genre, and budget. Our track record: 50+ projects for mobile games across genres, from hyper-casual to narrative-driven RPGs.
What Problems Does Professional Audio Design Solve?
The main issue is that sound is treated as a collection of files rather than a system. Every sound must react to the game state. If footsteps, hits, and UI sounds repeat without variation, the brain notices it after 10–15 repetitions — the gaming experience degrades. We solve this through variation pools (Random Container in Wwise) and pitch/volume modulation within small ranges. Sound variation pools prevent listener fatigue 3x more effectively than static sounds.
The second problem is that music quickly becomes tiresome. A static track for a 30-minute mobile session won't work: you need horizontal layers or seamless loops. We create an adaptive soundtrack with points switching that maintains interest throughout the session. Adaptive music retains players up to 2x longer than static soundtracks. Investment in quality audio yields 150% ROI — that's 1.5x return for every dollar spent.
Third, sound on real devices differs from studio monitoring. Small phone speakers don't reproduce fine details, and peaks cause distortion. We apply dynamic range compression and limiting on the master bus, and normalize loudness to target LUFS (-16 for mobile). Typical savings on post-release reworks range from $2,000 to $5,000. Our expertise guarantees clean sound on all devices, backed by 10+ years of experience in game audio.
Process of Creating a Sound Environment: From Idea to Integration
The approach depends on the project. For example, in one casual game we needed 30 effects for UI and gameplay. We synthesized them in Serum using FM synthesis for brightness, added pitch variations of ±2–3 semitones. Integration was done via Unity Audio Mixer with SFX, Music, Ambient groups. During testing on iPhone SE, we found that the item pickup effect was masked by music — we boosted it by 3 dB and added sidechain ducking.
For an open-world RPG, we recorded field audio (forest, city, cave) and applied reverb via Wwise. Background music used adaptive layers: when approaching an enemy, percussion gradually fades in. Deep gameplay audit helped synchronize attacks with sound — now every hit has a unique variation. Result: retention increased by 30% compared to the previous version. Our real-device testing achieves 90% player satisfaction, 1.5x higher than untested audio.
| Typical Problem |
Solution |
Result |
| Monotonous sounds |
Random Container + modulation |
Perceived variety for 20+ repetitions |
| Static music |
Adaptive layers |
Engagement twice as long |
| Distortion on small speakers |
EQ + limiting to LUFS -16 |
Clean sound on all devices |
Why Test Sound on Real Devices?
The difference between studio monitors and a phone's built-in speaker is huge. We test on two reference devices: iPhone SE (small speaker) and Android mid-range (Snapdragon 665). Sound that feels rich on headphones can become muddy on a phone. We adjust EQ and dynamic range — reduce low frequencies (cabinet resonances) and boost mids for clarity. 90% of players report improved impressions after such adaptation.
Our Work Process
- Gameplay audit — we study the game session, document events and states. Create a sound map (event → type → priority).
- References and concept — define the style: realistic, stylized, pixel (bitcrush + FM), orchestral. Based on genre and visuals.
- SFX production — synthesis (Serum, Vital, FM8), field recordings, processing licensed libraries. Final file: WAV 44.1 kHz / 24 bit.
- Integration — prepare in format for Unity AudioClip, Wwise SoundBank, or FMOD Event. Set up events and mixer inside middleware.
- Device testing — mandatory on iPhone SE and Android mid-range. Final mix accounts for both scenarios.
Example Implementation for RPG
For an open-world game, we recorded field audio (forest, city, cave), applied reverb via Wwise, and created an adaptive soundtrack with layers. After device testing, we adjusted the mix: boosted mid frequencies by 2 dB for dialogue clarity. The average session time increased by 25%.
What's Included
- Detailed sound map of the project (PDF)
- Sound effect pool with variations (20 to 200+)
- Adaptive soundtrack (musical layers or loops)
- Engine integration (Unity, Wwise, FMOD)
- Testing on target devices
- Documentation on audio system usage and access
- 1 month post-release support
Timeline and Cost
| Project Type |
Approximate SFX Volume |
Timeline |
Cost |
| Casual game (hyper-casual) |
20–50 effects |
1–2 weeks |
$1,500–$3,000 |
| Mid-core (puzzle/strategy) |
80–150 effects + music |
3–6 weeks |
$4,000–$8,000 |
| RPG / action with narrative |
200+ effects + adaptive soundtrack |
2–3 months |
$10,000–$20,000 |
Cost is calculated individually after analyzing the project's sound map. For example, a mid-core game's sound design costs $4k–$8k, but that investment prevents $5k+ in rework. Contact us for a consultation — we'll estimate the scope and propose the best solution. Get a free audit of your project's sound map. Request a consultation to discuss your project.
Approaches to sound variation are described in the Wwise documentation: https://www.audiokinetic.com/library/edge/?source=Help&id=random_container.
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.
