![evernote calendar connector evernote calendar connector](https://www.appsandreports.com/uploads/meistertask-screen-1.png)
You can smell some of the symptoms of this in constraints around organisers and attendees present in all calendar apps. Traditional calendar APIs are based around client-server interaction, that client being the single source of truth and the event representation being a collapsed form of a far richer object graph. The Cronofy API is deliberately not just a protocol conversion layer on top of the existing calendar APIs. Linking Evernote to a calendar represents some difficult synchronisation challenges that are present when you start to connect many classes of applications.
![evernote calendar connector evernote calendar connector](https://polezniesoveti.com/wp-content/uploads/2015/09/Razreshit-dostup-k-evernote.jpg)
Solving synchronization problems not just doing CRUD
Evernote calendar connector how to#
My hope is that understanding how we built this app will give you a better understanding of some of the considerations and challenges you may face when you’re deciding whether and how to integrate your application or service into your users’ calendars. That said the source code, in Ruby, is available on Github. This post is deliberately technical but, generally code agnostic, in an effort to explain some of the concepts behind the approach taken. If the professional then changes that event, either by moving it or adding additional information your booking service is notified and can reschedule or undertake whatever workflow is appropriate. So if your app is an online booking service, the setting of a reminder is analogous to a booking being made and the event is created in the calendar of the professional servicing the appointment. What’s more you can then edit the reminder and note information in either Evernote or your calendar and the two stay in sync. Our Evernote Calendar Connector creates a calendar event whenever a reminder is set on a note. You can then have a conversation about the similarities and differences rather than abstract concepts. APIs can be difficult services to explain, especially to non-technical users, so it generally helps to have a tangible use case for people to explore as a starting point.