What is the state of EventKit going forward?

I'm building an app that heavily relies on EKEventStore for calendar and reminder integration. The API is simple - and limited.

Change notifications amount to "something changed, you'd better refetch everything you care about." There's no way to know whether the calendar was updated while your app was closed or backgrounded. EKEvents and EKReminders don't trigger SwiftUI view updates, so you end up shunting them into your own observable state and keeping the two in sync.

My app is fairly complex rendering-wise, and I lament being locked into treating EKEventStore as a first-class citizen of my view and data layer. It makes everything clunkier, essentially shuts the door on modern features like undo/redo, and makes integrating with other calendar providers that much harder.

I'm exploring a custom SwiftData DataStore ↔ EKEventStore sync engine, but this is no easy task. There are still many unknowns I'd need to spike out before I can even attempt a proper implementation.

Still, I'm curious - is this something being actively worked on behind the scenes? Will we see a more modern, observable, SwiftUI-native EventKit integration in the future?

Hello @endgamer, cool username! 😎👾

Is there more information you can share here about the goal you are trying to accomplish? The more information the better, and that goes for code snippets and sample projects as well.

Someone here might have an answer for you.

And if not, I encourage you to file an enhancement request with information on how this design decision impacts you, and what you would like to see differently.

Feature enhancements can be submitted with Feedback Assistant. There, you can track if a fix has been found or not.

These forums are for code-level support but I'll do what I can to help!

 Travis Trotto - DTS Engineer

What is the state of EventKit going forward?
 
 
Q