Building a guessing game for visionOS

At a glance

Project structure

Source bundle/
└── GuessTogether/
    ├── GuessTogetherApp.swift
    ├── Models/
    │   ├── GameModel.swift
    │   ├── PlayerModel.swift
    │   └── AppModel.swift
    ├── ImmersiveSpace/
    │   ├── PhraseDeckView.swift
    │   ├── PhraseDeckPodiumView.swift
    │   └── SeatScoresView.swift
    ├── Utilities/
    │   └── PhraseManager.swift
    ├── WindowViews/
    │   ├── GameScoreBoardView.swift
    │   ├── TeamSelectionView.swift
    │   └── WelcomeView.swift
    └── GroupActivity/
        └── SessionController.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 5 project/configuration file(s) and 37 source declaration(s).

Overall architecture

flowchart LR
    N1["GuessTogetherApp"]
    N2["SessionController"]
    N3["PhraseManager"]
    N4["GroupActivities APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

GuessTogether/GuessTogetherApp.swift:10 — architecture anchor

@main
struct GuessTogetherApp: App {
    // ...
}

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 Group Activities.

Ownership and state

classDiagram
    GuessTogetherApp *-- AppModel : appModel
    GameModel o-- ActivityStage : stage
    GameModel o-- Excludedcategories : excludedCategories
    GameModel *-- Array : turnHistory

Ownership evidence

GuessTogether/GuessTogetherApp.swift:12 — stored dependency or nearest verified ownership anchor

    @State var appModel = AppModel()

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

GuessTogether/GuessTogetherApp.swift:11 — representative type boundary

struct GuessTogetherApp: App {
    // ...
}

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

Access control

Reference code

GuessTogether/GroupActivity/SessionController+RemoteParticipantSynchronization.swift:46 — representative boundary

    private func observeRemoteGameModelUpdates() {
        // ...
    }

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: GuessTogetherApp; Controller: SessionController; Manager: PhraseManager; Model: AppModel, GameModel, PlayerModel; Store: GameSyncStore; View: ActivitySharingView, CategorySelectionView, MainView, PhraseCardView, PhraseDeckPodiumView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: randomPhrase, teamHasPlayers, playersOnTeam.
• Files: GuessTogether/GuessTogetherApp.swift, GuessTogether/Models/GameModel.swift, GuessTogether/ImmersiveSpace/PhraseDeckView.swift, GuessTogether/Models/PlayerModel.swift, GuessTogether/Models/AppModel.swift, GuessTogether/Utilities/PhraseManager.swift.

Architecture takeaways

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