Soft-launching Synara, because it's time to move on from ICS files

Any time I’ve built something involving events, the same problem shows up immediately. The moment you try to send invites or keep them updated across Gmail, Outlook and Apple, everything becomes unpredictable. ICS files are old, fragile and interpreted differently by every provider. You fix one issue, and another appears somewhere completely unrelated.

Going through the provider APIs isn’t much better. Each one has its own event model, its own authentication rules and its own idea of how updates and RSVPs should behave. You end up building three separate integrations just to achieve basic consistency, and even then, you get edge cases that make no sense.

So I started by working on a new event format called ACE. The whole point is to replace ICS completely. It’s structured, modern, consistent and designed specifically for the problems developers hit today. And Synara is the first implementation of it. Instead of dealing with ICS quirks or three incompatible APIs, you send one ACE event and Synara handles the invites, updates and RSVPs in a predictable way.

Synara: https://synara.events/
The ACE Project: https://aceproject.dev/

I’m soft-launching it now because I want to hear from people who’ve dealt with the same headaches. If you’ve run into strange calendar behaviour, update failures or anything else that made you question your own code, those stories help shape what ACE and Synara need to cover by default.

If you have a minute to look at the site and tell me what’s confusing, missing or just not convincing enough, that feedback would be hugely useful right now.

Happy to talk about any part of it!