Authoring Apple Immersive Video

At a glance

Project structure

Source bundle/
├── ImmersiveMediaSupport Authoring/
│   ├── CreateAIVU.swift
│   └── CreateAIVUWriter.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── ImmersiveMediaSupport Authoring.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 3 project/configuration file(s) and 3 source declaration(s).

Overall architecture

flowchart LR
    N1["CreateAIVU"]
    N2["ImmersiveMediaSupport APIs"]
    N1 --> N2

Reference code

ImmersiveMediaSupport Authoring/CreateAIVU.swift:14 — architecture anchor

@main
struct CreateAIVU: AsyncParsableCommand {
    // ...
}

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 Immersive Media Support.

Ownership and state

classDiagram
    CreateAIVU *-- String : inputFile
    CreateAIVU *-- String : aimeFile
    CreateAIVU *-- String : usdzFile
    CreateAIVU *-- String : maskFile

Ownership evidence

ImmersiveMediaSupport Authoring/CreateAIVU.swift:17 — stored dependency or nearest verified ownership anchor

    var inputFile: String
    
    @Option(name: [.short, .customLong("aime")], help: "AIME file with the correct camera calibrations for the provided input file.")
    var aimeFile: String?
    
    @Option(name: [.short, .customLong("usdz")],
            help: "Optional USDZ file for camera calibration to use instead of an AIME file. (Must be used with --mask option).")

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.

Class and protocol design

ImmersiveMediaSupport Authoring/CreateAIVU.swift:15 — representative type boundary

struct CreateAIVU: AsyncParsableCommand {
    // ...
}

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

Access control

Reference code

ImmersiveMediaSupport Authoring/CreateAIVU.swift:33 — representative boundary

@main
struct CreateAIVU: AsyncParsableCommand {
    // ...
}

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

Naming conventions

• Types: feature-specific names rather than reusable layer suffixes.
• Protocols: no local protocol declaration in the scanned source.
• Methods: run, createVenueDescriptor, createPresentationDescriptor, create, getMetadataItem, getTimedMetadataGroup, getOutputProvider, getMetadataFormatDescription.
• Files: ImmersiveMediaSupport Authoring/CreateAIVU.swift, ImmersiveMediaSupport Authoring/CreateAIVUWriter.swift.

Architecture takeaways

• CreateAIVU is the main source-visible entry or composition anchor for this sample.
• Framework work reaches AVFoundation, ImmersiveMediaSupport, ArgumentParser 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