Implementing Wallet Extensions

At a glance

Project structure

Source bundle/
├── ImplementingWalletExtensionsSampleApp/
│   ├── ImplementingWalletExtensionsSampleApp.swift
│   └── LoginView.swift
├── WUIExt/
│   ├── WUIExtView.swift
│   └── WUIExtHandler.swift
├── ImplementingWalletExtensionsSampleAppTests/
│   ├── TestModels.swift
│   ├── WNonUIExtHandler.swift
│   ├── WatchConnectivitySession.swift
│   └── WNonUIExtHandlerTests.swift
└── WNonUIExt/
    ├── Models/
    │   ├── WatchConnectivitySession.swift
    │   ├── AppGroupManager.swift
    │   └── MockClasses.swift
    └── WNonUIExtHandler.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 9 project/configuration file(s) and 20 source declaration(s).

Overall architecture

flowchart LR
    N1["ImplementingWalletExtensionsSampleApp"]
    N2["LoginView"]
    N3["MockWatchConnectivitySession"]
    N4["PassKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

ImplementingWalletExtensionsSampleApp/ImplementingWalletExtensionsSampleApp.swift:10 — architecture anchor

@main
struct ImplementingWalletExtensionsSampleApp: App {
    var body: some Scene {
        WindowGroup {
            LoginView()
        }
    }
}

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 PassKit (Apple Pay and Wallet).

Ownership and state

classDiagram
    LoginView *-- String : username
    LoginView *-- String : password
    WUIExtView o-- Callback : completionHandler
    WUIExtView *-- String : username

Ownership evidence

ImplementingWalletExtensionsSampleApp/LoginView.swift:11 — stored dependency or nearest verified ownership anchor

struct LoginView: View {
    @State var username: String = ""
    @State var password: String = ""

    // ...
}

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.

No source-visible execution, scheduling, or synchronization boundary was found in the indexed source.

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

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

ImplementingWalletExtensionsSampleApp/ImplementingWalletExtensionsSampleApp.swift:11 — representative type boundary

@main
struct ImplementingWalletExtensionsSampleApp: App {
    // ...
            LoginView()
    // ...
}

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

Access control

Reference code

ImplementingWalletExtensionsSampleAppTests/TestModels.swift:67 — representative boundary

class MockUserDefaults: UserDefaults {
    private var passCredentialsData: [String: ProvisioningCredential] = [:]
    // ...
}

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: ImplementingWalletExtensionsSampleApp; Handler: WNonUIExtHandler, WUIExtHandler; Session: MockWatchConnectivitySession, WatchConnectivitySession; View: LoginView, WUIExtView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: handleLogin, handleBiometricLogin, requestPaymentPassData, data, bool, addPassCredentialJson, passes, isEqual.
• Files: ImplementingWalletExtensionsSampleApp/ImplementingWalletExtensionsSampleApp.swift, ImplementingWalletExtensionsSampleApp/LoginView.swift, WUIExt/WUIExtView.swift, WNonUIExt/Models/WatchConnectivitySession.swift, ImplementingWalletExtensionsSampleAppTests/WNonUIExtHandler.swift, ImplementingWalletExtensionsSampleAppTests/WatchConnectivitySession.swift.

Architecture takeaways

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