Connecting a network driver

At a glance

Project structure

Source bundle/
├── NetworkingDriverKitSampleApp/
│   ├── NetworkingDriverKitSampleApp.swift
│   ├── DriverLoadingViewModel.swift
│   ├── DriverLoadingView.swift
│   ├── NetworkingDriverKitSampleApp.entitlements
│   └── NetworkingDriverKitSampleApp.plist
├── NetworkingDriverKitSample/
│   ├── NetworkingDriverKitSample.cpp
│   ├── NetworkingDriverKitDebug.h
│   ├── NetworkingDriverKitSample.entitlements
│   └── NetworkingDriverKitSample.plist
├── Configuration/
│   └── SampleCode.xcconfig
└── NetworkingDriverKitSample.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: C++, C/Objective-C header, Swift.
• The verified tree contains 7 project/configuration file(s) and 8 source declaration(s).

Overall architecture

flowchart LR
    N1["NetworkingDriverKitSampleApp"]
    N2["DriverLoadingView"]
    N3["DriverLoadingViewModel"]
    N4["DriverKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

NetworkingDriverKitSampleApp/NetworkingDriverKitSampleApp.swift:10 — architecture anchor

@main
struct NetworkingDriverKitSampleApp: App {
    var body: some Scene {
        WindowGroup {
            DriverLoadingView()
        }
    }
}

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 PCIDriverKit.

Ownership and state

classDiagram
    DriverLoadingViewModel o-- State : state
    DriverLoadingViewModel *-- String : dextIdentifier
    DriverLoadingView o-- DriverLoadingViewModel : viewModel

Ownership evidence

NetworkingDriverKitSampleApp/DriverLoadingViewModel.swift:76 — stored dependency or nearest verified ownership anchor

class DriverLoadingViewModel: NSObject {
    // ...
    @Published private var state: DriverLoadingStateMachine.State = .unloaded
    // ...
}

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

NetworkingDriverKitSampleApp/NetworkingDriverKitSampleApp.swift:11 — representative type boundary

struct NetworkingDriverKitSampleApp: App {
    var body: some Scene {
        WindowGroup {
            DriverLoadingView()
        }
    }
}

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

Access control

Reference code

NetworkingDriverKitSampleApp/DriverLoadingViewModel.swift:76 — representative boundary

class DriverLoadingViewModel: NSObject {
    // ...
    @Published private var state: DriverLoadingStateMachine.State = .unloaded
    // ...
}

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: NetworkingDriverKitSampleApp; View: DriverLoadingView; ViewModel: DriverLoadingViewModel.
• Protocols: no local protocol declaration in the scanned source.
• Methods: process, activateMyDext, activateExtension, deactivateExtension, request, requestNeedsUserApproval.
• Files: NetworkingDriverKitSampleApp/NetworkingDriverKitSampleApp.swift, NetworkingDriverKitSampleApp/DriverLoadingViewModel.swift, NetworkingDriverKitSampleApp/DriverLoadingView.swift.

Architecture takeaways

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