Crafting High-Quality 360° Viewer Apps for Smartphones

Smooth playback of 360° video on mobile devices is a tough technical challenge. The standard AVPlayer can't render spherical projections; you need a custom Metal pipeline that decodes frames in real time without stuttering. Whether it's equirectangular video at 4K/8K or interactive virtual tours with hotspots, we deliver solutions for iOS and Android that go beyond simple static photos.

Technical Challenges We Solve

Decoding 360° Video on iOS

360° video in equirectangular format on iOS is decoded via AVPlayer with AVPlayerLayer, but AVPlayerLayer renders only in 2D. For spherical projection you need AVPlayerItemVideoOutput combined with Metal or SceneKit. According to Apple's documentation, AVPlayerItemVideoOutput.copyPixelBuffer(forItemTime:itemTimeForDisplay:) blocks the calling thread during frame decoding. On an iPhone 12, decoding 4K H.265 takes 8–15 ms — half the frame budget at 60 fps. Calling it on a CADisplayLink callback on the main thread causes visible stutter.

The correct approach: use CADisplayLink only to trigger the Metal render pass, and perform the CVPixelBuffer copy on a separate DispatchQueue(qos: .userInteractive). The result is passed to Metal via CVMetalTextureCacheCreateTextureFromImage.

let displayLink = CADisplayLink(target: self, selector: #selector(renderFrame))
displayLink.preferredFrameRateRange = CAFrameRateRange(minimum: 60, maximum: 120, preferred: 120)

@objc func renderFrame() {
    videoDecodeQueue.async { [weak self] in
        guard let pixelBuffer = self?.videoOutput.copyPixelBuffer(
            forItemTime: self!.playerItem.currentTime(),
            itemTimeForDisplay: nil
        ) else { return }
        self?.metalRenderer.render(pixelBuffer: pixelBuffer)
    }
}

This approach guarantees smooth rendering even on older devices. For Android, a similar solution uses TextureView + MediaCodec with a surface-level OpenGL call. Our custom Metal pipeline delivers 2× smoother playback than standard AVPlayer, and tiled panoramas use 4× less memory than single-image solutions.

Tiled Panoramas for Virtual Tours

For high-quality static panoramas (hotels, real estate, museums), we use a tiled approach instead of a single image: multiple levels of detail split into a grid. As you zoom in (decrease FOV), higher-resolution tiles are loaded.

The standard format is Krpano tile or Marzipano. For mobile rendering we use a custom Metal/OpenGL ES pipeline or PanoramaGL (Android). Tiles are loaded via URLSession with priorities: first the visible sphere quadrant, then the four neighboring tiles (prefetch).

An LRU cache for tiles is mandatory. Without it, navigating a virtual tour (10+ locations × 6 cube faces × 4 levels of detail) can cause memory to grow to 800 MB within 15 minutes. Our optimization reduces that to 120 MB.

Hotspots and Interactivity

A hotspot is a point in 3D sphere space that, when rendered, becomes a 2D element on screen (icon, tooltip, transition button). Conversion from spherical coordinates (yaw/pitch) to screen coordinates:

func sphericalToScreen(yaw: Float, pitch: Float,
                       cameraYaw: Float, cameraPitch: Float,
                       fov: Float, screenSize: CGSize) -> CGPoint? {
    // Matrix transformation: spherical -> cartesian -> camera projection -> NDC -> screen
    let direction = SIMD3<Float>(
        cos(pitch) * sin(yaw),
        sin(pitch),
        cos(pitch) * cos(yaw)
    )
    // ... view matrix × projection matrix → clip space → viewport
}

If dot(direction, cameraForward) < 0 — the hotspot is behind the camera, skip rendering.

Animation for hotspot appearance when entering FOV — fade-in via CABasicAnimation, not SwiftUI animation (SwiftUI overlay above Metal SCNView adds 2–3 ms layout pass per frame). We use a custom render pipeline that minimizes overhead.

Gyroscope and Compass

CMDeviceMotion via CMMotionManager provides device orientation quaternion at up to 100 Hz. We convert to Euler angles for the scene camera and apply a Kalman filter to smooth jitter. Without filtering, gyroscope drift on older devices (~0.3° per second) can misalign "north" by 15° after 5 minutes.

For north at startup, we use CLLocationManager.heading to bind the initial yaw to magnetic/true north. This guarantees accurate tracking on all iPhones and iPads with a gyroscope.

How We Work

Process

1. Analysis and requirements gathering: Discuss goals, content types, target devices.
2. Architecture design of the render pipeline (Metal/OpenGL ES).
3. Development of tile loading and caching modules.
4. Integration of gyroscope, compass, and touch controls.
5. Implementation of hotspots with animations and transitions.
6. Performance optimization for target devices.
7. Testing on real devices and simulators.
8. Preparation of documentation and instructions.
9. Support during App Store and Google Play publishing.
10. 3 months of technical support after delivery.

What's Included

• Detailed technical documentation and architecture diagram of the render pipeline
• Access to the repository with code and build tools
• Instructions for backend integration and store publishing
• 3 months of technical support

Timeline Estimates

A basic video panorama project starts at $5,000; a full virtual tour with 10 locations and hotspots is typically $15,000–$25,000. Cost is determined individually after requirements analysis. We will evaluate your project within 2 business days. Contact us for a project assessment — we will analyze your requirements and propose the best solution. Get a consultation to discuss the details.

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.