Building peer-to-peer apps

At a glance

Project structure

Source bundle/
└── Wi-Fi Aware Sample/
    ├── Wi-FiAwareSampleApp.swift
    ├── Simulation/
    │   ├── SimulationEngine.swift
    │   ├── SimulationView.swift
    │   └── SimulationScene.swift
    ├── ContentView.swift
    ├── Networking/
    │   ├── ConnectionManager.swift
    │   ├── DeviceDiscoveryPairingView.swift
    │   ├── NetworkManager.swift
    │   └── WiFiAwareError.swift
    ├── PairedDevices/
    │   └── PairedDevicesView.swift
    └── Extensions/
        ├── SimulationEngine+Extensions.swift
        └── WiFiAware+Extensions.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 25 source declaration(s).

Overall architecture

flowchart LR
    N1["Wi-FiAwareSampleApp"]
    N2["ContentView"]
    N3["ConnectionManager"]
    N4["SimulationEngine"]
    N5["WiFiAware APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

Wi-Fi Aware Sample/Wi-FiAwareSampleApp.swift:14 — architecture anchor

@main
struct WiFiAwareSampleApp: 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 Wi-Fi Aware.

Ownership and state

classDiagram
    Wi_FiAwareSampleApp *-- Logger : logger
    SimulationEngine o-- Mode : mode
    SimulationEngine o-- SimulationScene : scene
    SimulationEngine o-- NetworkState : networkState

Ownership evidence

Wi-Fi Aware Sample/Wi-FiAwareSampleApp.swift:12 — stored dependency or nearest verified ownership anchor

let logger = Logger(subsystem: "com.example.apple-samplecode.Wi-FiAwareSample", category: "App")

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

Wi-Fi Aware Sample/Wi-FiAwareSampleApp.swift:15 — representative type boundary

struct WiFiAwareSampleApp: App {
    // ...
}

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

Access control

Reference code

Wi-Fi Aware Sample/Extensions/WiFiAware+Extensions.swift:14 — representative boundary

    public static var simulationService: WAPublishableService {
        allServices[simulationServiceName]!
    }

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: WiFiAwareSampleApp; Engine: SimulationEngine; Manager: ConnectionManager, NetworkManager; Scene: SimulationScene; View: ContentView, DeviceDiscoveryPairingView, PairedDevicesView, SimulationView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: setupEventHandler, startConnectionMonitor, setup, handleLocalEvent, handleConnectionEvent, handleNetworkEvent, run, stopConnection.
• Files: Wi-Fi Aware Sample/Simulation/SimulationEngine.swift, Wi-Fi Aware Sample/Simulation/SimulationView.swift, Wi-Fi Aware Sample/ContentView.swift, Wi-Fi Aware Sample/Networking/ConnectionManager.swift, Wi-Fi Aware Sample/Networking/DeviceDiscoveryPairingView.swift, Wi-Fi Aware Sample/Networking/NetworkManager.swift.

Architecture takeaways

• Wi-FiAwareSampleApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches WiFiAware, Network, SwiftUI, SpriteKit 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