Integrating Your App with Siri Event Suggestions

At a glance

Project structure

Source bundle/
├── Siri Event Suggestions/
│   ├── Siri Event Suggestions/
│   │   ├── AppDelegate.swift
│   │   ├── View Controllers/
│   │   │   ├── ReservationContainersTableViewController.swift
│   │   │   ├── ReservationDetailsViewController.swift
│   │   │   └── ReservationsTableViewController.swift
│   │   ├── Server.swift
│   │   ├── HelperExtensions.swift
│   │   ├── Base.lproj/
│   │   │   ├── LaunchScreen.storyboard
│   │   │   └── Main.storyboard
│   │   └── Info.plist
│   └── Siri Event Suggestions.xcodeproj/
│       ├── .xcodesamplecode.plist
│       └── project.pbxproj
└── Configuration/
    └── SampleCode.xcconfig

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["ReservationContainersTableViewController"]
    N3["Intents APIs"]
    N1 --> N2
    N2 --> N3

Reference code

Siri Event Suggestions/Siri Event Suggestions/AppDelegate.swift:16 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    var window: UIWindow?

    func application(_ application: UIApplication,
                     continue userActivity: NSUserActivity,
                     restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {

        // Your app was launched with the INGetReservationDetailsIntent intent. You should reconfigure your UI
        // to display the reservations specified in the intent.
        if userActivity.activityType == "INGetReservationDetailsIntent" {
            let notification = Notification(name: .showReservation, object: userActivity, userInfo: nil)
            let notificationCenter = NotificationCenter.default
            notificationCenter.post(notification)
            return true
        }
        // Your app was launched with the custom "com.example.apple-samplecode.Siri-Event-Suggestions.check-in" activity type
        // that is specified for the check-in action. You should reconfigure your UI to start the check-in flow.
        else if userActivity.activityType == "com.example.apple-samplecode.Siri-Event-Suggestions.check-in" {
            let notification = Notification(name: .startReservationCheckIn, object: userActivity, userInfo: nil)
            let notificationCenter = NotificationCenter.default
            notificationCenter.post(notification)
            return true
        }
        return false
    }
}

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-- Notification : showReservation
    AppDelegate o-- Notification : startReservationCheckIn
    AppDelegate o-- UIWindow : window
    ReservationContainersTableViewController o-- NSObjectProtocol : showReservationNotificationToken

Ownership evidence

Siri Event Suggestions/Siri Event Suggestions/AppDelegate.swift:12 — stored dependency or nearest verified ownership anchor

extension Notification.Name {
    static let showReservation = Notification.Name("ShowReservation")
    static let startReservationCheckIn = Notification.Name("StartReservationCheckIn")
}

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

Siri Event Suggestions/Siri Event Suggestions/AppDelegate.swift:17 — representative type boundary

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    var window: UIWindow?
    // ...
}

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

Access control

Reference code

Siri Event Suggestions/Siri Event Suggestions/HelperExtensions.swift:12 — representative boundary

    open override func present(
        // ...
        completion: (() -> Void)? = nil) {
        // ...
    }

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: ReservationContainersTableViewController, ReservationDetailsViewController, ReservationsTableViewController; Delegate: AppDelegate.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, viewDidLoad, buildTable, viewDidAppear, didPressClearButton, tableView, updateReservations, setupNotifications.
• Files: Siri Event Suggestions/Siri Event Suggestions/AppDelegate.swift, Siri Event Suggestions/Siri Event Suggestions/View Controllers/ReservationContainersTableViewController.swift, Siri Event Suggestions/Siri Event Suggestions/View Controllers/ReservationDetailsViewController.swift, Siri Event Suggestions/Siri Event Suggestions/View Controllers/ReservationsTableViewController.swift, Siri Event Suggestions/Siri Event Suggestions/Server.swift.

Architecture takeaways

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