Hello fellow Hackers - longtime lurker, first time poster here. My name Is Dan and I wanted to share a project I have been working on for over a year - Time Trigger (https://timetrigger.dev). Time Trigger is a system that allows developers to have JSON data sent to an endpoint at a specific time in the future.
There are lots of cron services out there, but here is what’s different:
This service was originally built for another project I am working on and I decided to just spin it off as a separate product all together - This is the first side project I have ever actually launched and I would love your feedback on it!
Thanks!
I think a lot of devs who are working on their own app backends and need this feature might prefer to implement this functionality themselves.
Whether or not they are making the right call, I think you'll be up against this. You can either sell your way through it, or reposition this for a different audience who wouldn't have these objections.
Perhaps there are some use-cases for No-Coders you can satisfy. Is there anything like this already that can trigger Zapier?
Hi @mattgillooly, thank you for the great feedback. I love getting constructive criticism and you're absolutely right many devs would probably want to implement this themselves. I did obviously, and it was such a pain to build a reliable distributed system to do this I figured it was worth putting it out there.
The problem with other solutions is that they are all cron-based e.g. recurring - even on Zapier. Doing this kind of thing on a non-repeating schedule did not seem to exist (not that I could find anyway!).
Cheers,
Dan
Great, so if you integrated with Zapier, you'd be providing something unique to No-Coders that they can't get any other way.
Hey Dan! Congrats on the launch! Here are a few thoughts I had while glancing at your site:
Hope this was helpful and keep up the great work!
Andy
Hi Andy,
Thanks for the detailed feedback, this is very valuable to me. I'll take this into consideration as I update the marketing homepage this week - and I'll fix the CSS bug ;-)
Cheers,
Dan