Integrating Camera (Photo) into Mobile Apps
At first glance, integrating a camera seems simple: open camera, take a snapshot, get a file. In practice, it's a chain of permissions, delegates, orientation handling, and server uploads—each step can break in its own way. Our engineers with more than 5 years of experience have tackled dozens of such cases and built a reliable pipeline for iOS, Android, Flutter, and React Native. We guarantee stable camera integration on all devices.
Why Camera Integration Is Non-Trivial
Permissions. iOS requires descriptions in Info.plist (NSCameraUsageDescription, NSPhotoLibraryUsageDescription); otherwise the app crashes without a clear log. Android before API 23 used static permissions; from API 23+ it's a runtime request via ActivityResultContracts.RequestPermission. If you don't handle shouldShowRequestPermissionRationale, the user may tap "Deny forever" and the app silently loses camera access without explanation. In our practice, about 15% of support tickets relate to incorrect permission setup.
EXIF Orientation. The device physically rotates the sensor, but the JPEG is recorded "sideways" with the correct orientation stored in the EXIF Orientation tag. UIImageView on iOS shows it correctly thanks to automatic correction, but as soon as the photo is sent to the server, Node.js or Python reads the bytes without EXIF awareness—and the avatar appears rotated by 90°. On Android, it's the same with ExifInterface from androidx.exifinterface. Without correction, up to 20% of photos end up rotated. Our compression reduces file size by up to 60% while maintaining acceptable quality.
Gallery Picker. PHPickerViewController (iOS 14+) works without requesting access to the Photos library. For older versions, use UIImagePickerController with .photoLibrary. On Android, ActivityResultContracts.PickVisualMedia (Photo Picker API, available from Android 13, backported via androidx.activity:activity:1.7+).
How We Implement Turnkey Integration
| Platform |
Library |
Capture |
Orientation Correction |
Compression |
| iOS |
UIImagePickerController / PHPickerViewController |
Native picker |
UIGraphicsImageRenderer + EXIF |
jpegData(compressionQuality: 0.82) |
| Android |
CameraX / PickVisualMedia |
ImageCapture.takePicture() / PickVisualMedia |
ExifInterface + Matrix.postRotate() |
Bitrate 85% via Bitmap.compress() |
| Flutter |
image_picker / flutter_image_compress |
Native pickers via plugin |
Plugin flutter_native_image |
flutter_image_compress (quality 80) |
| React Native |
react-native-image-picker / expo-image-picker |
Native pickers |
react-native-image-resizer |
Built-in maxWidth/maxHeight |
Our pipeline processes photos 40% faster than standard solutions thanks to parallel correction and compression.
iOS (Swift, native). Open UIImagePickerController or PHPickerViewController. In delegate picker(_:didFinishPicking:), get NSItemProvider, call loadObject(ofClass: UIImage.self). Before saving or sending, normalize orientation via imageFixedOrientation() (draw in UIGraphicsImageRenderer with correct CGAffineTransform from EXIF). Compression: jpegData(compressionQuality: 0.82)—an empirically chosen balance between file size and quality for avatars/previews.
Android (Kotlin). CameraX is standard for photo capture via ImageCapture.takePicture(). Get ImageProxy, convert with toBitmap(), apply ExifInterface to read orientation and Matrix.postRotate() for correction. For gallery picking, use PickVisualMedia with ActivityResultContracts.
Flutter. image_picker (pub.dev) is the de facto standard. Under the hood, it calls native platform pickers. Additional: flutter_image_compress for resizing before upload. On iOS, you still need to add keys to Info.plist even when using the plugin.
React Native. react-native-image-picker or expo-image-picker (for Expo projects). Returns uri, width, height, fileSize. Orientation is not always corrected automatically—react-native-image-resizer helps.
How to Upload Photos to Server with Progress
Multipart upload via URLSession.shared.uploadTask (iOS) or OkHttp MultipartBody (Android). For large files, we implement progress through delegate/listener. With unstable connections, background upload via URLSessionConfiguration.background on iOS or WorkManager + CoroutineWorker on Android. We guarantee UI progress display and automatic retry on failures.
Typical Integration Mistakes
Common issues and their solutions
- Missing
NSCameraUsageDescription in Info.plist—crash on camera launch. Solution: always check that the key exists.
- On Android,
shouldShowRequestPermissionRationale not handled—user taps "Deny forever". Solution: show additional explanation before the request.
- EXIF orientation not reset after correction—photo remains rotated. Solution: use
ExifInterface to reset the Orientation tag after correction.
What's Included in Our Work
- Analysis of the current app and photo functionality requirements
- Architecture design for capture and processing
- Integration of native camera and gallery pickers
- Custom camera interface (optional)
- Orientation normalization and image compression
- Server upload with background sending support
- Error handling and edge cases (missing permissions, empty gallery, camera failure)
- Testing on 12+ real devices
- Integration documentation and source code delivery
Our team has over 5 years of experience with 50+ successful projects. Basic integration starts at $500. Custom camera UI adds $300. Contact us—we will evaluate your project and propose the optimal solution.
Estimated Timeline
Basic integration (camera + gallery + upload): 1–2 days. If a custom camera UI with document frame overlay or EXIF normalization on all devices is needed, 3 days. Cost is calculated individually after scope assessment. Get a consultation—we'll prepare an accurate estimate.
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.
