Connecting to a service with passkeys

At a glance

Project structure

Source bundle/
├── Shared/
│   ├── AppDelegate.swift
│   ├── AccountManager.swift
│   ├── SceneDelegate.swift
│   ├── SignInViewController.swift
│   ├── UserHomeViewController.swift
│   ├── Base.lproj/
│   │   ├── LaunchScreen.storyboard
│   │   └── Main.storyboard
│   ├── Info.plist
│   └── Shiny.entitlements
├── Configuration/
│   └── SampleCode.xcconfig
└── Shiny.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: Swift.
• The verified tree contains 7 project/configuration file(s) and 5 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["SignInViewController"]
    N3["AccountManager"]
    N4["AuthenticationServices APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Shared/AppDelegate.swift:10 — architecture anchor

@main
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
}

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

Ownership and state

classDiagram
    AppDelegate *-- AccountManager : accountManager
    AccountManager o-- Notification : UserSignedIn
    AccountManager o-- Notification : ModalSignInSheetCanceled
    AccountManager o-- ASPresentationAnchor : authenticationAnchor

Ownership evidence

Shared/AppDelegate.swift:12 — stored dependency or nearest verified ownership anchor

    let accountManager = AccountManager()

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        // The override point for customization after app launch.
        return true
    }

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

Shared/AppDelegate.swift:11 — representative type boundary

class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
}

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

Access control

Reference code

Shared/SignInViewController.swift:18 — representative boundary

class SignInViewController: UIViewController {
    // ...
    private var signInObserver: NSObjectProtocol?
    // ...
}

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: Controller: SignInViewController, UserHomeViewController; Delegate: AppDelegate, SceneDelegate; Manager: AccountManager.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, signInWith, beginAutoFillAssistedPasskeySignIn, signUpWith, authorizationController, presentationAnchor, didFinishSignIn, didCancelModalSheet.
• Files: Shared/AppDelegate.swift, Shared/AccountManager.swift, Shared/SceneDelegate.swift, Shared/SignInViewController.swift, Shared/UserHomeViewController.swift.

Architecture takeaways

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