Building a productivity app for Apple Watch

At a glance

Project structure

Source bundle/
└── WatchTaskListSample/
    ├── WatchTaskListSampleApp.swift
    ├── Models/
    │   ├── ItemListModel.swift
    │   ├── Color+AppColors.swift
    │   ├── ChartData.swift
    │   ├── DateFormatStyle.swift
    │   ├── IntegerFormatStyle.swift
    │   └── ListItem.swift
    ├── Views/
    │   ├── ContentView.swift
    │   ├── AddItemLink.swift
    │   ├── ItemDetail.swift
    │   └── ItemList.swift
    └── ComplicationController.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 3 project/configuration file(s) and 14 source declaration(s).

Overall architecture

flowchart LR
    N1["WatchTaskListSampleApp"]
    N2["ContentView"]
    N3["ItemListModel"]
    N4["SwiftUI / Charts APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

WatchTaskListSample/WatchTaskListSampleApp.swift:10 — architecture anchor

@main
struct WatchTaskListSampleApp: 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 watchOS-Apps.

Ownership and state

classDiagram
    WatchTaskListSampleApp *-- ItemListModel : itemListModel
    Color_AppColors *-- Color : appYellow
    Color_AppColors *-- Color : appCoolGray
    Color_AppColors *-- Color : appDarkGray

Ownership evidence

WatchTaskListSample/WatchTaskListSampleApp.swift:13 — stored dependency or nearest verified ownership anchor

@main
struct WatchTaskListSampleApp: App {
    // ...
    @StateObject var itemListModel = ItemListModel()
    // ...
}

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

WatchTaskListSample/WatchTaskListSampleApp.swift:11 — representative type boundary

struct WatchTaskListSampleApp: App {
    // ...
}

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

Access control

Reference code

WatchTaskListSample/Models/DateFormatStyle.swift:16 — representative boundary

struct DateFormatStyle: FormatStyle {
    // ...
    private var dateFormatTemplate: String
    // ...
}

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: WatchTaskListSampleApp; Controller: ComplicationController; Model: ItemListModel; View: ContentView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: getComplicationDescriptors, handleSharedComplicationDescriptors, getTimelineEndDate, getPrivacyBehavior, getCurrentTimelineEntry, getTimelineEntries, getLocalizableSampleTemplate, createData.
• Files: WatchTaskListSample/WatchTaskListSampleApp.swift, WatchTaskListSample/Models/ItemListModel.swift, WatchTaskListSample/Views/ContentView.swift, WatchTaskListSample/ComplicationController.swift, WatchTaskListSample/Models/ChartData.swift, WatchTaskListSample/Models/DateFormatStyle.swift.

Architecture takeaways

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