Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
dpearson2699 avatar

Alarmkit

  • 2.6k installs
  • 944 repo stars
  • Updated July 15, 2026
  • dpearson2699/swift-ios-skills

alarmkit is an iOS skill for AlarmKit alarms and timers with system Live Activity UI on Lock Screen and Dynamic Island.

About

The alarmkit skill implements AlarmKit alarms and countdown timers for iOS and iPadOS 26 plus with system-managed Live Activities on Lock Screen, Dynamic Island, and Apple Watch. Setup requires NSAlarmKitUsageDescription, requestAuthorization via AlarmManager.shared, AlarmPresentation for alert countdown and paused states, AlarmAttributes with optional metadata and tint color, and AlarmConfiguration for alarm or timer modes. Alarms use Alarm.Schedule fixed or relative times with weekly repeats; timers use duration-based firing with always-on countdown UI. State lifecycle covers scheduled, countdown, paused, and alerting with alarmUpdates async observation and cancel, pause, resume, stop, and countdown actions. AlarmButton configures stop and snooze actions; secondaryButtonBehavior chooses countdown snooze versus custom intents. CountdownDuration sets preAlert and postAlert phases for visible countdown and snooze repeats. Alarms override Focus and Silent mode automatically. Widget extensions support non-alerting Live Activity UI during countdown phases. Common mistakes and a review checklist address authorization failures and missing plist keys.

  • Requires NSAlarmKitUsageDescription and explicit authorization before scheduling.
  • Alarms use fixed or relative schedules; timers fire after a duration.
  • System renders templated Live Activities via AlarmPresentation states.
  • States include scheduled, countdown, paused, and alerting with alarmUpdates.
  • Alarms override Focus and Silent mode on iOS 26 plus and iPadOS 26 plus.

Alarmkit by the numbers

  • 2,582 all-time installs (skills.sh)
  • +109 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #79 of 1,039 Mobile Development skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
At a glance

alarmkit capabilities & compatibility

Capabilities
alarm and timer scheduling with alarmconfigurati · authorization and alarmupdates state observation · alarmpresentation alert, countdown, and paused u · snooze and stop intents with alarmbutton configu · widget extension guidance for countdown live act
Use cases
frontend · ui design
Platforms
macOS
From the docs

What alarmkit says it does

AlarmKit requires iOS 26+ / iPadOS 26+. Alarms override Focus and Silent mode automatically.
SKILL.md
Without it, alarms silently fail to schedule.
SKILL.md
npx skills add https://github.com/dpearson2699/swift-ios-skills --skill alarmkit

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.6k
repo stars944
Security audit3 / 3 scanners passed
Last updatedJuly 15, 2026
Repositorydpearson2699/swift-ios-skills

How do I schedule wake-up alarms or countdown timers with Apple's system alarm UI on iOS?

Schedule AlarmKit alarms and countdown timers with Lock Screen, Dynamic Island, and Apple Watch system UI on iOS 26 plus.

Who is it for?

iOS 26 plus apps needing prominent alarms, snooze, or workout-style countdown timers.

Skip if: Skip for local notifications only or Android alarm implementations without AlarmKit.

When should I use this skill?

User mentions AlarmKit, AlarmManager, countdown timers, or Dynamic Island alarm UI.

What you get

Authorized AlarmManager schedules with AlarmPresentation, intents, and observable alarm state transitions.

  • AlarmKit scheduling code
  • AlarmPresentation configuration
  • Live Activity integration

By the numbers

  • Requires iOS 26+ and iPadOS 26+ for AlarmKit support

Files

SKILL.mdMarkdownGitHub ↗

AlarmKit

Schedule prominent alarms and countdown timers that surface on the Lock Screen, Dynamic Island, and Apple Watch. AlarmKit requires iOS 26+ / iPadOS 26+. Alarms override Focus and Silent mode automatically.

AlarmKit builds on Live Activities -- every alarm creates a system-managed Live Activity with templated UI. You configure the presentation via AlarmAttributes and AlarmPresentation rather than building custom widget views.

See references/alarmkit-patterns.md for complete code patterns including authorization, scheduling, countdown timers, snooze handling, and widget setup.

import AlarmKit

Contents

Workflow

1. Create a new alarm or timer

