4 comments
Why didn't you use something like Acuity? Serious questions because I'm building on their API right now (<a href="https://developers.acuityscheduling.com/" rel="nofollow">https://developers.acuityscheduling.com/</a>).
Cool! Who is this for? Can you share some potential use cases? Do you have a clear understanding of your target audience? Or is this more of a “build it and they will come” approach?
Great questions. It's targeted at dev teams wanting to build their own custom experiences on the frontend without having to deal with the complications of a scheduling backend. This could be anything from calendar functionality in their application to a platform that handles bookings for an office, etc.
While assisting several startups get their product built, we ran into a need for something like this which drove us to build this as a standalone service.
Figured others might find it useful as well!
What’s the value prop of this over cal.com scheduling backend with higher primitives?
Good question. Currently the value here is cost vs api usage compared to something like cal.com. Similar usage there would be significantly higher. That said, they also have some additional features that we don't have yet. We are actively working towards new features to close the gap! Thanks for checking it out.
Date math as a service!