Skip to main content
Technology & EngineeringiOS Swift28 lines

EventKit Calendars and Reminders

Integrate Apple EventKit for calendar event creation, calendar reading or reminders using the least supported access and predictable denial, editing and refresh behavior.

Quick Summary8 lines
Start by deciding which operation the user asked for. Presenting Apple's event editor for a user-managed addition, silently saving an event, reading existing calendars, and writing reminders have different permissions and interaction. Check the target OS and SDK and use the EventKit or EventKitUI path appropriate to that operation.

## Key Points

- [Apple EventKit event store access](https://developer.apple.com/documentation/eventkit/accessing-the-event-store.md)
- [Apple EventKit event and reminder creation](https://developer.apple.com/documentation/eventkit/creating-events-and-reminders.md)
skilldb get ios-swift-skills/eventkitFull skill: 28 lines
Paste into your CLAUDE.md or agent config

EventKit Calendars and Reminders

Start by deciding which operation the user asked for. Presenting Apple's event editor for a user-managed addition, silently saving an event, reading existing calendars, and writing reminders have different permissions and interaction. Check the target OS and SDK and use the EventKit or EventKitUI path appropriate to that operation.

Ask for the minimum capability

On supported systems, use the system event editor when the user can own review and saving. For a programmatic new event without reading calendars, use write-only calendar access where available. A write-only app cannot use the returned virtual calendar as proof that the user's real calendars were enumerated. Request full event access only when reading or editing existing calendar data is required. Reminders use their own entity access and capability checks.

Add the appropriate usage descriptions for the selected API and OS versions. If supporting older OS versions, use the documented availability branch rather than assuming new authorization methods and statuses exist. Request access at the moment the user initiates the feature and distinguish not determined, denied, restricted and granted states. Handle revocation while the app is suspended. If access is denied, explain the feature limitation and allow a manual workflow where possible.

Preserve event identity and local time

Use a bounded date predicate for reads and keep results tied to the event store and current permissions. Refresh displayed data when the store changes instead of retaining stale objects indefinitely. A recurring occurrence and an entire series require different save/remove spans. Ask which scope is intended before an irreversible edit. Use calendar date semantics for all-day events and verify times across daylight-saving transitions and locales. Do not create duplicate entries after an uncertain save by blindly retrying.

Verify with an authorized test calendar or reminders list. Exercise a new event, user cancellation in the editor, deny or revoke access, repeated launch, and a recurring item that must change only one occurrence. If the app supports reminders, separately exercise task due dates and permission. Compare app state with the observed calendar/list outcome. Keep real titles, invitees and identifiers out of evidence, and distinguish simulator observations from actual device/calendar synchronization.

References and rights

Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.

Install this skill directly: skilldb add ios-swift-skills

Get CLI access →