We often encounter this task: a user wants to crop an avatar into a circle with a 1:1 ratio. A developer takes UIImageView, adds a pinch-to-zoom gesture – and after a day realizes that transforms accumulate incorrectly, and on export the image is cropped to a different rectangle than the user sees. To avoid such mistakes, a systematic approach to coordinate handling is needed. An error in recalculation is the most common cause of defects in mobile editors. We analyzed over 50 projects and found that 60% of errors are related precisely to coordinate recalculation.
The Core Problem: Coordinate System During Cropping
The editor displays a preview in an imageView of a certain size, but the original image is 4000×3000 px. The crop rectangle in screen coordinates must be recalculated to original image coordinates. The scale factor is imageView.bounds vs image.size, accounting for contentMode. UIImageView with aspectFit adds letterbox padding – these must be subtracted before scaling. On Android, the same story with Matrix and getImageMatrix() on ImageView.
How the Coordinate System Works During Cropping?
We implement a function cropRectInImageCoordinates() that:
- Takes the scaling factor (bounds.width / image.width adjusted for contentMode)
- Subtracts letterbox padding (if contentMode = aspectFit)
- Applies UIScrollView transform (offset and scale)
- Returns a CGRect in pixel coordinates of the original
Without this step, even a perfect UI produces an image cropped from the wrong location.
How We Build the Editor
iOS. Two options: ready-made CropViewController from TOCropViewController or a custom implementation. For most tasks, TOCropViewController covers 90% of requirements – aspect ratios, rotation, circular mask. If a custom UI is needed, we build a UIScrollView with UIImageView inside, with a CAShapeLayer cutout on top. During final export:
let cropRect = cropRectInImageCoordinates() // recalculated from UI coordinates
let cgImage = image.cgImage!.cropping(to: cropRect)
let result = UIImage(cgImage: cgImage!, scale: image.scale, orientation: image.imageOrientation)
Android. uCrop – the de facto standard. UCrop.of(sourceUri, destinationUri).withAspectRatio(1f, 1f).start(activity). Under the hood, OpenGL ES for smooth preview, final cropping via BitmapRegionDecoder to save memory on large sources.
Flutter. image_cropper (pub.dev) – wraps uCrop on Android and TOCropViewController on iOS. Customization via CropStyle, CropAspectRatio. For a fully native Flutter solution – the crop package.
Which Approach to Choose: Ready Libraries or Custom Solution?
| Criterion |
image_cropper |
Custom (extended_image) |
| Reliability |
high (native code) |
depends on implementation |
| UI customization |
limited |
full control |
| Performance |
excellent |
good (pure Dart) |
| Integration complexity |
low |
medium |
| Gesture support |
pinch/rotate |
pinch/rotate via GestureDetector |
For simple scenarios, image_cropper is faster. When unique design is needed, we go custom.
Why GPU Shaders Are Faster Than CPU for Color Correction?
Brightness, contrast, saturation – typical operations we implement via GPU. On iOS – CIFilter: CIColorControls (brightness, contrast, saturation), CIExposureAdjust, CIHueAdjust. Render via CIContext with kCIContextUseSoftwareRenderer: false – use GPU, avoid slowdowns. On Android – ColorMatrix + ColorMatrixColorFilter for basic corrections, or RenderScript (deprecated in API 31) → GPUImage (OpenGL ES). For new projects – androidx.renderscript via renderscript-toolkit. We do real-time preview with a debounce on the slider (150ms) to avoid overloading the GPU during fast slider movement. Compared to CPU processing, GPU yields up to 60% performance improvement when working with 12 MP images.
Saving the Result
We export to JPEG (compressionQuality: 0.88 – balance of quality and size for standard avatars). For documents – lossless PNG. Temporary files go to Caches, final files to Documents or via FileProvider (Android). We also preserve EXIF metadata if needed.
| Format |
When to Use |
Quality |
File Size |
| JPEG (0.88) |
Avatars, web |
Good |
~100-300 KB |
| PNG |
Documents, transparency |
Lossless |
~500 KB – 2 MB |
Steps to Integrate Cropping into a Project
- Choose a library or custom component based on design.
- Configure aspect ratios and allowed transformations.
- Implement coordinate recalculation for correct export.
- Integrate preview with debounce and GPU rendering.
- Test on devices with different screen resolutions.
Apple Developer Documentation: CIColorControls – more details on filters.
What’s Included in the Work
- Analysis of your design and functional requirements.
- Choice of library or development of a custom component.
- Implementation of cropping, rotation, color correction.
- Export integration (JPEG/PNG) with metadata preservation.
- Performance optimization (GPU rendering, debounce).
- Integration documentation and support during deployment.
Additional information on GPU optimization
For intensive operations (e.g., sepia, vignette), we use Metal Performance Shaders on iOS and OpenGL ES on Android. This allows processing 4K images in 200–400 ms.
Timeline and Cost
A simple cropper with fixed aspect ratio and rotate buttons – 2 days. An editor with brightness/contrast correction, multiple ratios, and real-time preview – 3–4 days. Cost is calculated individually after discussing the project. Contact us – we'll evaluate your task and propose the optimal solution.
We have 5+ years of experience in mobile editor development and over 30 successful turnkey projects. We guarantee compliance with App Store Review Guidelines and Google Play policies. Get a consultation – write to us on Telegram or by email.
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.