1. Add NSAlarmKitUsageDescription to Info.plist with a user-facing string. 2. Request authorization with AlarmManager.shared.requestAuthorization(). 3. Configure AlarmPresentation (alert, countdown, paused states). 4. Create AlarmAttributes with the presentation, optional metadata, and tint color. 5. Build an AlarmManager.AlarmConfiguration (.alarm or .timer). 6. Schedule with AlarmManager.shared.schedule(id:configuration:). 7. Observe state changes via alarmManager.alarmUpdates. 8. If using countdown, add a widget extension target for non-alerting Live Activity UI.

2. Review existing alarm code

Run through the Review Checklist at the end of this document.

Authorization

AlarmKit requires explicit user authorization. Without it, alarms silently fail to schedule. Request early (e.g., at onboarding) or let AlarmKit prompt automatically on first schedule.

let manager = AlarmManager.shared

// Request authorization explicitly
let state = try await manager.requestAuthorization()
guard state == .authorized else { return }

// Check current state synchronously
let current = manager.authorizationState // .authorized, .denied, .notDetermined

// Observe authorization changes
for await state in manager.authorizationUpdates {
    switch state {
    case .authorized: print("Alarms enabled")
    case .denied:     print("Alarms disabled")
    case .notDetermined: break
    @unknown default: break
    }
}

Alarm vs Timer Decision

FeatureAlarm (.alarm)Timer (.timer)
Fires atSpecific time (schedule)After duration elapses
Countdown UIOptionalAlways shown
RecurringYes (weekly days)No
Use caseWake-up, scheduled remindersCooking, workout intervals

Use .alarm(schedule:...) when firing at a clock time. Use .timer(duration:...) when firing after a duration from now.

Scheduling Alarms

Alarm.Schedule

Alarms use Alarm.Schedule to define when they fire.

// Fixed: fire at an exact Date (one-time only)
let fixed: Alarm.Schedule = .fixed(myDate)

// Relative one-time: fire at 7:30 AM in device time zone, no repeat
let oneTime: Alarm.Schedule = .relative(.init(
    time: .init(hour: 7, minute: 30),
    repeats: .never
))

// Recurring: fire at 6:00 AM on weekdays
let weekday: Alarm.Schedule = .relative(.init(
    time: .init(hour: 6, minute: 0),
    repeats: .weekly([.monday, .tuesday, .wednesday, .thursday, .friday])
))

Schedule and Configure

let id = UUID()

let configuration = AlarmManager.AlarmConfiguration.alarm(
    schedule: .relative(.init(
        time: .init(hour: 7, minute: 0),
        repeats: .never
    )),
    attributes: attributes,
    stopIntent: StopAlarmIntent(alarmID: id.uuidString),
    secondaryIntent: SnoozeIntent(alarmID: id.uuidString),
    sound: .default
)

let alarm = try await AlarmManager.shared.schedule(
    id: id,
    configuration: configuration
)

Alarm State Transitions

cancel(id:)
    |
scheduled --> countdown --> alerting
    |             |             |
    |         pause(id:)    stop(id:) / countdown(id:)
    |             |
    |         paused ----> countdown (via resume(id:))
    |
cancel(id:) removes from system entirely
  • cancel(id:) -- remove the alarm completely (any state)
  • pause(id:) -- pause a counting-down alarm
  • resume(id:) -- resume a paused alarm
  • stop(id:) -- stop an alerting alarm
  • countdown(id:) -- restart countdown from alerting state (snooze)

Countdown Timers

Timers fire after a duration and always show a countdown UI. Use Alarm.CountdownDuration to control pre-alert and post-alert durations.

// Simple timer: 5-minute countdown, no snooze
let timerConfig = AlarmManager.AlarmConfiguration.timer(
    duration: 300,
    attributes: attributes,
    stopIntent: StopTimerIntent(timerID: id.uuidString),
    sound: .default
)

let alarm = try await AlarmManager.shared.schedule(
    id: UUID(),
    configuration: timerConfig
)

CountdownDuration

Alarm.CountdownDuration controls the visible countdown phases:

  • preAlert -- seconds to count down before the alarm fires (the main countdown)
  • postAlert -- seconds for a repeat/snooze countdown after the alarm fires
