Scheduling an alarm with AlarmKit

At a glance

Project structure

Source bundle/
└── AlarmKit-ScheduleAndAlert/
    ├── AlarmKit-ScheduleAndAlert/
    │   ├── AlarmKitScheduleAndAlertApp.swift
    │   ├── ContentView.swift
    │   ├── AppIntents.swift
    │   ├── ViewModel.swift
    │   ├── AlarmForm.swift
    │   ├── AlarmMetadata.swift
    │   └── Info.plist
    ├── AlarmLiveActivity/
    │   ├── AlarmLiveActivityBundle.swift
    │   ├── AlarmLiveActivity.swift
    │   └── Info.plist
    └── AlarmKit-ScheduleAndAlert.xcodeproj/
        ├── .xcodesamplecode.plist
        └── project.pbxproj

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 21 source declaration(s).

Overall architecture

flowchart LR
    N1["AlarmKitScheduleAndAlertApp"]
    N2["ContentView"]
    N3["ViewModel"]
    N4["AlarmKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

AlarmKit-ScheduleAndAlert/AlarmKit-ScheduleAndAlert/AlarmKitScheduleAndAlertApp.swift:10 — architecture anchor

@main
struct AlarmKitScheduleAndAlertApp: 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 AlarmKit.

Ownership and state

classDiagram
    ContentView *-- ViewModel : viewModel
    AlarmCell o-- Alarm : alarm
    AlarmCell o-- LocalizedStringResource : label
    AlarmAddView *-- AlarmForm : userInput

Ownership evidence

AlarmKit-ScheduleAndAlert/AlarmKit-ScheduleAndAlert/ContentView.swift:12 — stored dependency or nearest verified ownership anchor

    @State private var viewModel = ViewModel()

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

AlarmKit-ScheduleAndAlert/AlarmKit-ScheduleAndAlert/AlarmKitScheduleAndAlertApp.swift:11 — representative type boundary

struct AlarmKitScheduleAndAlertApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

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

Access control

Reference code

AlarmKit-ScheduleAndAlert/AlarmKit-ScheduleAndAlert/ContentView.swift:12 — representative boundary

    @State private var viewModel = ViewModel()

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: AlarmKitScheduleAndAlertApp; View: AlarmAddView, AlarmProgressView, ButtonView, ContentView, TimePickerView; ViewModel: ViewModel.
• Protocols: no local protocol declaration in the scanned source.
• Methods: alarmList, pickerRow, perform, fetchAlarms, scheduleAlarm, scheduleAlertOnlyExample, scheduleCountdownAlertExample, scheduleCustomButtonAlertExample.
• Files: AlarmKit-ScheduleAndAlert/AlarmKit-ScheduleAndAlert/AlarmKitScheduleAndAlertApp.swift, AlarmKit-ScheduleAndAlert/AlarmKit-ScheduleAndAlert/ContentView.swift, AlarmKit-ScheduleAndAlert/AlarmLiveActivity/AlarmLiveActivityBundle.swift, AlarmKit-ScheduleAndAlert/AlarmKit-ScheduleAndAlert/ViewModel.swift, AlarmKit-ScheduleAndAlert/AlarmKit-ScheduleAndAlert/AlarmForm.swift, AlarmKit-ScheduleAndAlert/AlarmLiveActivity/AlarmLiveActivity.swift.

Architecture takeaways

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