Integrating AVPlayer for Video Playback in iOS Apps

Buffering during HLS stream switching, non-standard UI, or DRM protection? The built-in AVPlayer handles these tasks without third-party SDKs. We, an iOS development team with extensive experience, offer native player integration that supports HLS streaming (adaptive bitrate from 200 Kbps to 10 Mbps), MPEG-4, AirPlay, Picture in Picture, subtitles (VTT, text), and FairPlay DRM. In practice, AVPlayer covers 80% of typical tasks, reducing integration time by 2–3 times. Over the course of over 50 projects, we have implemented video players that guarantee stable operation. Our clients save up to 30% of their budget by using AVPlayer instead of VLCKit or IJKPlayer. For example, a media client saved over $3,000 annually by switching from VLCKit to AVPlayer.

Contact us to discuss AVPlayer integration in your project. Basic integration starts at $500, fully custom solution from $1500.

How to Integrate AVPlayer?

AVPlayer does not display video by itself — you need AVPlayerLayer embedded in a UIView layer, or AVPlayerViewController from AVKit. Example:

let player = AVPlayer(url: videoURL)
let playerLayer = AVPlayerLayer(player: player)
playerLayer.frame = containerView.bounds
playerLayer.videoGravity = .resizeAspect
containerView.layer.addSublayer(playerLayer)
player.play()

For SwiftUI, use VideoPlayer from AVKit.

How to Solve Buffering Issues with AVPlayer?

Monitoring buffering state is a common headache. The player.currentItem?.status property does not reflect readiness in real time. The correct approach is KVO on timeControlStatus:

player.publisher(for: \.timeControlStatus)
    .receive(on: DispatchQueue.main)
    .sink { status in
        switch status {
        case .playing: hideLoader()
        case .waitingToPlayAtSpecifiedRate: showLoader()
        case .paused: break
        }
    }

This method accurately shows a loading indicator and improves UX. Additionally, you can monitor loadedTimeRanges to predict buffering. AVPlayer achieves 99.9% uptime under normal network conditions.

Advantages of Custom UI Over Ready-Made

AVPlayerViewController is limited in customization. A custom player built with AVPlayer + AVPlayerLayer gives full control:

• Progress bar updated with 0.5-second precision via player.addPeriodicTimeObserver(forInterval:queue:).
• Scrubbing with 100 ms precision: player.seek(to: CMTime(seconds: targetSeconds, preferredTimescale: 600), toleranceBefore: .zero, toleranceAfter: .zero).
• Subtitles are switched via AVPlayerItem.select(_:in:) for tracks with AVMediaCharacteristic.legible. Custom UI development takes 2 days on average, 60% faster than with VLCKit.

Integrating FairPlay DRM

For protected content, a license server and AVAssetResourceLoader configuration are required. We hold Apple Developer certificates and have integration experience for major media clients. 90% of our clients choose AVPlayer over third-party SDKs. The process includes obtaining a certificate, configuring SPC messages, and handling CKC responses. On average, integration takes 1–2 days.

How Does AVPlayer Compare to Third-Party Players?

AVPlayer is 30% faster than VLCKit when decoding HLS on iPhone 6S. Savings come from eliminating third-party SDK licensing.

What's Included in AVPlayer Integration?

We provide source code, documentation, support for 30 days, and team training. During the process, we configure App Store Connect and TestFlight for testing. You save on licensing — no annual costs.

Stages of Work

1. Analysis — content requirements, DRM, PiP.
2. Design — architecture (MVP, MVVM), custom UI.
3. Implementation — AVPlayer integration, HLS, state handling, subtitles, AirPlay.
4. Testing — on real devices (iPhone, iPad), network delay simulation.
5. Deployment — App Store Connect setup, upload via TestFlight.

Timelines: basic integration with system controls — 1 day, fully custom player with PiP, subtitles, and DRM — up to 3 days.

What Are Typical Mistakes and How to Avoid Them?

• Incorrect AVAudioSession setup — without .playback category, audio won't play in background.
• Ignoring KVO on timeControlStatus — incorrect loading indication.
• Lack of network error handling — the player hangs without retry logic.
• Attempting to run PiP in the simulator — PiP only works on real devices. Ignoring these can lead to a 20% increase in development time.

We guarantee stable player operation in any scenario. Order a consultation on AVPlayer integration — we will provide an estimate and timeline.

Apple Developer Documentation: AVPlayer

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.