Booking Rides with SiriKit

At a glance

Project structure

Source bundle/
├── RideBooker/
│   ├── AppDelegate.swift
│   └── Base.lproj/
│       ├── LaunchScreen.storyboard
│       └── Main.storyboard
├── RideExtension/
│   ├── GetRideStatusHandler.swift
│   ├── Handler.swift
│   ├── IntentHandler.swift
│   ├── ListRideOptionsHandler.swift
│   └── RequestRideIntent.swift
├── RideExtensionUI/
│   └── IntentViewController.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── RideBooker.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 10 project/configuration file(s) and 7 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["IntentViewController"]
    N3["GetRideStatusHandler"]
    N4["Intents / IntentsUI APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

RideBooker/AppDelegate.swift:10 — architecture anchor

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

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    IntentHandler *-- Array : intentHandlers
    ListRideOptionsHandler *-- Array : fareLineItems
    ListRideOptionsHandler *-- Array : rideOptions

Ownership evidence

RideBooker/AppDelegate.swift:13 — stored dependency or nearest verified ownership anchor

    var window: UIWindow?

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        // Override point for customization after application 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

RideExtension/Handler.swift:10 — representative type boundary

protocol Handler: AnyObject {
    
    func canHandle(_ intent: INIntent) -> Bool
    
}

The source explicitly defines local protocol relationships: GetRideStatusHandler → Handler, ListRideOptionsHandler → Handler, RequestRideIntentHandler → Handler.

Access control

Reference code

RideExtension/IntentHandler.swift:12 — representative boundary

    private let intentHandlers: [Handler] = [
        RequestRideIntentHandler(),
        ListRideOptionsHandler(),
        GetRideStatusHandler()
    ]

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: IntentViewController; Delegate: AppDelegate; Handler: GetRideStatusHandler, Handler, IntentHandler, ListRideOptionsHandler, RequestRideIntentHandler.
• Protocols: Handler.
• Methods: application, canHandle, handle, startSendingUpdates, stopSendingUpdates, handler, confirm, configure.
• Files: RideBooker/AppDelegate.swift, RideExtension/GetRideStatusHandler.swift, RideExtension/Handler.swift, RideExtension/IntentHandler.swift, RideExtension/ListRideOptionsHandler.swift, RideExtensionUI/IntentViewController.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches Intents, IntentsUI, 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.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation