I'm building a family calendar app (Expo SDK 56 + Supabase). I already have two-way Google Calendar sync running server-side: OAuth, a calendar the app creates in the user's account, push notifications plus an incremental sync token, and an outbox for writes going out.
Now I need two-way sync with Apple Calendar. A read-only .ics subscription doesn't work for me, because users need to edit on either side. I see two options:
A: iCloud CalDAV from my server
The user creates an app-specific password at appleid.apple.com and pastes it into the app.
The server creates its own calendar (MKCALENDAR) and syncs with sync-collection, using the same outbox/worker I already have for Google.
✅ Works on every platform, including web, and keeps syncing when the app is closed.
❌ The setup is clunky for non-technical parents.
❌ An app-specific password unlocks the whole iCloud account (mail, contacts, every calendar), so I'd be storing a much broader credential than I need.
❌ iCloud doesn't push changes, so I'd have to poll.
❓ Apple doesn't officially support this.
B: EventKit on the device (expo-calendar)
The phone reads and writes its local calendars (iCloud, Exchange, and on Android whatever is in CalendarContract).
✅ No credentials, the OS permission prompt handles access, and it covers every account on the phone.
❌ Syncs only while the app runs (background fetch on iOS is unreliable).
❌ One user with two devices means two writers.
❌ Needs a native build, and does nothing on web.
Questions for anyone who has shipped one of these:
Is anyone running iCloud CalDAV with app-specific passwords in production? How do users take the setup, and has Apple ever pushed back or broken it?
If you went with EventKit, how did you handle background sync and conflicts across several devices?
Is there a third option I'm missing, or a hybrid (for example EventKit on iOS, server sync everywhere else)?
0
0
80