Mobile Messenger Development
Sending a message is not enough. Users expect it to arrive instantly, not get lost during network drops, and stay confidential. When building a messenger, common problems arise: message loss on unstable networks, data leaks over unencrypted channels, high battery consumption. We build messengers that solve these at the protocol level: WebSocket for real-time, E2EE on Signal Protocol, push-wake for battery savings. We'll assess your project within 2 business days.
How to Ensure Guaranteed Message Delivery?
WebSocket is the basic transport for real-time exchange. On mobile devices it doesn't persist forever: iOS kills background connections after 30 seconds of inactivity, Android Doze Mode closes them on idle. The right solution — WebSocket in foreground + push notifications (FCM/APNs) for wake-up. On receiving a push, the client reconnects and downloads new messages. This approach is 5 times more efficient than constant polling in terms of traffic.
Step-by-step delivery implementation
- Client generates a UUID and per-conversation sequence number, saves the message in local DB with status
sending.
- Sends the message over WebSocket with a callback for acknowledgment (
ack).
- Server confirms receipt — client changes status to
sent.
- On receiving push notification from server, client updates status to
delivered.
- If user reads — status
read.
A queue of unsent messages with automatic retry on connection restore.
// iOS — message delivery status management
enum MessageStatus: String, Codable {
case sending, sent, delivered, read, failed
}
class MessageStore {
func sendMessage(_ text: String, to conversationId: String) {
let msg = Message(
id: UUID().uuidString,
conversationId: conversationId,
body: text,
status: .sending,
timestamp: Date()
)
coreDataContext.insert(msg)
webSocketClient.send(msg) { [weak self] result in
switch result {
case .success: self?.updateStatus(msg.id, .sent)
case .failure: self?.updateStatus(msg.id, .failed)
}
}
}
}
Delivery approach comparison:
| Method |
Latency |
Battery drain |
Reliability |
| Polling (every 5s) |
5s |
High |
Medium |
| WebSocket |
<1s |
Medium |
High (with reconnect) |
| WebSocket + Push |
<1s |
Low |
Very high |
Why E2EE is a Basic Necessity?
E2EE is not an option, but a standard for a serious messenger. The industry standard — Signal Protocol includes Double Ratchet and X3DH. Implementation via official libsignal libraries (ports for iOS and Android). On registration, keys are generated (identity key, signed prekey, one-time prekeys), public parts are uploaded to the server. At conversation start, the client downloads the recipient's prekey, performs X3DH, and establishes an encrypted session. The server never sees plaintext.
Details of Signal Protocol Implementation
- Double Ratchet: each new session generates session keys, old ones are destroyed (perfect forward secrecy).
- X3DH: three Diffie-Hellman between identity/public/prekey to establish a shared key.
- The server side never has access to user private keys.
Encrypted backup of conversation history is stored with a key known only to the user (PIN/passphrase).
History Storage and Synchronization
SQLite via Room (Android) or CoreData/GRDB (iOS). DB schema: conversations, messages, attachments, reactions. Indexes on conversation_id + timestamp for fast feed loading. Full-text search — FTS5.
Pagination — reverse cursor: load the last N messages, on scroll up request next. Storing full history locally is impractical: limit to last N messages per conversation, rest lazy load from server. This saves up to 40% of traffic and local DB size.
Media and Battery Optimization
Photos, videos, documents — separate upload pipeline: presigned URL → upload to object storage → link in message. Thumbnail generated client-side and attached as base64 blurred preview (blurhash) — shows placeholder before original download.
Voice messages: recording via AVAudioRecorder (iOS, opus through AVAudioSession) or MediaRecorder (Android). Codec Opus 24 kbps. Waveform preview — sample amplitudes normalized to size.
Image compression before sending: UIGraphicsImageRenderer with max size 1280px and JPEG quality 0.8 — without this, each photo from a modern smartphone weighs 12+ MB. Reduces traffic by 10 times.
WebSocket keepalive — ping/pong every 25 seconds. APNs Priority 5 (low priority) for background notifications — doesn't wake screen; Priority 10 (high) — only for explicit incoming messages. This reduces battery consumption by 30%.
What Stages Does Mobile Messenger Development Include?
- Documentation: architecture, protocol, API design, ER diagrams.
- Source code: repository with code review and CI/CD.
- Builds: beta TestFlight/Google Play Console, CI builds for staging.
- Access: store accounts, push certificates, provisioning profiles.
- Training: workshop for the client's team on modification and support.
- Support: 3 months post-release bug fixing.
Group Chats and Channels
Group chat up to 1000 participants — standard fan-out. Broadcast channels with tens of thousands of subscribers — asynchronous delivery via queue (Kafka). For E2EE in groups we use Sender Keys (Signal/WhatsApp): one encrypted stream for all participants, not N individual sessions. Mentions (@username) in group — push only to the mentioned user or with configurable notifications.
Group approach comparison:
| Approach |
Participants |
E2EE |
Delivery latency |
| Fan-out (peer-to-peer) |
≤1000 |
Yes |
Low |
| Fan-out (main) |
≤1000 |
Yes |
Low |
| Broadcast (Kafka) |
>10 000 |
No |
Medium |
| Sender Keys |
≤1000 |
Yes |
Low (single stream) |
Timelines and Cost
MVP with chat, media, and push without E2EE — 6–8 weeks. Full messenger with E2EE, voice messages, groups, and backup — 3–5 months. Cost is calculated individually after requirements audit. Contact us for a detailed discussion of your project. Order development right now — we guarantee transparency at every stage.
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.
