We develop Stories mechanics — ephemeral content — in mobile apps for iOS, Android, and cross-platform. This is a nontrivial UI pattern: progress bars with 60 FPS animation, tap navigation, pause on hold, swipe-down to close, media preloading without delays, and a server-side 24-hour timer. A mistake in any element ruins user experience. Our experience: 10+ years in mobile development, over 50 delivered projects. We'll evaluate your project for free.
How We Implement Progress Bars and Navigation
Horizontal progress bars at the top — UIView with frame.width animation via CADisplayLink (iOS) or ValueAnimator (Android). CADisplayLink provides 60/120 FPS synchronization with the display — smooth animation. Using Timer.scheduledTimer is not recommended: it stutters, especially under load. Duration for one story — usually 5–7 seconds for photos, for video — clip length (but no more than 15 seconds). The video progress bar syncs with AVPlayer.currentTime() via addPeriodicTimeObserver, not with a system timer.
Navigation: tap right half of screen — next story, left half — previous. UITapGestureRecognizer checking location.x > bounds.width / 2. Hold — UILongPressGestureRecognizer with minimumPressDuration: 0.1: on .began pause animation and AVPlayer, on .ended — resume. Swipe-down to close — interactive dismiss via UIPanGestureRecognizer. Scaling and moving the screen with the gesture (transform), on release — either full dismiss or return (UIViewPropertyAnimator).
Why Media Preloading Is Critical
Delay when switching stories is the main UX bug. User taps — waits 1–2 seconds while the photo or video loads. Correct solution: preload the next 2–3 stories. For photos — SDWebImage.prefetchURLs() or Kingfisher ImagePrefetcher. For video — AVAsset.loadValuesAsynchronously(forKeys: ["playable"]) + AVPlayerItem created in advance, AVPlayer not started until display. On Android — Coil ImageLoader.enqueue(ImageRequest) for photo preloading, ExoPlayer with ConcatenatingMediaSource for video: add next item to queue, ExoPlayer preloads buffer. Cache preloaded resources in memory (not just on disk) — repeat viewing of a story within the same session must be instant.
Creating Stories: From Photo to Video
Photo — PHPickerViewController + optional editor (text, stickers). Text over image: UITextView over UIImageView, on save — combine in UIGraphicsImageRenderer. Stickers — UIView with UIPanGestureRecognizer + UIPinchGestureRecognizer + UIRotationGestureRecognizer.
Video — recording via AVCaptureSession directly in the stories camera (like Instagram/Snapchat) or selection from gallery. Recording with 15-second limit — AVCaptureMovieFileOutput.maxRecordedDuration. Hold button to record, release — stop. After creation — upload in background. Story appears in feed immediately with placeholder, replaced by real content after upload.
How the Expiration Timer Works
24-hour timer — server-side, not client. Client simply requests list of active stories. Server filters by created_at + 24h < now. On client, for already loaded stories from cache — check expiresAt on open. If expired — don't show cache, request server (or delete from local storage). Views — mark on server via separate API request after story display. Batch marks: not one request per view, accumulate over session and send on app background or every 30 seconds.
Typical Mistakes When Implementing Stories
| Mistake |
Consequence |
Solution |
Using Timer for progress bar |
Janky animation, desync with video |
CADisplayLink on iOS, ValueAnimator on Android |
| Loading media "on the fly" |
Delays when switching |
Preload next 2-3 stories |
| No in-memory cache |
Repeated downloads on return |
Cache in NSCache or LruCache |
Ignoring expiresAt on client |
Showing outdated stories |
Check time before display |
| Individual view requests |
Server load |
Batching every 30 seconds |
What's Included
- Documentation (API schemas, flow diagrams)
- Source code with comments
- Access to repository, App Store Connect / Google Play Console
- Integration with your backend (REST/GraphQL)
- Testing on real devices (iOS 15+, Android 10+)
- Post-release support for 1 month
Timeline and Cost
Story viewing with progress bars, preloading, navigation, and expiration timer — 3–4 days. Creation with camera, text, and stickers + upload — another 2–3 days. Cost is calculated individually after analyzing your project. Contact us for a consultation and preliminary estimate.
| Component |
Time (days) |
| Viewing mechanics (progress bars, gestures, timer) |
3-4 |
| Media preloading and caching |
2-3 |
| Story creation (camera, editor, upload) |
2-3 |
| Backend integration and testing |
2-3 |
| Total |
7-10 |
More details on stories mechanics can be found in the App Store Review Guidelines (Section 4.2 and 5.1) and Google Play documentation.
Our team — 10+ years of mobile development experience, guaranteeing quality and on-time delivery. Order stories development for your app — we'll evaluate the project 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.
