Accelerating app interactions with App Intents

At a glance

Project structure

Source bundle/
└── AppIntentsSampleApp/
    ├── AppIntentsSampleApp.swift
    ├── Model/
    │   ├── ActivityTracker.swift
    │   ├── TrailCollection.swift
    │   ├── AccountManager.swift
    │   ├── NavigationModel.swift
    │   └── TrailDataManager.swift
    ├── App Intents/
    │   ├── Entities/
    │   │   └── LocationOptionsProvider.swift
    │   └── OpenTrail.swift
    └── Views/
        ├── ActiveActivityInfoView.swift
        ├── ContentView.swift
        ├── TrailDetailView.swift
        └── TrailInfoView.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 8 project/configuration file(s) and 42 source declaration(s).

Overall architecture

flowchart LR
    N1["AppIntentsSampleApp"]
    N2["ContentView"]
    N3["AccountManager"]
    N4["LocationOptionsProvider"]
    N5["AppIntents APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

AppIntentsSampleApp/AppIntentsSampleApp.swift:11 — architecture anchor

@main
struct AppIntentsSampleApp: App {
    // ...
    private var trailManager: TrailDataManager
    // ...
}

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 App Intents.

Ownership and state

classDiagram
    AppIntentsSampleApp o-- TrailDataManager : trailManager
    AppIntentsSampleApp o-- NavigationModel : sceneNavigationModel
    AppIntentsSampleApp o-- AccountManager : accountManager
    AppIntentsSampleApp o-- ActivityTracker : activityManager

Ownership evidence

AppIntentsSampleApp/AppIntentsSampleApp.swift:14 — stored dependency or nearest verified ownership anchor

@main
struct AppIntentsSampleApp: App {
    // ...
    private var trailManager: TrailDataManager
    // ...
}

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.

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

Reference code

AppIntentsSampleApp/App Intents/BuyDayPass.swift:16 — representative execution boundary

    @MainActor
    func perform() async throws -> some IntentResult & ProvidesDialog {
        // ...
            let passAmount = IntentCurrencyAmount(amount: 6.50, currencyCode: "USD")
        // ...
    }

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

AppIntentsSampleApp/Model/ActivityTracker.swift:257 — representative type boundary

@MainActor
private protocol ActivityTrackingActions {
    var isActivityTrackingAuthorized: Bool { get }
    // ...
}

The source explicitly defines local protocol relationships: ActivityTracker → ActivityTrackingActions, LiveWorkoutManager → ActivityTrackingActions.

Access control

Reference code

AppIntentsSampleApp/App Intents/Entities/ActivityStatisticsSummary+Transferable.swift:35 — representative boundary

#if canImport(UIKIt)
    private var formattedSummary: AttributedString {
        let distanceStyle = Measurement<UnitLength>.FormatStyle(width: .abbreviated, usage: .road)
        // ...
    }
#endif // canImport(UIKit)

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: AppIntentsSampleApp; Manager: AccountManager, LiveWorkoutManager, TrailDataManager; Model: NavigationModel; Provider: LocationOptionsProvider; Tracker: ActivityTracker; View: ActiveActivityInfoView, ContentView, TrailDetailView, TrailInfoView.
• Protocols: ActivityTrackingActions.
• Methods: requestActivityTrackingAuthorization, startNewActivity, pauseActivity, resumeActivity, endActivity, activityHistory, saveHistory, hash.
• Files: AppIntentsSampleApp/AppIntentsSampleApp.swift, AppIntentsSampleApp/Model/ActivityTracker.swift, AppIntentsSampleApp/Model/TrailCollection.swift, AppIntentsSampleApp/App Intents/Entities/LocationOptionsProvider.swift, AppIntentsSampleApp/Model/AccountManager.swift, AppIntentsSampleApp/Model/NavigationModel.swift.

Architecture takeaways

• AppIntentsSampleApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches AppIntents, SwiftUI, CoreLocation, HealthKit 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