Would you want to, then, completely disable the ‘auto export to a specific calendar’ feature? and only export specific events to specific calendars? Because I can’t envision satisfying your request while maintaining an ‘auto export’ function.
Would you want it to be ‘opt-in, per event’, always? In which the flow looks like “if you want to export an event, you would tap on it, tap export, and select the calendar to which it will export’?
Truthfully, this is quite a tricky request to consider implementing. What’s your use case?
Svend Korsgaard
•
Apr 11
Flow would look like this:
-In the Auto-export option: When setting up auto-export, you can choose to include several calenders, to be able to export to. You must chose one of them to be the “Default” calander option.
-With Auto-export enabled: every event exports to the default calendar upon creation.
-Events: Its possible to tap an event, the event has an “exports to” option. With the default calander always appearing by default. You can tap the “exports to” option, and the list of calanders you had chosen during the setup appears. You can then choose to change which specific calender that specific event exports to. (And possibly, maybe even export the same event to multiple different calanders from the list?)
Thats all: easy to use. Simple to setup, and is a minimal addition.
Luke M
Team•
Apr 11
Thanks for clarifying Svend, I really appreciate you taking the time to share these details.
The user experience as you’ve described sounds simple and straightforward, which is great. Under the hood though, it’s a bigger shift than it might seem at a glance, since the app currently assumes a single global calendar. Your idea involves changing how events sync, how they’re stored, managing individual overrides, handling data migration, and catching edge cases like moved or deleted appointments.
I like the idea and I’m happy to explore it, but please understand it might take some time to flesh this out safely. AI will probably be able to help, but I’d have to do a significant amount of testing to all the existing flows before rolling this out. Calendar Sync is absolutely one of the most complex things in the app, with tens of thousands of lines of code.
I appreciate your patience in the meantime, thank you!
Log in to comment and vote
Comments3
Luke M
Mar 30
Thanks for the feedback Svend.
This sounds quite complex; some questions:
Would you want to, then, completely disable the ‘auto export to a specific calendar’ feature? and only export specific events to specific calendars? Because I can’t envision satisfying your request while maintaining an ‘auto export’ function.
Would you want it to be ‘opt-in, per event’, always? In which the flow looks like “if you want to export an event, you would tap on it, tap export, and select the calendar to which it will export’?
Truthfully, this is quite a tricky request to consider implementing. What’s your use case?
Svend Korsgaard
Apr 11
Flow would look like this:
-In the Auto-export option: When setting up auto-export, you can choose to include several calenders, to be able to export to. You must chose one of them to be the “Default” calander option.
-With Auto-export enabled: every event exports to the default calendar upon creation.
-Events: Its possible to tap an event, the event has an “exports to” option. With the default calander always appearing by default. You can tap the “exports to” option, and the list of calanders you had chosen during the setup appears. You can then choose to change which specific calender that specific event exports to. (And possibly, maybe even export the same event to multiple different calanders from the list?)
Thats all: easy to use. Simple to setup, and is a minimal addition.
Luke M
Apr 11
Thanks for clarifying Svend, I really appreciate you taking the time to share these details.
The user experience as you’ve described sounds simple and straightforward, which is great. Under the hood though, it’s a bigger shift than it might seem at a glance, since the app currently assumes a single global calendar. Your idea involves changing how events sync, how they’re stored, managing individual overrides, handling data migration, and catching edge cases like moved or deleted appointments.
I like the idea and I’m happy to explore it, but please understand it might take some time to flesh this out safely. AI will probably be able to help, but I’d have to do a significant amount of testing to all the existing flows before rolling this out. Calendar Sync is absolutely one of the most complex things in the app, with tens of thousands of lines of code.
I appreciate your patience in the meantime, thank you!