Working with Overlays and Parental Controls in tvOS

At a glance

Project structure

Source bundle/
├── TVAVPlayerViewControllerDemo/
│   ├── TVAVPlayerViewControllerDemo/
│   │   ├── AppDelegate.swift
│   │   ├── CustomInteractiveVideoOverlayViewController.swift
│   │   ├── MenuViewController.swift
│   │   ├── VideoPlaybackViewController.swift
│   │   ├── Base.lproj/
│   │   │   ├── CustomInteractiveVideoOverlay.xib
│   │   │   └── Main.storyboard
│   │   └── Info.plist
│   └── TVAVPlayerViewControllerDemo.xcodeproj/
│       ├── .xcodesamplecode.plist
│       └── project.pbxproj
└── Configuration/
    └── SampleCode.xcconfig

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 6 project/configuration file(s) and 4 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["MenuViewController"]
    N3["AVKit APIs"]
    N1 --> N2
    N2 --> N3

Reference code

TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        // Override point for customization after application launch.

        return true
    }

}

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
    CustomInteractiveVideoOverlay o-- UIStackView : stackView
    MenuViewController o-- VideoPlaybackViewController : videoPlaybackViewController
    MenuViewController o-- TVPosterView : firstPosterView

Ownership evidence

TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/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.

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

Reference code

TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/VideoPlaybackViewController.swift:32 — representative execution boundary

            DispatchQueue.main.async { // Avoid modifying an observed property from directly within an observer.
                let pendingItemStatus = object.pendingPlayerItem?.status
                // ...
            }

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

TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/AppDelegate.swift:11 — representative type boundary

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
    var window: UIWindow?
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/VideoPlaybackViewController.swift:88 — representative boundary

    private func metadataItem(_ identifier: AVMetadataIdentifier, stringValue value: String) -> AVMutableMetadataItem {
        let metadataItem = AVMutableMetadataItem()
        // ...
    }

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 Menu
    participant Playback as Playback controller
    participant Item as Pending player item
    participant Policy as Restriction authorization
    participant AVKit as AVPlayerViewController
    User->>Menu: Select poster
    Menu->>Playback: loadAndPlay metadata
    Playback->>Item: create item and external metadata
    Item-->>Playback: status readyToPlay via KVO
    Playback->>Policy: request authorization
    alt authorized
        Playback->>AVKit: attach queue player
        Playback->>AVKit: start playback
    else denied or failed
        Playback->>Playback: dismiss
    end

Reference code

TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/VideoPlaybackViewController.swift:29 — commonInit

    func commonInit() {
        playerItemStatusObservation = observe(\.pendingPlayerItem?.status) { (object, change) in
            DispatchQueue.main.async { // Avoid modifying an observed property from directly within an observer.
                let pendingItemStatus = object.pendingPlayerItem?.status
                if pendingItemStatus == AVPlayerItem.Status.readyToPlay {
                    if checkParentalControlsExplicitly {
                        object.pendingPlayerItem?.requestPlaybackRestrictionsAuthorization { (success, error) in
                            if success {
                                object.pendingPlayerItem = nil
                                object.playerViewController?.player = object.player
                                object.player?.rate = 1.0
                            } else {
                                _ = object._dismiss()
                            }
                        }
                    } else {
                        object.pendingPlayerItem = nil
                        object.playerViewController?.player = object.player
                        object.player?.rate = 1.0
                    }
                }
            }
        }
        currentItemErrorObservation = observe(\.playerViewController?.player?.currentItem?.error) { (object, change) in
            DispatchQueue.main.async {
                if object.playerViewController?.player?.currentItem?.error != nil {
                    _ = object._dismiss()
                }
            }
        }
    }

Naming conventions

• Types: Controller: MenuViewController, VideoPlaybackViewController; Delegate: AppDelegate.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, viewDidLoad, presentVideo, action, commonInit, metadataItem, metadataItemForMediaContentRating, loadNewPlayerViewController.
• Files: TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/AppDelegate.swift, TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/MenuViewController.swift, TVAVPlayerViewControllerDemo/TVAVPlayerViewControllerDemo/VideoPlaybackViewController.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, AVKit, TVUIKit 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.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation