Implementing Video Filters in a Mobile App

Real-time Video Filter Implementation in Mobile Apps

Developing video filters for mobile apps is always a trade-off between image quality and performance. One client came with a task: apply LUT filters to 4K 60fps video in real time. On an iPhone 14 Pro, initial tests delivered 12 fps—dropping every other frame. The issue was creating a new CIContext for each frame. After optimization, GPU utilization dropped to 30%, and fps stabilized at 60. We use GPU shaders for frame processing. On iOS: Swift with Metal; on Android: GLSL or Vulkan. For cross-platform projects, we implement native modules via platform channels.

Two Modes: Preview and Export

Real-time preview (during playback) requires GPU processing without writing the result to a file. Export—final recording with applied filter—can take seconds but must be frame-accurate.

Why a Single CIContext Matters

Creating a new CIContext per frame is a performance killer. On an iPhone 13, this yields 3–4 fps instead of 30. The context is created once and reused. A Metal-backed CIContext is mandatory: CIContext(mtlDevice: MTLCreateSystemDefaultDevice()!). Without explicit specification, some devices fall back to CPU rendering, causing video stutter.

How to Avoid FPS Drops During Export

The CVPixelBuffer from renderContext.newPixelBuffer() must be returned immediately after finish(withComposedVideoFrame:). Holding a reference leads to buffer pool exhaustion and crashes with kCVReturnInvalidArgument. On Android: GPUImageFilter is not thread-safe—you cannot apply the same instance from multiple threads simultaneously.

Platform Comparison

Performance: CPU vs GPU

iOS: AVVideoComposition + Core Image

AVVideoCompositionCoreAnimationTool is suitable for static overlays like text and logos. For pixel-level filters, we use AVVideoComposition with a custom AVVideoCompositing:

class FilterCompositor: NSObject, AVVideoCompositing {
    func startRequest(_ asyncVideoCompositionRequest: AVAsynchronousVideoCompositionRequest) {
        guard let frame = asyncVideoCompositionRequest.sourceFrame(byTrackID: trackID) else { return }
        let ciImage = CIImage(cvPixelBuffer: frame)
        let filtered = applyFilter(ciImage)
        let output = asyncVideoCompositionRequest.renderContext.newPixelBuffer()!
        ciContext.render(filtered, to: output)
        asyncVideoCompositionRequest.finish(withComposedVideoFrame: output)
    }
}

For LUT filters, we use CIColorCubeWithColorSpace with a 64×64×64 table. Learn more about Core Image.

Android: GPUImage and media3 Effects

Real-time preview uses GPUImageView with a custom GPUImageFilter. Shaders are written in GLSL:

precision mediump float;
uniform sampler2D inputImageTexture;
varying vec2 textureCoordinate;
void main() {
    vec4 color = texture2D(inputImageTexture, textureCoordinate);
    float luma = dot(color.rgb, vec3(0.299, 0.587, 0.114));
    gl_FragColor = vec4(mix(vec3(luma), color.rgb, 1.3), color.a);
}

For export with filter, we use media3 Transformer with GlEffect. MatrixTextureProcessor accepts the shader and applies it to each frame during transcoding.

Flutter. Full real-time video filters require platform code. Native plugins with MethodChannel are the only viable approach for production applications.

Applying Filters to Live Camera Recording

An even more demanding scenario is applying filters during capture. On iOS: AVCaptureSession + AVCaptureVideoDataOutput → SampleBufferDelegate → Metal shader → render into MTKView. The chain latency must be < 16 ms for 60fps. The pixel format kCVPixelFormatType_420YpCbCr8BiPlanarFullRange (YUV) converts faster to a Metal texture than BGRA.

On Android: CameraX Analysis + ImageAnalysis.Analyzer → GLES shader → GLSurfaceView. Using ImageAnalysis.STRATEGY_KEEP_ONLY_LATEST discards old frames if the GPU hasn't finished processing the previous one.

Process of Work

1. Analysis: Assess filter requirements, target devices, desired fps.
2. Design: Choose architecture (native/cross-platform), prototype shaders.
3. Implementation: Write GPU shaders, integrate with AVFoundation/Media3, optimize performance.
4. Testing: On real devices (iPhone 8–14, Samsung Galaxy S10–S23), measure fps, check for artifacts.
5. Deployment: Publish to App Store/Google Play, configure TestFlight/App Distribution.

What Is Included in the Work

• Source code for shaders and integration (Swift, Kotlin, Dart).
• Integration and configuration documentation.
• Instructions for adding new filters.
• One month of support after delivery.
• Testing on 3+ real devices.

Timeline and Guarantees

5–7 business days: Develop shaders for 5–8 filters, integrate preview and export on iOS and Android. Flutter version with native code adds 2 days. The cost is calculated individually—contact us for an estimate. We guarantee stable filter operation on devices from iPhone 8 and Android 10. Our experience: 5+ years in mobile development, 30+ video-processing projects. Get in touch—we'll help implement video filters for your app.

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.