Displaying essential information on a watch face

At a glance

Project structure

Source bundle/
└── Complications WatchKit Extension/
    ├── ContentView.swift
    ├── TemplateConfiguration.swift
    ├── VariantListView.swift
    ├── ComplicationController.swift
    ├── ExtensionDelegate.swift
    ├── HostingController.swift
    ├── Timeline.swift
    ├── GraphicBezel.swift
    ├── GraphicCircular.swift
    ├── GraphicCorner.swift
    ├── GraphicRectangle.swift
    └── Utilities.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 6 project/configuration file(s) and 12 source declaration(s).

Overall architecture

flowchart LR
    N1["ComplicationController"]
    N2["ClockKit APIs"]
    N1 --> N2

Reference code

Complications WatchKit Extension/ComplicationController.swift:11 — architecture anchor

class ComplicationController: NSObject, CLKComplicationDataSource {
    // ...
}

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
    ContentView o-- TemplateConfiguration : configuration
    ContentView o-- Isconfiguratondirty : isConfiguratonDirty
    FamilyRowView *-- String : familyName
    VariantListView o-- TemplateConfiguration : configuration

Ownership evidence

Complications WatchKit Extension/ContentView.swift:12 — stored dependency or nearest verified ownership anchor

struct ContentView: View {
    @EnvironmentObject var configuration: TemplateConfiguration
    // ...
}

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

Complications WatchKit Extension/ContentView.swift:11 — representative type boundary

struct ContentView: View {
    // ...
}

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

Access control

Reference code

Complications WatchKit Extension/ComplicationController.swift:60 — representative boundary

    private func nextDayEntries(for complication: CLKComplication, after date: Date, limit: Int) -> [CLKComplicationTimelineEntry] {
        // ...
    }

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: ComplicationController, HostingController; Delegate: ExtensionDelegate; View: ContentView, FamilyRowView, VariantListView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: refreshComplications, isConfigurationDirty, encode, save, getSupportedTimeTravelDirections, getTimelineEndDate, getPrivacyBehavior, getCurrentTimelineEntry.
• Files: Complications WatchKit Extension/ContentView.swift, Complications WatchKit Extension/TemplateConfiguration.swift, Complications WatchKit Extension/VariantListView.swift, Complications WatchKit Extension/ComplicationController.swift, Complications WatchKit Extension/ExtensionDelegate.swift, Complications WatchKit Extension/HostingController.swift.

Architecture takeaways

• ComplicationController is the main source-visible entry or composition anchor for this sample.
• Framework work reaches ClockKit, SwiftUI, WatchKit, 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.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation