Implementing a background delivery extension

At a glance

Project structure

Source bundle/
├── SpendingTracker/
│   ├── SpendingTracker/
│   │   ├── FinanceKitBackgroundDeliveryApp.swift
│   │   ├── ContentView.swift
│   │   ├── Info.plist
│   │   └── SpendingTracker.entitlements
│   ├── SpendingTrackerWidgetExtension/
│   │   └── SpendingWidget.swift
│   ├── SpendingTrackerBackgroundDeliveryExtension/
│   │   └── SpendingBackgroundDeliveryExtension.swift
│   ├── Shared/
│   │   ├── FinanceUtilities.swift
│   │   ├── Storage.swift
│   │   └── FormattingUtilities.swift
│   └── SpendingTracker.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 9 project/configuration file(s) and 11 source declaration(s).

Overall architecture

flowchart LR
    N1["FinanceKitBackgroundDeliveryApp"]
    N2["ContentView"]
    N3["TransactionModel"]
    N4["SpendingWidgetProvider"]
    N5["FinanceKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

SpendingTracker/SpendingTracker/FinanceKitBackgroundDeliveryApp.swift:10 — architecture anchor

@main
struct FinanceKitBackgroundDeliveryApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

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

Ownership and state

classDiagram
    SpendingWidget *-- String : kind
    SpendingEntry *-- Date : date
    SpendingEntry o-- Decimal : total
    SpendingWidgetView o-- SpendingEntry : entry

Ownership evidence

SpendingTracker/SpendingTrackerWidgetExtension/SpendingWidget.swift:13 — stored dependency or nearest verified ownership anchor

@main
struct SpendingWidget: Widget {
    let kind: String = "com.myapp.spending-widget"

    // ...
}

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

SpendingTracker/Shared/FinanceUtilities.swift:15 — representative execution boundary

    static func calculateWeeklySpendingTotal() async throws -> Decimal {
        // ...
        let accounts = try await FinanceStore.shared.accounts(query: AccountQuery())
        // ...
    }

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

SpendingTracker/SpendingTracker/FinanceKitBackgroundDeliveryApp.swift:11 — representative type boundary

@main
struct FinanceKitBackgroundDeliveryApp: App {
    // ...
            ContentView()
    // ...
}

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

Access control

Reference code

SpendingTracker/Shared/Storage.swift:12 — representative boundary

struct Storage {
    // This is the identifier of the app group in the project settings.
    private static var appGroupIdentifier = "group.com.example.apple-samplecode.FinanceKit-background-delivery"
    private static var weeklySpendingKey = "WeeklySpending"

    private let defaults: UserDefaults

    init() {
        guard let defaults = UserDefaults(suiteName: Self.appGroupIdentifier) else {
            fatalError("Couldn't initialize UserDefaults for app group")
        }

        self.defaults = defaults
    }

    var weeklySpending: Decimal {
        // Read the value as a `String` and convert it to a `Decimal` if it's not `nil`.
        if let amount = defaults.string(forKey: Self.weeklySpendingKey).flatMap({ Decimal(string: $0) }) {
            return amount
        } else {
            return 0
        }
    }

    func setWeeklySpending(_ amount: Decimal) {
        // Convert the `Decimal` value into a `String` before storing it.
        defaults.set(String(describing: amount), forKey: Self.weeklySpendingKey)
    }
}

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: FinanceKitBackgroundDeliveryApp; Model: TransactionModel; Provider: SpendingWidgetProvider; View: ContentView, SpendingWidgetView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: getSnapshot, getTimeline, placeholder, didReceiveData, willTerminate, updateView, updateTransactions, updateWeeklySpending.
• Files: SpendingTracker/SpendingTracker/FinanceKitBackgroundDeliveryApp.swift, SpendingTracker/SpendingTrackerWidgetExtension/SpendingWidget.swift, SpendingTracker/SpendingTrackerBackgroundDeliveryExtension/SpendingBackgroundDeliveryExtension.swift, SpendingTracker/SpendingTracker/ContentView.swift, SpendingTracker/Shared/FinanceUtilities.swift, SpendingTracker/Shared/Storage.swift.

Architecture takeaways

• FinanceKitBackgroundDeliveryApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches FinanceKit, SwiftUI, WidgetKit 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