Developing Reels (Short Videos) in a Mobile App

Client complains: the vertical video feed lags on iPhone 8 with old iOS — switching between clips takes a second, audio is out of sync, and fast swipes crash the app due to memory pressure. Sound familiar? We solve it: we implement smooth paging scroll using a shared player, preload videos three positions ahead, and cache AVPlayerItem for five neighboring clips — all delivering stable 60 fps even on devices with 2 GB RAM.

Vertical video feeds are technically one of the most challenging UI patterns: they require audio-video synchronization, minimized scroll latency, and proper memory management. Our team has built over 50 video feed projects using Swift 5.9+, Kotlin 1.9+, Combine, and Coroutines. Our engineers are Apple and Google certified, with deep experience in App Store Review Guidelines (Section 4.2, 5.1) and Google Play Console. The key solution: using a single instance of AVPlayer (iOS) or ExoPlayer (Android) reassigned across cells. This eliminates player initialization delays and reduces GPU load. Preloading AVPlayerItem three videos ahead cuts switch time to 80 ms. Contact us for a free estimate.

Vertical Paging Scroll

The foundation of Reels is UICollectionView with UICollectionViewCompositionalLayout + UICollectionLayoutSectionOrthogonalScrollingBehavior.paging (iOS) or RecyclerView with PagerSnapHelper (Android). Each cell fills the entire screen (bounds.size).

On iOS, paging scroll via UICollectionView with isPagingEnabled = true works but lacks control over deceleration. Better: a custom UICollectionViewFlowLayout overriding targetContentOffset(forProposedContentOffset:withScrollingVelocity:) that snaps to the nearest video with desired animation.

Velocity-based switching: a fast swipe switches to the next Reel regardless of scroll distance. sqrt(velocity.x² + velocity.y²) > threshold → snap to the next cell.

How to Switch Videos Without Delay?

The critical decision: one shared AVPlayer with AVPlayerItem reassignment during scroll. In scrollViewDidEndDecelerating, we take the player from the previous cell and assign it to the current one. AVPlayerLayer.player = avPlayer — instant. The player is never recreated — switching occurs without pauses.

On Android — one ExoPlayer for the entire activity/fragment. PlayerView.player = exoPlayer reassigns. We use MediaItem with preload: exoPlayer.addMediaItem(nextMediaItem) for the next video — ExoPlayer starts buffering before actual switch. ExoPlayer with preloading is 4x faster than standard MediaPlayer.

Preloading: keep in memory AVPlayerItem for current, next, and previous videos. Creating AVPlayerItem from URL takes time — we do it at scroll start toward a neighbor cell, not on completion.

func collectionView(_ collectionView: UICollectionView,
                    willDisplay cell: UICollectionViewCell, forItemAt indexPath: IndexPath) {
    // Preload AVPlayerItem for this index
    let item = AVPlayerItem(url: videoURLs[indexPath.row])
    playerItemCache[indexPath.row] = item
}

According to Apple AVFoundation Guide, this approach minimizes delays.

How to Implement Multi-Segment Recording?

The camera for recording Reels is a custom AVCaptureSession. AVCaptureVideoPreviewLayer shows live preview fullscreen. Recording via AVCaptureMovieFileOutput with limit: maxRecordedDuration = CMTime(seconds: 60, preferredTimescale: 600).

Multi-segment recording (several short clips into one Reel) — create a separate AVAsset for each take, then merge via AVMutableComposition. AVMutableCompositionTrack.insertTimeRange() inserts segments sequentially.

Real-time filters — Core Image with CIFilter applied to CMSampleBuffer in delegate method captureOutput(_:didOutput:from:). Render via CIContext with Metal (CIContext(mtlDevice: MTLCreateSystemDefaultDevice()!)). OpenGL for this task is outdated with worse performance.

Sound, Text, Effects

Audio track — user's music from media library via MPMediaPickerController (iOS) or ACTION_PICK with MediaStore.Audio (Android), or in-app catalog tracks. Lay audio over video using AVMutableComposition with two tracks: video + audio.

Text overlay — not UILabel on top of UIImageView, but baked into video via AVVideoCompositionCoreAnimationTool with CATextLayer. This ensures correct text rendering during export and publication.

Feed Performance

UICollectionView.prefetchDataSource on iOS — request metadata of next 3 videos during scroll. RecyclerView.setRecycledViewPool() on Android — common view pool for reuse, reducing inflate operations.

Memory: store decoded AVPlayerItem for at most 5 neighboring videos. On scroll further, release AVPlayerItem.asset explicitly. Without this, watching 20+ Reels causes memory growth to 300–500 MB and iOS fires memory warning. Our engineers are Apple and Google certified, guaranteeing smooth operation even on devices with 2 GB RAM.

What's Included

• Architecture and API documentation.
• Source code with comments.
• CI/CD setup and store access (App Store Connect, Google Play Console).
• Client team training (2–3 sessions).
• 30 days of post-release support.

Timeline and Cost

Viewing feed with auto-play, preloading, and paging — 1–2 weeks. Full cycle (recording, editing, filters, publishing, feed) — 3–6 weeks. Cost is calculated individually based on integration complexity and required features. Contact us for a project estimate.

Step-by-Step Guide: How to Implement a Shared Player

1. Create a single AVPlayer / ExoPlayer in your Activity/ViewController.
2. In each cell, use playerLayer.player = player / PlayerView.player = player.
3. In scrollViewDidEndDecelerating, assign the player to the now-visible cell.
4. For preloading, implement prefetchDataSource (iOS) or addMediaItem (Android).
5. Test on devices with 2 GB RAM.

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).

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

1. Define requirements: target latency, number of concurrent users, need for P2P.
2. Choose protocol and stack: WebRTC for video calls, RTMP/HLSLive for broadcasting.
3. Set up signaling (SIP, WebSocket, MQTT) and TURN server.
4. Implement publishing/viewing via native API or cross-platform plugin.
5. Test on real devices with different cameras and network conditions.
6. Optimize bitrate and resolution based on bandwidth.

What is Included in the Work

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.