Playing video content in a standard user interface

At a glance

Project structure

Source bundle/
├── Using AVKit in iOS/
│   ├── AppDelegate.swift
│   ├── PlayerViewControllerCoordinator.swift
│   ├── PlaybackController.swift
│   ├── VideoBrowserViewController.swift
│   ├── ViewController.swift
│   ├── VideoBrowserCell.swift
│   ├── DebugHUD.swift
│   ├── Video.swift
│   └── VideoBrowserFlowLayout.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── Using AVKit in iOS.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 7 project/configuration file(s) and 12 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["PlaybackController"]
    N3["PlayerViewControllerCoordinator"]
    N4["AVKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Using AVKit in iOS/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into AVKit.

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    PlayerViewControllerCoordinator o-- Video : video
    PlayerViewControllerCoordinator o-- PlayerViewControllerCoordinatorDelegate : delegate
    PlayerViewControllerCoordinator o-- Status : status

Ownership evidence

Using AVKit in iOS/AppDelegate.swift:13 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

No source-visible execution, scheduling, or synchronization boundary was found in the indexed source.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

Using AVKit in iOS/PlayerViewControllerCoordinator.swift:310 — representative type boundary

protocol PlayerViewControllerCoordinatorDelegate: AnyObject {
    // ...
        _ coordinator: PlayerViewControllerCoordinator,
        restoreUIForPIPStop completion: @escaping (Bool) -> Void
    // ...
}

The source explicitly defines local protocol relationships: VideoBrowserViewController → VideoBrowserCellDelegate, ViewController → PlayerViewControllerCoordinatorDelegate.

Access control

Reference code

Using AVKit in iOS/DebugHUD.swift:19 — representative boundary

    private lazy var label: UILabel = {
        let label = UILabel()
        // ...
    }()

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Main application flow

sequenceDiagram
    actor User
    participant Browser as Video browser
    participant Playback as PlaybackController
    participant Coord as Coordinator
    participant AVKit as AVPlayerViewController
    User->>Browser: Select video
    Browser->>Playback: present or embed index path
    Playback->>Playback: find or create coordinator
    Playback->>Coord: presentFullScreen or embedInline
    Coord->>AVKit: lazily create and attach player
    AVKit-->>Coord: delegate lifecycle events
    Coord-->>Browser: status-visible playback UI

Reference code

Using AVKit in iOS/PlaybackController.swift:49 — embed

    func embed(contentForIndexPath indexPath: IndexPath, in parentViewController: UIViewController, containerView: UIView) {
        coordinator(for: indexPath).embedInline(in: parentViewController, container: containerView)
    }

Naming conventions

• Types: Controller: PlaybackController, VideoBrowserViewController, ViewController; Coordinator: PlayerViewControllerCoordinator; Delegate: AppDelegate, PlayerViewControllerCoordinatorDelegate, VideoBrowserCellDelegate.
• Protocols: PlayerViewControllerCoordinatorDelegate, VideoBrowserCellDelegate.
• Methods: presentFullScreen, embedInline, restoreFullScreen, dismiss, removeFromParentIfNeeded, playerViewControllerWillStartPictureInPicture, playerViewController, playerViewControllerDidStopPictureInPicture.
• Files: Using AVKit in iOS/AppDelegate.swift, Using AVKit in iOS/PlayerViewControllerCoordinator.swift, Using AVKit in iOS/PlaybackController.swift, Using AVKit in iOS/VideoBrowserViewController.swift, Using AVKit in iOS/ViewController.swift, Using AVKit in iOS/VideoBrowserCell.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, AVKit, AVFoundation through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation