When a user drags a photo onto a template, scales it, rotates it, and adds text — any lag in rendering is immediately noticeable. The entire UI must run on the GPU, not the CPU. We specialize in building mobile collage and photo album apps that maintain 60 FPS even during concurrent pinch, rotate, and pan gestures. With over five years of experience and more than 50 successful releases on the App Store and Google Play, we deliver stable performance even on mid-range devices. Contact our engineers for a project consultation.
Canvas Performance: Avoiding Lag During Manipulations
iOS. We avoid using UIImageView for every layer because Core Animation does not GPU-accelerate transformations when using transform. Instead, we build a CALayer hierarchy or use Metal rendering via MTKView. For most collages (up to 10–15 layers), CALayer suffices: each element is a sublayer with contents = CGImage, and transformations via CATransform3D are GPU-backed. CATiledLayer handles large background images. For final file output, we use UIGraphicsImageRenderer or a Metal pipeline to accurately capture transformations.
Android. The Canvas approach on SurfaceView or TextureView works but makes layer management complex. We prefer a custom View with drawBitmap and a transformation matrix per element. For advanced effects, we use OpenGL ES through GLSurfaceView. In Jetpack Compose, the Canvas Composable with drawImage(paint = ...) is fast for simple cases; for large projects we rely on OpenGL.
Flutter. We use CustomPainter with canvas.drawImageRect for images and canvas.drawParagraph for text. To avoid redrawing the entire scene, each editable element is wrapped in a RepaintBoundary. Flutter then repaints only the changed layer.
| Platform |
Primary Approach |
GPU Acceleration |
Layer Complexity |
Typical Latency (ms) |
| iOS |
CALayer / Metal |
Yes |
Medium |
≤16 |
| Android |
Custom View / GLSurfaceView |
Yes |
High |
≤20 |
| Flutter |
CustomPainter + RepaintBoundary |
Yes |
Low |
≤16 |
Synchronous Gesture Handling for Scale, Rotation, and Pan
Processing pinch, rotate, and pan simultaneously is standard but tricky to implement correctly. On iOS, we use UIPinchGestureRecognizer, UIRotationGestureRecognizer, and UIPanGestureRecognizer together with shouldRecognizeSimultaneouslyWith. Each gesture’s delta is applied incrementally to the element’s CATransform3D — never an absolute value, otherwise the element jumps when a new gesture starts. UIPinchGestureRecognizer documentation
On Android, we combine ScaleGestureDetector with a manually implemented RotationGestureDetector (tracking two touch points) and GestureDetector. ScaleGestureDetector documentation
Flutter: GestureDetector with onScaleUpdate handles both scale and rotation in one callback (ScaleUpdateDetails.rotation). We also implement snap-to-grid and snap-to-center: when dragging, we check proximity to axes (±10 dp) and canvas center, snapping with haptic feedback if close.
Why Store Collage Templates as JSON?
A template defines the number of cells, their positions, and aspect ratios. We store them as JSON: an array of {x, y, width, height, rotation} in 0-to-1 units relative to the collage size. At runtime, we scale to the screen dimensions. Users fill cells with photos from the gallery using PHPickerViewController (iOS 14+), PhotoPicker (Android), or image_picker (Flutter) — modern pickers that don’t require full gallery permission. The user chooses between fit or fill for each cell, cropping or padding as needed.
On a recent project, we reduced gesture latency from 50 ms to under 16 ms on mid-range devices by switching to Metal rendering on iOS and optimizing transform delta calculations for Android. This allowed smooth real-time previews even on devices like the iPhone 8 and Samsung Galaxy A50.
What We Guarantee
We follow a methodology proven on 50+ projects. For iOS, the final build undergoes code review and testing on devices running iOS 15 and above. For Android, we test on emulators and physical devices with Android 10+. We ensure no memory leaks (monitored via Instruments and LeakCanary) and stable 60 FPS during gestures. We provide technical documentation and support during deployment.
Export Resolutions
We render the final collage offline at 2x–3x screen resolution for social media, or at 300 DPI for a given physical print size. Rendering progress is shown via Progress or ProgressBar. Saving to Photos uses PHPhotoLibrary.performChanges (iOS) or MediaStore.Images.Media.insertImage (Android).
| Target Use |
Resolution |
Format |
Approx. File Size |
| Social media |
2x–3x screen (up to 12 MP) |
JPEG/PNG |
1–5 MB |
| Print (10×15 cm) |
300 DPI (1181×1772 px) |
PNG |
3–8 MB |
| Print (20×30 cm) |
300 DPI (2362×3543 px) |
PNG |
10–25 MB |
What's Included in Our Work
- UX/UI analysis and prototyping (wireframes, user flows)
- Canvas implementation with GPU acceleration (Metal / OpenGL / CustomPainter)
- Template system (10–15 built-in, custom possible)
- Gesture handling (pinch, rotate, pan, snap-to-grid)
- High-resolution export (2x–3x, 300 DPI)
- Testing on real devices (iOS/Android)
- Deployment to App Store and Google Play, code signing setup
- Documentation and team training
Timelines and Pricing
A basic editor with 10–15 templates, text, and export takes 3–4 weeks. A full editor with stickers, filters, custom templates, and cloud storage takes 6–8 weeks. Cost is determined individually after analyzing your requirements. Contact us for a stack and timeline consultation.
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.
