Interacting with App Clip Codes in AR

At a glance

Project structure

Source bundle/
└── ARKitAppClipCodesSample/
    ├── SharedAssets/
    │   ├── AppDelegate.swift
    │   ├── AppClipCodeCoachingOverlayView.swift
    │   ├── SceneDelegate.swift
    │   ├── ViewController.swift
    │   ├── CachingWebLoader.swift
    │   ├── Utilities.swift
    │   ├── ViewController+ProductKeyProcessing.swift
    │   └── OverlayLabel.swift
    ├── ARAppClip/
    │   ├── ARAppClip.entitlements
    │   └── Info.plist
    ├── ARParentApp/
    │   └── Info.plist
    └── ARSeedShop.xcodeproj/
        └── .xcodesamplecode.plist

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 8 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["ViewController"]
    N3["CachingWebLoader"]
    N4["UIKit / ARKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

ARKitAppClipCodesSample/SharedAssets/AppDelegate.swift:10 — architecture anchor

@main
class AppDelegate: UIResponder, UIApplicationDelegate {

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

    // MARK: UISceneSession Lifecycle
    func application(
        _ application: UIApplication,
        configurationForConnecting connectingSceneSession: UISceneSession,
        options: UIScene.ConnectionOptions
    ) -> UISceneConfiguration {
        // Called when a new scene session is being created.
        // Use this method to select a configuration to create the new scene with.
        return UISceneConfiguration(name: "Default Configuration", sessionRole: connectingSceneSession.role)
    }
}

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 App Clips.

Ownership and state

classDiagram
    SceneDelegate o-- UIWindow : window
    SceneDelegate *-- URL : appClipCodeURL
    ViewController *-- ARView : arView
    ViewController o-- AppClipCodeCoachingOverlayView : appClipCodeCoachingOverlay

Ownership evidence

ARKitAppClipCodesSample/SharedAssets/SceneDelegate.swift:12 — stored dependency or nearest verified ownership anchor

class SceneDelegate: UIResponder, UIWindowSceneDelegate {
    // ...
    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

ARKitAppClipCodesSample/SharedAssets/AppClipCodeCoachingOverlayView.swift:32 — representative execution boundary

        DispatchQueue.main.async { [weak self] in
            UIView.animate(withDuration: 0.25, delay: 0, options: [.beginFromCurrentState], animations: { [weak self] in
                self?.alpha = hide ? 0 : 1
            })
        }

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

ARKitAppClipCodesSample/SharedAssets/AppDelegate.swift:11 — representative type boundary

@main
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
        return true
    // ...
}

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

Access control

Reference code

ARKitAppClipCodesSample/SharedAssets/CachingWebLoader.swift:16 — representative boundary

class CachingWebLoader: NSObject, URLSessionDelegate, URLSessionTaskDelegate, URLSessionDownloadDelegate {
    // ...
    public static let shared = CachingWebLoader()
    // ...
}

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: Controller: ViewController; Delegate: AppDelegate, SceneDelegate; Loader: CachingWebLoader; View: AppClipCodeCoachingOverlayView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, setCoachingViewHidden, scene, viewDidLoad, session, displayUnsupportedDevicePrompt, initializeARView, runARSession.
• Files: ARKitAppClipCodesSample/SharedAssets/AppDelegate.swift, ARKitAppClipCodesSample/SharedAssets/AppClipCodeCoachingOverlayView.swift, ARKitAppClipCodesSample/SharedAssets/SceneDelegate.swift, ARKitAppClipCodesSample/SharedAssets/ViewController.swift, ARKitAppClipCodesSample/SharedAssets/CachingWebLoader.swift, ARKitAppClipCodesSample/SharedAssets/OverlayLabel.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, ARKit, RealityKit 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