Mobile Video Editor: Smooth Trimming, Merging, and Export

We encounter the task of integrating a video editor in almost every second mobile project. Clients want users to trim extra seconds, merge several clips, or overlay text — all without 30-second freezes. It seems video APIs are available on every platform, but there are plenty of pitfalls: frame-accurate trimming, smooth timeline, fast export without blocking the UI. Let's dive into how we solve these problems on iOS and Android. This guide covers mobile video trimming, iOS video editor Swift implementation, and Android video editing Kotlin techniques.

Why Video Trimming Is Not a Trivial Task

Time-range trimming. On iOS we use AVAssetExportSession with timeRange:

exportSession.timeRange = CMTimeRange( start: CMTime(seconds: startTime, preferredTimescale: 600), duration: CMTime(seconds: duration, preferredTimescale: 600) ) 

Apple's official documentation recommends preferredTimescale: 600 for video frame accuracy. preferredTimescale: 600 is the standard for video, multiples of 24/25/30/60 fps. Using timescale: 1 causes frame rounding errors. On Android — MediaMuxer + MediaExtractor for frame-accurate trimming without re-encoding (only if keyframes align). If not — Transformer from media3 with explicit re-encoding. This approach guarantees frame-level accuracy, critical for professional editing.

How to Merge Clips Without Quality Loss

Merging clips. iOS: AVMutableComposition — add AVMutableCompositionTrack for video and audio, insert via insertTimeRange(_:of:at:). Important: audio tracks are merged separately from video tracks, otherwise desync. Android: media3 Transformer with Composition API (1.2.x+). Clip sequence — EditedMediaItemSequence. We configure audio mix so transitions are seamless — no clicks or delays.

Text overlays. iOS: AVVideoComposition + AVVideoCompositionCoreAnimationTool. Create a CATextLayer, add appearance animation via CABasicAnimation, pass to animationTool. On Android — OverlayEffect in media3 Transformer or draw via Canvas on each frame (slow, only for short content). For long videos we prefer native overlays via SurfaceView — up to 3x performance gain compared to Canvas.

Step-by-Step: Building a Timeline Preview

1. Generate frame thumbnails using AVAssetImageGenerator on iOS or MediaMetadataRetriever on Android. Request frames every 0.1 second for timeline scrubber.
2. Cache generated images in an LRU cache to prevent lag during scrolling.
3. Display thumbnails in a horizontal scroll view. On iOS, use UICollectionView with custom layout; on Android, RecyclerView with LinearLayoutManager.
4. Handle user drag: update current time marker and seek video accordingly.

generator.generateCGImagesAsynchronously(forTimes: times) { _, image, _, _, _ in DispatchQueue.main.async { thumbnailView.image = UIImage(cgImage: image) } } 

Export

Always async, with progress. iOS: exportSession.progress via Timer every 0.1 s. Android: Transformer.addListener with onProgress(progress: Float). Output format: H.264 in MP4 — maximum compatibility. H.265 (HEVC) — smaller size, but not all servers accept without transcoding.

Performance comparison: native iOS via AVAssetExportSession is 2–3x faster than an equivalent FFmpeg solution (thanks to hardware decoding). On Android, MediaCodec with H.264 gives up to 50% speedup over software encoding.

Cross-Platform Considerations: Flutter's video_editor

video_editor (available on pub.dev) provides UI components (timeline, cropper) but relies on ffmpeg_kit_flutter for actual operations. The trade-off is cross-platform UI code versus performance: FFmpeg processes video on CPU, which is significantly slower than native AVFoundation or MediaCodec. For example, exporting a 2-minute clip takes ~45 seconds with FFmpeg vs ~12 seconds with native code — a 3.75x difference. Therefore, we recommend native implementation for production-grade apps, while Flutter solution suffices for MVPs or occasional use. Our team has successfully migrated two clients from Flutter to native, reducing export time by an average of 70%.

Our Track Record

With over 5 years of experience and 20+ media apps delivered (including streaming video editors and UGC apps), our team of 10+ engineers specializes in high-performance mobile video processing. We have successfully shipped editors for clients ranging from startups to Fortune 500 companies, achieving an average App Store rating of 4.5+. Our solutions reduce development time and cost by up to 30% compared to in-house builds, saving clients an average of $1,500 on basic features alone.

What We Deliver

• Requirements analysis (trimming, merging, overlays, effects)
• Architecture design: framework selection, processing pipeline setup
• Core module implementation: trimming, composition, export with unit tests
• Timeline integration with preview and gesture handling
• Performance optimization: frame caching, async processing, hardware acceleration
• Testing on various devices (iPhone SE — iPhone 15 Pro, Xiaomi Redmi — Samsung Galaxy S24)
• Build and deployment to App Store / Google Play with code signing and provisioning profiles
• Integration documentation (API schemas, code examples, store setup guide)
• Training and knowledge transfer for your team
• Post-deployment support for 30 days
• Access to source code and build scripts

We guarantee that the implemented functionality will pass App Store moderation (Section 4.2 — minimalism, 5.1 — privacy) and Google Play (media usage policy).

Timeline and Investment

Basic time-range trimming + export: $2,000–$3,000 (2–3 working days). Full editor with timeline, clip merging, and text overlays: $5,000–$8,000 (5–8 working days). Timelines refine after a briefing: complexity depends on the number of effects, HDR support, subtitle handling. Contact us for a free project estimate.