let countdown = Alarm.CountdownDuration(
    preAlert: 600,   // 10-minute countdown before alert
    postAlert: 300   // 5-minute snooze countdown if user taps Repeat
)

let config = AlarmManager.AlarmConfiguration(
    countdownDuration: countdown,
    schedule: .relative(.init(
        time: .init(hour: 8, minute: 0),
        repeats: .never
    )),
    attributes: attributes,
    stopIntent: stopIntent,
    secondaryIntent: snoozeIntent,
    sound: .default
)

Alarm States

Each Alarm has a state property reflecting its current lifecycle position.

StateMeaning
.scheduledWaiting to fire (alarm mode) or waiting to start countdown
.countdownActively counting down (timer or pre-alert phase)
.pausedCountdown paused by user or app
.alertingAlarm is firing -- sound playing, UI prominent

Observing State Changes

let manager = AlarmManager.shared

// Get all current alarms
let alarms = manager.alarms

// Observe changes as an async sequence
for await updatedAlarms in manager.alarmUpdates {
    for alarm in updatedAlarms {
        switch alarm.state {
        case .scheduled:  print("\(alarm.id) waiting")
        case .countdown:  print("\(alarm.id) counting down")
        case .paused:     print("\(alarm.id) paused")
        case .alerting:   print("\(alarm.id) alerting!")
        @unknown default: break
        }
    }
}

An alarm that disappears from alarmUpdates has been cancelled or fully stopped and is no longer tracked by the system.

AlarmAttributes and AlarmPresentation

AlarmAttributes conforms to ActivityAttributes and defines the static data for the alarm's Live Activity. It is generic over a Metadata type conforming to AlarmMetadata.

AlarmPresentation

Defines the UI content for each alarm state. The system renders a templated Live Activity using this data -- you do not build custom SwiftUI views for the alarm itself.

// Alert state (required) -- shown when alarm is firing
let alert = AlarmPresentation.Alert(
    title: "Wake Up",
    secondaryButton: AlarmButton(
        text: "Snooze",
        textColor: .white,
        systemImageName: "bell.slash"
    ),
    secondaryButtonBehavior: .countdown  // snooze restarts countdown
)

// Countdown state (optional) -- shown during pre-alert countdown
let countdown = AlarmPresentation.Countdown(
    title: "Morning Alarm",
    pauseButton: AlarmButton(
        text: "Pause",
        textColor: .orange,
        systemImageName: "pause.fill"
    )
)

// Paused state (optional) -- shown when countdown is paused
let paused = AlarmPresentation.Paused(
    title: "Paused",
    resumeButton: AlarmButton(
        text: "Resume",
        textColor: .green,
        systemImageName: "play.fill"
    )
)

let presentation = AlarmPresentation(
    alert: alert,
    countdown: countdown,
    paused: paused
)

AlarmAttributes

struct CookingMetadata: AlarmMetadata {
    var recipeName: String
    var stepNumber: Int
}

let attributes = AlarmAttributes(
    presentation: presentation,
    metadata: CookingMetadata(recipeName: "Pasta", stepNumber: 3),
    tintColor: .blue
)

AlarmPresentationState

AlarmPresentationState is the system-managed ContentState of the alarm Live Activity. It contains the alarm ID and a Mode enum:

  • .alert(Alert) -- alarm is firing, includes the scheduled time
  • .countdown(Countdown) -- actively counting down, includes fire date and durations
  • .paused(Paused) -- countdown paused, includes elapsed and total durations

The widget extension reads AlarmPresentationState.mode to decide which UI to render in the Dynamic Island and Lock Screen for non-alerting states.

AlarmButton

AlarmButton defines the appearance of action buttons in the alarm UI.

let stopButton = AlarmButton(
    text: "Stop",
    textColor: .red,
    systemImageName: "stop.fill"
)

let snoozeButton = AlarmButton(
    text: "Snooze",
    textColor: .white,
    systemImageName: "bell.slash"
)

Secondary Button Behavior

The secondary button on the alert UI has two behaviors:

BehaviorEffect
.countdownRestarts a countdown using postAlert duration (snooze)
.customTriggers the secondaryIntent (e.g., open app)

Live Activity Integration

AlarmKit alarms automatically appear as Live Activities on the Lock Screen and Dynamic Island on iPhone, and in the Smart Stack on Apple Watch. The system manages the alerting UI. For countdown and paused states, add a widget extension that reads AlarmAttributes and AlarmPresentationState.

