This is a problem with all of these tasks having similar, overlapping use cases and similar, overlapping technology implementations. There are also remarkably f

This is a problem with all of these tasks having similar, overlapping use cases and similar, overlapping technology implementations. There are also remarkably few standards for the things around calendars, so most clients kludge something up with structured data sent over e-mail. Which leads to every implementation having its own, non-compatible spec. Even something as simple as forwarding calendar invites can have dramatically different functionality between two systems. I was at a company that ran split-brain between Google and Lotus Notes and it was an absolute nightmare that effectively broke calendaring for 2 years because you could only forward events one way, and acceptances wouldn’t flow back up the chain because some of the clients used a different mechanism for signaling acceptance. This has all been a problem for decades. The business world solved this by just forming a consensus on Outlook / Exchange in the mid-2000s; if you use any other combination you have to accept that there will be dropped communications with those who use the standard stack.