Providing Multiple Complications

At a glance

Project structure

Source bundle/
├── Coffee Tracker WatchKit Extension/
│   ├── CoffeeTrackerApp.swift
│   ├── CoffeeTrackerView.swift
│   ├── ComplicationController.swift
│   ├── ContentView.swift
│   ├── DrinkListView.swift
│   ├── HostingController.swift
│   ├── CoffeeData.swift
│   ├── Drink.swift
│   ├── DrinkType.swift
│   └── Info.plist
├── Coffee Tracker WatchKit App/
│   └── Info.plist
└── Coffee Tracker.xcodeproj/
    └── .xcodesamplecode.plist

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 5 project/configuration file(s) and 10 source declaration(s).

Overall architecture

flowchart LR
    N1["CoffeeTrackerApp"]
    N2["ContentView"]
    N3["ClockKit APIs"]
    N1 --> N2
    N2 --> N3

Reference code

Coffee Tracker WatchKit Extension/CoffeeTrackerApp.swift:10 — architecture anchor

@main
struct CoffeeTrackerApp: App {
    // ...
}

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

Ownership and state

classDiagram
    CoffeeTrackerView o-- CoffeeData : coffeeData
    Complication *-- String : identifier
    Complication *-- String : displayName
    Complication *-- Complication : caffeine

Ownership evidence

Coffee Tracker WatchKit Extension/CoffeeTrackerView.swift:14 — stored dependency or nearest verified ownership anchor

struct CoffeeTrackerView: View {
    // ...
    @EnvironmentObject var coffeeData: CoffeeData
    // ...
}

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

Coffee Tracker WatchKit Extension/CoffeeTrackerApp.swift:11 — representative type boundary

struct CoffeeTrackerApp: App {
    // ...
}

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

Access control

Reference code

Coffee Tracker WatchKit Extension/CoffeeData.swift:33 — representative boundary

class CoffeeData: ObservableObject {
    // ...
    private var background = DispatchQueue(label: "Background Queue",
    qos: .userInitiated)
    // ...
}

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: CoffeeTrackerApp; Controller: ComplicationController, HostingController; View: CoffeeTrackerView, ContentView, DrinkListView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: colorForCaffeineDose, colorForDailyDrinkCount, getTimelineEndDate, getPrivacyBehavior, getComplicationDescriptors, getCurrentTimelineEntry, getTimelineEntries, getLocalizableSampleTemplate.
• Files: Coffee Tracker WatchKit Extension/CoffeeTrackerApp.swift, Coffee Tracker WatchKit Extension/CoffeeTrackerView.swift, Coffee Tracker WatchKit Extension/ComplicationController.swift, Coffee Tracker WatchKit Extension/ContentView.swift, Coffee Tracker WatchKit Extension/DrinkListView.swift, Coffee Tracker WatchKit Extension/HostingController.swift.

Architecture takeaways

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