A widget extension is required if your alarm uses countdown presentation. Without it, the system may dismiss alarms unexpectedly.

struct AlarmWidgetBundle: WidgetBundle {
    var body: some Widget {
        AlarmActivityWidget()
    }
}

struct AlarmActivityWidget: Widget {
    var body: some WidgetConfiguration {
        ActivityConfiguration(for: AlarmAttributes<CookingMetadata>.self) { context in
            // Lock Screen presentation for countdown/paused states
            AlarmLockScreenView(context: context)
        } dynamicIsland: { context in
            DynamicIsland {
                DynamicIslandExpandedRegion(.center) {
                    Text(context.attributes.presentation.alert.title)
                }
                DynamicIslandExpandedRegion(.bottom) {
                    // Show countdown or paused info based on mode
                    AlarmExpandedView(state: context.state)
                }
            } compactLeading: {
                Image(systemName: "alarm.fill")
            } compactTrailing: {
                AlarmCompactTrailing(state: context.state)
            } minimal: {
                Image(systemName: "alarm.fill")
            }
        }
    }
}

Common Mistakes

DON'T: Forget NSAlarmKitUsageDescription in Info.plist. DO: Add a descriptive usage string. Without it, AlarmKit cannot schedule alarms at all.

DON'T: Skip authorization and assume alarms will schedule. DO: Call requestAuthorization() early and handle .denied gracefully.

DON'T: Use .timer when you need a recurring schedule. DO: Use .alarm with .weekly([...]) for recurring alarms. Timers are one-shot.

DON'T: Omit the widget extension when using countdown presentation. DO: Add a widget extension target. AlarmKit requires it for countdown/paused Live Activity UI. Why: Without a widget extension, the system may dismiss alarms before they alert.

DON'T: Ignore alarmUpdates and track alarm state manually. DO: Observe alarmManager.alarmUpdates to stay synchronized with the system. Why: Alarm state can change while your app is backgrounded.

DON'T: Forget to provide a stopIntent -- it cannot be nil in practice. DO: Always provide a LiveActivityIntent for stop so the button performs cleanup.

DON'T: Store large data in AlarmMetadata. It is serialized with the Live Activity. DO: Keep metadata lightweight. Store large data in your app and reference by ID.

DON'T: Use deprecated stopButton parameter on AlarmPresentation.Alert. DO: Use the current init(title:secondaryButton:secondaryButtonBehavior:) initializer.

Review Checklist

  • [ ] NSAlarmKitUsageDescription present in Info.plist with non-empty string
  • [ ] Authorization requested and .denied state handled in UI
  • [ ] AlarmPresentation covers all relevant states (alert, countdown, paused)
  • [ ] Widget extension target added if countdown presentation is used
  • [ ] AlarmAttributes metadata type conforms to AlarmMetadata
  • [ ] Alarm ID stored for later cancel/pause/resume/stop operations
  • [ ] alarmUpdates async sequence observed to track state changes
  • [ ] stopIntent and secondaryIntent are valid LiveActivityIntent implementations
  • [ ] postAlert duration set on CountdownDuration if snooze (.countdown behavior) is used
  • [ ] Tint color set on AlarmAttributes to differentiate from other apps
  • [ ] Error handling for AlarmManager.AlarmError.maximumLimitReached
  • [ ] Tested on device (alarm sound/vibration differs from Simulator)

References

  • Patterns and code: references/alarmkit-patterns.md
  • Apple docs: AlarmKit |

AlarmManager | AlarmAttributes | Scheduling an alarm

Related skills

How it compares

Choose alarmkit over generic local-notification skills when the product needs Apple's first-party alarm surfaces on Lock Screen, Dynamic Island, and Apple Watch.

FAQ

Why do alarms fail to schedule silently?

Missing authorization or NSAlarmKitUsageDescription prevents AlarmManager from scheduling alarms.

When should I use alarm versus timer mode?

Use alarm for clock-time or recurring schedules; use timer when firing after a duration with countdown UI.

Do I build custom SwiftUI alarm views?

No. Configure AlarmPresentation and AlarmAttributes; the system renders templated Live Activities.

Is Alarmkit safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.