Skip months of integration hell. Use our SDK or open source scheduling package to handle everything calendar, simplify OAuth, build robust booking systems, integrate Google, Outlook, and other calendars with one unified API... 51M+ events created.
Replies
Best
we're using Recal in our Product (>1.5M ARR) and integration been smooth af -- the only scheduling API that price-wise scaled 4 our use-case too; big fan here! LFG!
Congrats! Why did you decide not to include any built-in UI components or templates for calendar interfaces, and do you see that causing challenges or friction for teams that want to move quickly?
@vouchy Thanks! We did not included UI components for now because we saw that most of our users often have very different views on how scheduling looks for them and most likely have their own designs or use components like this from shadcn and customize it to their needs. Regarding teams that want to move quickly, I think Recal is the perfect solution because our focus has always been to enable and minimize what needs to be handled and implemented. A great example of this in long term relations is that we simply don't vendor lock you, allowing you to move quickly in any direction you want.
nice nice nice! I used APIs like this before, and defo there is a big area to improve. which ICPs and marketers are you prioritizing first? there are tons of verticals i can think of!
Replies
we're using Recal in our Product (>1.5M ARR) and integration been smooth af -- the only scheduling API that price-wise scaled 4 our use-case too; big fan here! LFG!
Recal.dev
@niklas_von_haxthausen 🚀🫶
Super exciting!! Congrats @torben_koehler!! 😍
Recal.dev
Thank you @david_pflugpeil1! 🔥
wow, that looks promising.
Recal.dev
Thanks @crovs! 🚀
Superchat
Congrats! Super cool 🚀
Recal.dev
@alexanderfarr Thanks! 🚀
Ordinary People Prompts
Recal.dev
@wherelambo Love to hear that! 🫶
More of this! Indie pilots
Recal.dev
@maximilian_arnold ^^, lfg!
Finally a non .exe solution!
Exactly what I needed! Will try it out
Recal.dev
@jan_hecker Let's build something scheduling! 🧑💻
Congrats! Why did you decide not to include any built-in UI components or templates for calendar interfaces, and do you see that causing challenges or friction for teams that want to move quickly?
Recal.dev
@vouchy Thanks! We did not included UI components for now because we saw that most of our users often have very different views on how scheduling looks for them and most likely have their own designs or use components like this from shadcn and customize it to their needs. Regarding teams that want to move quickly, I think Recal is the perfect solution because our focus has always been to enable and minimize what needs to be handled and implemented. A great example of this in long term relations is that we simply don't vendor lock you, allowing you to move quickly in any direction you want.
Recal.dev
@vouchy for an overview of our quick implementation you can also view our docs here
SMASHSEND
nice nice nice! I used APIs like this before, and defo there is a big area to improve. which ICPs and marketers are you prioritizing first? there are tons of verticals i can think of!