We implement end-to-end video sending in mobile chat apps — from file selection to inline player. Raw camera footage cannot be uploaded directly: without transcoding and chunked upload, users wait minutes, and on weak connections they get timeouts. Our team has over a decade of experience in iOS and Android development, with more than 50 video integration projects for chat apps. We guarantee stability and performance.
Why video upload requires transcoding
Video from an iPhone 14 Pro at 4K/60fps weighs ~400 MB per minute. Even a 15-second clip is 100 MB. Uploading that directly is unacceptable in both time and data usage.
On iOS, video from PHPickerViewController or UIImagePickerController arrives as MOV (HEVC or H.264). It must be transcoded before upload. The standard path uses AVAssetExportSession with preset AVAssetExportPresetMediumQuality (720p, ~2 Mbit/s) or AVAssetExportPreset1280x720. Export is asynchronous, taking 2–30 seconds depending on clip length and device model. On iPhone SE 2nd gen, transcoding a 30-second video to 720p takes about 8 seconds.
On Android, the situation is more complex: MediaMuxer + MediaCodec give maximum control but require heavy coding. For most projects we use FFmpegKit (a mobile FFmpeg fork) — it lets you set bitrate, resolution, and codec with a single command: -vcodec libx264 -crf 28 -vf scale=720:-2. The downside is adding ~15 MB to the APK.
How to ensure resumable upload
Video cannot be uploaded in a single request without resume support. If the connection drops, all progress is lost.
The proper approach is multipart upload on the server side (AWS S3 Multipart Upload, Cloudflare R2, or custom chunked upload). The file is divided into 5–10 MB parts, each uploaded as a separate request. On interruption, we resume from the last successful chunk.
On iOS, we implement this with URLSession using Background Configuration (URLSessionConfiguration.background(withIdentifier:)): upload continues even after the app is backgrounded. On Android, we use WorkManager with an UploadWorker that receives setExpedited(OutOfQuotaPolicy.RUN_AS_NON_EXPEDITED_WORK_REQUEST) for background operation.
In React Native, we use react-native-background-upload or a custom native module. Standard fetch with FormData does not support background upload on iOS.
How to reduce user wait time
We generate a preview frame before upload: on iOS via AVAssetImageGenerator with generateCGImagesAsynchronously, on Android via MediaMetadataRetriever.getFrameAtTime(). The frame is compressed to JPEG 480p and uploaded separately — it appears instantly in the chat while the video is still uploading.
For playback in chat, we don't embed a full player in the cell — that kills scroll performance. Instead, we show a thumbnail with a play button; tapping opens AVPlayerViewController (iOS) or ExoPlayer (Android) overlaid on the chat. ExoPlayer with SimpleExoPlayer and DefaultMediaSourceFactory supports HLS, DASH, and progressive MP4 out of the box.
By comparison, Android's native VideoView gives less control over buffering and doesn't natively support HLS — ExoPlayer solves these issues, typically starting streams 2x faster.
Limitations and UX
The video length limit is not technical but a UX decision. We recommend 60–120 seconds for chats. If exceeded, we show a warning before transcoding starts, not after.
A progress bar showing speed (e.g., "2.3 MB/s") and remaining time is mandatory. A cancel button must stop both transcoding and upload, and delete temporary files.
| Stage |
Time (30s clip, 720p) |
| Transcoding (iPhone 14) |
3–5 s |
| Transcoding (iPhone SE 2) |
7–12 s |
| Upload 15 MB at 10 Mbit/s |
~12 s |
| Preview generation |
< 1 s |
| Problem |
Solution |
| Large file size |
Transcode to 720p H.264 |
| Connection drop |
Chunked upload with resume |
| Display delay |
Instant preview |
What is included in our work
We provide: API documentation, source code of the module, configured authorization schemes for S3/GCS, server deployment instructions, and training for your iOS/Android developers. We guarantee support during the commissioning phase. Order video upload implementation for your chat — our engineers will audit and propose the optimal solution.
Timelines
Basic implementation (selection, transcoding, chunked upload, preview, playback) — 3–5 days if your backend already supports multipart upload. Background upload with resume adds another 1–2 days. Cost is calculated individually after requirements analysis.
Contact us for a free project estimate. Our certified engineers perform integration reviews and provide optimization recommendations.
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.
