There are millions of iPhone users out there.
Allowing them to connect their Apple Calendar to your application creates a better user experience and puts you one step ahead of your competition.
However, it's not easy.
The only way to connect to iCloud is using CalDAV. This client/server document protocol is used to submit and retrieve Apple Calendar documents.
Unfortunately, CalDAV can be a challenge for developers used to more commonly styled HTTP APIs.
This mean that many applications that could benefit from calendar sync don’t take advantage of it and their users miss out.
Using Cronofy's unified calendar API, you can solve these problems and more.
Sync between different calendar services
With traditional calendar integration, two versions of an event exist in two different calendar services.
Both can be updated independently, meaning that if an event is cancelled or rescheduled, one party may miss out on important details.
To avoid conflict deadlocks and infinite update loops, you’re responsible for handling ownership and state transitions.
The Cronofy API resolves these synchronization challenges.
Changes to calendar events are idempotent. You don't have to worry about if an event already exists or not, you just tell us what state you want to it be in and we'll make the necessary changes.
Cronofy also differentiates between events sourced from your application (‘Managed’) and events already in the user’s calendars (‘Unmanaged’) to ensure that you have reliable integration from the start.