Supporting Multiple Users in Your tvOS App

At a glance

Project structure

Source bundle/
└── MemoryGame/
    ├── MemoryGameApp.swift
    ├── GameView.swift
    ├── TileView.swift
    ├── ContentView.swift
    ├── CoreDataStore.swift
    ├── DebugCoreDataView.swift
    ├── DynamicFetchRequestView.swift
    ├── MainMenuView.swift
    ├── NewGameView.swift
    ├── ProminentHighScoreView.swift
    ├── SectionHeaderView.swift
    └── StandardHighScoreView.swift

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

Overall architecture

flowchart LR
    N1["MemoryGameApp"]
    N2["ContentView"]
    N3["CoreDataStore"]
    N4["SwiftUI / CoreData APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

MemoryGame/MemoryGameApp.swift:10 — architecture anchor

@main
struct MemoryGameApp: App {
    @StateObject private var store = CoreDataStore()

    var body: some Scene {
        WindowGroup {
            ContentView().environment(\.managedObjectContext, store.viewContext)
        }
    }
}

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 TV Services.

Ownership and state

classDiagram
    MemoryGameApp *-- CoreDataStore : store
    GameView o-- GameEntity : game
    TileView *-- String : sticker
    TileView o-- TileState : state

Ownership evidence

MemoryGame/MemoryGameApp.swift:12 — stored dependency or nearest verified ownership anchor

@main
struct MemoryGameApp: App {
    @StateObject private var store = CoreDataStore()
    // ...
}

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

MemoryGame/GameView.swift:84 — representative execution boundary

                    DispatchQueue.main.asyncAfter(deadline: .now() + 1.5) {
                        withAnimation(.spring()) { state = .none }
                    }

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

MemoryGame/MemoryGameApp.swift:11 — representative type boundary

@main
struct MemoryGameApp: App {
    @StateObject private var store = CoreDataStore()
    // ...
}

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

Access control

Reference code

MemoryGame/CoreDataStore.swift:12 — representative boundary

    private lazy var container: NSPersistentCloudKitContainer = {
        let container = NSPersistentCloudKitContainer(name: "MemoryGame")
        // ...
    }()

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: App: MemoryGameApp; Store: CoreDataStore; View: ContentView, DebugCoreDataView, DynamicFetchRequestView, GameView, MainMenuView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: cell, select, state, save, makePlayGameView, makeResetCurrentGamesView, resetCurrentGames.
• Files: MemoryGame/MemoryGameApp.swift, MemoryGame/GameView.swift, MemoryGame/TileView.swift, MemoryGame/ContentView.swift, MemoryGame/CoreDataStore.swift, MemoryGame/DebugCoreDataView.swift.

Architecture takeaways

• MemoryGameApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, CoreData 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