Integrating FFmpeg for Media Processing in Mobile Apps

Why FFmpeg on a Mobile Device?

You're developing a video editing app, and built-in frameworks (AVFoundation, MediaCodec) fall short. You need frame-accurate trimming, concatenation of multiple clips, hardware acceleration, and flexible encoding settings. Sending video to a server is slow and expensive, and users demand privacy. FFmpeg solves these tasks directly on the device. We integrate it into iOS, Android, and Flutter, configure the optimal ffmpeg-kit build, and connect hardware encoders VideoToolbox or MediaCodec. This reduces CPU load and accelerates processing by 5–10x. With over 50 successful media processing integrations, we guarantee compatibility with App Store and Google Play requirements — including app size optimization and license compliance.

What Problems Does FFmpeg Solve on Mobile?

FFmpeg enables any media file operation: transcoding, trimming, concatenation, watermarking, volume adjustment, and more. Here are typical commands:

For quick trimming, use -c copy — no re-encoding, keyframe accuracy. For frame-accurate trimming, omit -c copy but it takes longer. In UI, offer a choice: "Fast Trim" and "Accurate Trim".

How to Choose the Optimal ffmpeg-kit Build?

The build choice directly affects app size and available functionality. The minimal build (min) weighs 8–12 MB and includes basic codecs (H.264, AAC) — enough for trimming and conversion. If you need HTTPS support (e.g., downloading files over network) — choose the https build. For H.265, VP9, or audio codecs FLAC/opus, full (~50 MB) is required. For GPL-compatible projects, use full-gpl. We recommend the https build as the optimal balance of functionality and size. More details on variants can be found in the ffmpeg-kit documentation.

How to Integrate FFmpeg into a Project?

iOS. ffmpeg-kit with CocoaPods — minimal setup in 15 minutes:

// Podfile
pod 'ffmpeg-kit-ios-https', '~> 6.0'

// Usage
FFmpegKit.executeAsync("-i input.mp4 -vn -acodec copy output.aac") { session in
    guard let returnCode = session?.getReturnCode() else { return }
    if ReturnCode.isSuccess(returnCode) {
        print("Done: \(session?.getOutput() ?? "")")
    } else {
        print("Error: \(session?.getLogsAsString() ?? "")")
    }
}

Android. Via Maven:

implementation("com.arthenica:ffmpeg-kit-android-https:6.0.LTS")

FFmpegKit.executeAsync(
    "-i input.mp4 -vf scale=1280:720 -c:v libx264 -preset ultrafast -crf 23 output.mp4"
) { session ->
    if (ReturnCode.isSuccess(session.returnCode)) {
        // process result on main thread
    }
}

Flutter. Install the ffmpeg_kit_flutter package from pub.dev — Dart wrapper identical to native API.

Monitoring Processing Progress

FFmpeg writes progress to stderr. ffmpeg-kit provides StatisticsCallback, where getTime() returns the current position in milliseconds. Obtain total duration via FFprobeKit.getMediaInformationAsync.

FFmpegKit.executeAsync(command,
    withCompleteCallback: { session in /* complete */ },
    withLogCallback: nil,
    withStatisticsCallback: { stats in
        guard let duration = totalDurationMs else { return }
        let progress = Double(stats?.getTime() ?? 0) / duration
        DispatchQueue.main.async { self.progressBar.progress = Float(progress) }
    }
)

Step-by-Step Integration Guide

1. Choose a build. Determine required codecs and protocols. For a typical app — https.
2. Add dependency. Include the dependency (CocoaPods, Maven, or pub.dev). Test a basic command, e.g., getting file info.
3. Optimize performance. Enable hardware acceleration via h264_videotoolbox (iOS) or h264_mediacodec (Android) with a software fallback.

On iPhone 14 Pro, transcoding a 1-minute 1080p video via libx264 ultrafast takes 45–60 seconds. That's too long for UX. We use hardware encoders: iOS — h264_videotoolbox (via VideoToolbox) — 5–10x faster, but less bitrate control. Android — h264_mediacodec (via MediaCodec) — similar. Add a software fallback:

val command = if (isHardwareEncoderAvailable()) {
    "-i input.mp4 -c:v h264_mediacodec output.mp4"
} else {
    "-i input.mp4 -c:v libx264 -preset ultrafast output.mp4"
}

Binary size: the full build adds 30–50 MB to the app, min — 8–12 MB. Choose the minimal one for specific tasks.

What’s Included in the Integration?

• Selection and configuration of the optimal ffmpeg-kit build (considering licenses and size).
• Development of an API for commands (transcoding, trimming, concatenation, etc.).
• Integration of progress monitoring and UI display.
• Hardware acceleration support with fallback.
• ProGuard/R8 configuration (Android) for minification.
• Usage documentation.
• Testing on 5+ real devices.
• Post-deployment support for 30 days.

FFmpeg integration reduces server processing costs by up to 40%, saving infrastructure budget. It pays for itself within 2–3 months. Contact us for a project assessment — we'll prepare a proposal within 1 business day. Request a consultation to discuss details and get a tailored work plan.

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.