Tracking heart rate zones for workouts

At a glance

Project structure

Source bundle/
├── HKWorkoutZoneSample Watch App/
│   ├── HKWorkoutZoneSampleApp.swift
│   ├── MetricsView.swift
│   ├── ControlsView.swift
│   ├── SessionView.swift
│   └── StartView.swift
├── HKWorkoutZoneSampleApp/
│   ├── HKWorkoutZoneSampleApp.swift
│   └── MetricsView.swift
└── Shared/
    ├── Views/
    │   ├── SummaryView.swift
    │   ├── ElapsedTimeView.swift
    │   └── HeartRateZoneView.swift
    ├── WorkoutManager.swift
    └── NavigationModel.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 5 project/configuration file(s) and 30 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["HKWorkoutZoneSample Watch App"]
    V2["HKWorkoutZoneSampleApp"]
    Boundary["HealthKit APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

HKWorkoutZoneSample Watch App/HKWorkoutZoneSampleApp.swift:10 — architecture anchor

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

Interpretation

The branches represent separate entry-bearing project variants in the downloaded bundle, not runtime calls between those variants. Each branch is intentionally collapsed at the documented framework boundary; the detailed target-local flow remains in the cited files. Ownership is claimed only where the next section cites a stored property or assignment.

Ownership and state

classDiagram
    ZoneDetailView *-- String : title
    ZoneDetailView o-- ZoneDisplayData : zones
    SummaryMetricRow *-- String : title
    SummaryMetricRow *-- String : value

Ownership evidence

Shared/Views/SummaryView.swift:123 — stored dependency or nearest verified ownership anchor

private struct ZoneDetailView: View {
    let title: String
    // ...
}

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

HKWorkoutZoneSample Watch App/HKWorkoutZoneSampleApp.swift:11 — representative type boundary

struct HKWorkoutZoneSampleWatchApp: App {
    // ...
}

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

Access control

Reference code

HKWorkoutZoneSample Watch App/HKWorkoutZoneSampleApp.swift:12 — representative boundary

@main
struct HKWorkoutZoneSampleWatchApp: App {
    @State private var workoutManager = WorkoutManager.shared
    // ...
}

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: HKWorkoutZoneSampleApp, HKWorkoutZoneSampleWatchApp; Manager: CountDownManager, WorkoutManager; Model: MetricsModel, NavigationModel; View: ContentView, ControlsView, CountDownView, ElapsedTimeView, HeartRateZoneView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: zoneColor, formatZoneDuration, prepareWorkout, requestAuthorization, startWorkout, pause, resume, togglePause.
• Files: HKWorkoutZoneSampleApp/HKWorkoutZoneSampleApp.swift, Shared/Views/SummaryView.swift, Shared/WorkoutManager.swift, HKWorkoutZoneSample Watch App/MetricsView.swift, HKWorkoutZoneSampleApp/MetricsView.swift, Shared/NavigationModel.swift.

Architecture takeaways

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

Source map

• Official Apple documentation