We integrate Wwise into mobile games: replacing standard Unity Audio with professional audio middleware Wwise that delivers adaptive soundtracks, RTPC, and 3D positioning. Without Wwise, you're limited to playing back files — sound doesn't react to the game state. The result is "cardboard" audio that players perceive as lagging behind the gameplay.
Consider an example: an open-world RPG where background music changes with time of day and enemy proximity. Without Wwise, you'd have to write crossfades in C# and sync them manually. With Wwise — one Music Switch Container with Day/Night/Combat tracks, parameters TimeOfDay and EnemyProximity, transitions configured in the editor. Players report 40% higher immersion compared to static audio. [cite]Wwise SDK Documentation[/cite]
Wwise is not just a player, but a system of events, parameterized RTPC parameters, and automatic compilation into SoundBanks. On mobile platforms, it uses hardware codecs (AAC for iOS, Vorbis for Android) and allows fine-grained performance tuning. The Wwise SDK recommends keeping voice count below 25 for mid-range devices.
How Integration Works
Wwise does not work with WAV files at runtime. The process: sounds → Wwise Authoring → SoundBank (.bnk) → loaded via SDK. Code calls Wwise events by name: AkSoundEngine.PostEvent("Play_Footstep_Wood", gameObject).
Installation. The Wwise Unity integration is installed via the Wwise Launcher. The SDK and plugin versions must match — otherwise compilation errors on mobile. For iOS: AkiOS.framework + Podfile, for Android: .aar via mainTemplate.gradle.
SoundBank optimization. Sounds are compiled into banks via Wwise Authoring or command line (WwiseCLI). For mobile: iOS — AAC, Android — Vorbis. Size control: load only needed banks for the scene, unload via AkBankManager.UnloadBank.
How RTPC Make Sound Alive
Game Parameters (RTPC). Real-time parameter control is the heart of interactive audio. The parameter Health (0-100) changes pitch and filter on an ambient track: as health drops, the music becomes darker and more tense. One parameter, one Wwise event, any complexity of mapping through a curve in Wwise.
Music Switch Container. Adaptive music Wwise without seams. Transitions between states (Exploration → Combat → Victory) occur at a musically correct moment — on a downbeat or cue point. AkSoundEngine.SetState("MusicState", "Combat") — Wwise chooses the moment.
Why Wwise Over Standard Unity Audio?
| Criteria |
Unity Audio |
Wwise |
| Events |
Only Play/Stop |
Parameterized events + RTPC |
| Adaptive music |
Manual implementation |
Music Switch Container with transitions |
| 3D positioning |
Attenuation curves |
Attenuation + Occlusion + Reflect |
| CPU load on mobile |
~1-2% at 10 voices |
~3-5% at 25 voices (adjustable) |
| Profiling |
None |
Wwise Profiler over Wi-Fi |
| Compression |
Vorbis (built-in) |
Vorbis/AAC with selectable bitrate |
Wwise is up to 5x more efficient than standard Unity Audio for complex soundscapes, reducing implementation time by 3x.
Spatializer and 3D audio. Attenuation curves, obstruction/occlusion, room acoustics via Wwise Reflect. On mobile — use cautiously: Reflect adds CPU load, noticeable on mid-range Android. Typically we limit to Attenuation + Doppler.
Profiler. Wwise Profiler connects to the device over Wi-Fi. Real-time: which events are playing, CPU usage of audio, voice count, SoundBank memory. Target: no more than 20-25 simultaneous voices, audio thread CPU 3-5%.
Performance Tuning on Mobile
| Parameter |
Recommendation |
| Voice count |
20-25 for mid-range, 30-35 for high-end |
| CPU usage |
3-5% at 25 voices |
| SoundBank size |
No more than 5 MB per level |
| Codec |
AAC 192 kbps for iOS, Vorbis 128 kbps for Android |
| Sample rate |
44100 Hz, stereo |
// Unity — example of calling an event with a parameter
void PlayFootstep(SurfaceType surface) {
AkSoundEngine.SetSwitch("Surface", surface.ToString(), gameObject);
AkSoundEngine.PostEvent("Play_Footstep", gameObject);
}
// Updating RTPC parameter for health
void OnHealthChanged(float health) {
AkSoundEngine.SetRTPCValue("PlayerHealth", health, gameObject);
}
What's Included in the Integration Work?
- Audio audit — evaluate your sound content, identify problem areas.
- SoundBank optimization — split into banks per scene, configure 100+ RTPC parameters.
- SDK integration — install Wwise into the project, set up builds for iOS and Android.
- Event and RTPC creation — link to game mechanics (health, speed, weapons).
- Adaptive music setup — Music Switch Container, transitions, sync with gameplay.
- Performance optimization — reduce voice count, test on real devices.
- Documentation and training — hand over SoundBanks, scripts, instructions for your team.
Common Integration Issues and Solutions
- Audio loss on Android after app suspend. Handle
OnApplicationPause: call AkSoundEngine.Suspend(true) on pause and WakeupFromSuspend() on resume. Otherwise the Android AudioSession is not restored.
- Bloated SoundBanks. All sounds in one Default SoundBank — initial load takes 5-8 seconds. Solution: split into per-level banks (MenuBank, Level1Bank) and load asynchronously.
- Conflict with other audio. If using a video player or AdMob, configure AVAudioSession priorities on iOS: Wwise should set the
.playback category with correct mix options.
Timelines and How to Start
Basic integration — 3-5 working days. Full integration (adaptive music, 50+ RTPC, optimization) — up to 2 weeks. Cost is calculated individually. Basic integration starts at $1,500 (3-5 days). Full integration from $3,000. We guarantee a fully functional integration within agreed timeline and provide a 30-day support period. Contact us — we'll assess your project in one day. Get a consultation: our engineers with 5+ years of experience and 50+ mobile projects can help. Order Wwise integration and make your game's sound alive.
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.
