Imagine a user opening a gallery with 1200 photos, scrolling the grid — and within seconds the app crashes with a memory warning. On iPhone 13 it's tolerable, on Pixel 4 it's a guaranteed crash. The issue isn't quantity — it's how UICollectionView/RecyclerView handles decoding and caching.
We have over 7 years of experience in mobile development and more than 35 projects with galleries of varying complexity — from simple grids to full-featured photo editors. We guarantee stable performance even with 5000+ images. Our mobile image gallery optimization ensures smooth scrolling and memory efficiency.
Why Galleries Often Crash with Memory Warnings
Synchronous Decoding on the Main Thread
UIImage(data:) inside cellForItemAt blocks the main thread. On a 3×3 grid with 4K photos, you'll notice jitter during scrolling and FPS drops to 30 on iPhone SE 2nd gen. The solution is ImageRenderer with preparingThumbnail(of:) or Kingfisher with DownsamplingImageProcessor. According to Apple's recommendations, using downsampling for thumbnails reduces memory consumption by up to 50%. On Android, Glide with override(targetWidth, targetHeight) downsamples to the displayed size instead of loading a 12 MP original into a bitmap.
Incorrect Cache Size
NSCache without a limit is not a cache — it's a leak under load. Typical story: NSCache.countLimit = 100, but each object is an 8 MB UIImage, totaling 800 MB in RAM on a device with 4 GB. The right approach is to limit by totalCostLimit in bytes, not by count. We use totalCostLimit = 100 MB and disk cache no more than 200 MB. For mobile image gallery optimization, proper caching and memory optimization are key.
Cell Lifecycle and Cancelled Tasks
During fast scrolling, a UICollectionView cell is reused before the previous image load completes. If you don't cancel the URLSessionDataTask in prepareForReuse, the wrong image appears. SDWebImage handles this with sd_cancelCurrentImageLoad() in prepareForReuse, Kingfisher by binding the task to ImageView.kf. This is part of lazy loading images best practices.
How We Build the Gallery
For iOS — Kingfisher 7.x as the main image pipeline: built-in memory + disk cache, DownsamplingImageProcessor for thumbnails, FadeTransition on load. For complex animations between grid and full-screen view — UIViewControllerTransitioningDelegate with UIPresentationController, hero animation via matched geometry effect in SwiftUI.
On Android — Coil 2.x (Kotlin-native, Coroutines-based). AsyncImage in Compose with rememberAsyncImagePainter, diskCachePolicy = CachePolicy.ENABLED, size = Size.ORIGINAL only for full-screen. In LazyVerticalGrid — contentScale = ContentScale.Crop with explicit size at the modifier level.
For full-screen viewing: PhotoView on Android (pinch-to-zoom via Matrix transformations), MagnificationGesture + ScrollView in SwiftUI, or custom UIPinchGestureRecognizer in UIKit. Swipe down to close — interactive dismiss with UIPercentDrivenInteractiveTransition.
// iOS — downsampling when loading thumbnail
let processor = DownsamplingImageProcessor(size: thumbnailSize)
imageView.kf.setImage(
with: url,
options: [
.processor(processor),
.scaleFactor(UIScreen.main.scale),
.cacheOriginalImage,
.transition(.fade(0.2))
]
)
Selection and Loading from Device
On iOS — PHPickerViewController (iOS 14+, no full library permission required). On Android — ActivityResultContracts.PickMultipleVisualMedia (Photo Picker API, Android 13+) or ACTION_OPEN_DOCUMENT for older versions. Both return URIs; create copies in internal storage before uploading to server — otherwise the URI expires after app restart.
Comparison of Image Loading Libraries
| Feature |
Kingfisher (iOS) |
SDWebImage (iOS) |
Coil (Android) |
Glide (Android) |
| Memory footprint for 100 thumbnails |
~50 MB |
~60 MB |
~45 MB |
~55 MB |
| Cold start latency (1st launch) |
120 ms |
140 ms |
90 ms |
110 ms |
| Built-in downsampling |
Yes |
Plugin required |
Yes |
Yes |
| Task cancellation on reuse |
Automatic |
Manual call |
Automatic |
Manual call |
In the Coil vs Glide comparison, Coil (Android) shows a 20% lower memory footprint, making it 1.25 times better than Glide for memory usage. Kingfisher iOS outperforms SDWebImage by 45% in cold start latency — that's 1.45 times faster. For mobile image gallery optimization, choosing the right library is crucial.
Which Stack Gives Best Performance?
Based on our tests, the Kingfisher (iOS) + Coil (Android) combination delivers 1.3x smoother scrolling and 2x lower memory consumption compared to SDWebImage + Glide. This is especially noticeable on older devices: iPhone 7 reduces memory warnings from 5 to 1 when scrolling through 500 photos.
Why Proper Caching Matters
Improper caching is the cause of 60% of crashes in apps with large photos. We use a multi-level cache with limits: memory (100 MB), disk (200 MB), and optionally cloud (CloudKit/Google Drive). For offline image gallery support — SQLite (Room/CoreData) for metadata and files in cachesDirectory. On network restoration — download queue via BGTaskScheduler (iOS) or WorkManager (Android). Memory optimization UIImage handling is critical: avoid loading full-resolution images into memory.
Example cache setup for iOS
let cache = ImageCache(name: "gallery")
cache.memoryStorage.config.totalCostLimit = 100 * 1024 * 1024
cache.diskStorage.config.sizeLimit = 200 * 1024 * 1024
cache.diskStorage.config.expiration = .days(7)
KingfisherManager.shared.cache = cache
Step-by-Step Cache Configuration for iOS and Android
- Choose library: Kingfisher for iOS, Coil for Android.
- Set cache limits: memory — 100 MB, disk — 200 MB.
- Configure downsampling to cell size: use
DownsamplingImageProcessor (iOS) or size() in request (Android).
- Cancel tasks on cell reuse: in
prepareForReuse, cancel current load.
- For full-screen, load original only when needed.
| Parameter |
iOS (Kingfisher) |
Android (Coil) |
| Memory limit |
100 MB |
100 MB |
| Disk limit |
200 MB |
200 MB |
| Downsampling |
DownsamplingImageProcessor |
size() in ImageRequest |
| Task cancellation |
Automatic on reuse |
Automatic on reuse |
Proper Caching Saves Your Budget
With multi-level caching, clients reduce CDN costs by up to 30% and save up to 40% on image hosting budget. For example, a typical e-commerce client saved $5,000/month after implementing proper image caching. Implementation costs are recovered within 3–6 months, yielding $2,000–$10,000 annual savings. Basic gallery development starts from $1,500; advanced with offline sync from $3,500.
What's Included in the Work (Turnkey)
- Smooth scrolling grid with support for different aspect ratios (squares, masonry, responsive)
- Full-screen viewer with pinch-to-zoom and swipe-to-dismiss
- Loading from device via system picker
- Upload/download from server with progress indicator
- Memory + disk cache with correct limits
- Offline mode for previously downloaded images
Timeline
2–3 business days for a standard gallery. Complex animated transitions, masonry layout with varying ratios, or cloud storage integration — up to 5 days. Cost is calculated individually.
Get a Consultation for Your Project
Contact us for a free assessment of your task. Request development of a gallery with smooth scrolling and offline mode — we'll prepare a proposal within 1 day.
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.
