ChronoTrigger is a clock-based scheduler that runs inside your Rails app. Use it to run code (events) at specific times and intervals.
Nobody wants to be the first person to arrive at a club, and yet, this is exactly what most app onboarding processes feel like.
A typical visitor will spend 7-12 seconds evaluating your hard work before deciding if they will engage. You must convey that exciting things are happening, or they will close the tab and forget you exist.
ChronoTrigger is a tool designed to breathe life into otherwise static user interfaces and onboarding experiences.
It allows you to subtly expose users to a crafted narrative that nudges them forward, without feeling like a canned theme park ride. The story is advanced by their actions and their engagement is rewarded with simulated interaction, even if they are user number one.
If you spend months building something cool, and then hustle to get people to check it out, you get exactly one chance to make your first and only impression. It's up to you to do everything you can to make sure that your app is special enough to love. To succeed long-term, you need these first users to become cheerleaders and evangelize to their friends.
If you think about the stand-out onboarding success stories like Slack, they all prioritize anticipating what the user will be thinking, feeling and wondering during each moment of the first minutes the user spends on the site.
ChronoTrigger is for developers who are proud of what they have created; tech founders looking for a way to give new users an aspirational story to tell themselves. This converging path leads to feelings of ownership and drives conversion without a hard sell.
You will use ChronoTrigger to orchestrate the onboarding experience your app deserves:
ActiveJob is amazing, but creating Jobs for typical ChronoTrigger use cases feels like taking a taxi to the next house.
Jobs are not designed to run immediately, and priority should be given to important things like mail delivery. There's also functionality in the Event class that would be hard to retrofit to Job classes.
It's also worth mentioning that requiring Sidekiq would require Heroku users to set up a worker dyno, even if you're not using ActiveJob. Finally, Sidekiq sometimes runs jobs multiple times!
ChronoTrigger runs on real world time, like trains. Every second, on the second, ChronoTrigger decides whether there are new events to run. If so, there's a thread-safe and highly-optimized pool of workers waiting.
{% hint style="info" %}
Other event scheduling libraries tend to be either cron wrappers or use timing offsets (think: sleep 1) from whenever they are called and don't factor in their own timing footprint. In other words, 1000 loops later, more than 1000 seconds have passed. No good!
{% endhint %}
You start the ChronoTrigger Clock after your web server, and it runs inside your Rails app process.
ChronoTrigger Events live in app/events and follow a structure that will be familiar to ActiveJob users.
You can schedule Events from anywhere in your application that it makes sense to do so, such as:
FAQs
Unknown package
We found that chrono_trigger demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.
Security News
AGENTS.md is a fast-growing open format giving AI coding agents a shared, predictable way to understand project setup, style, and workflows.
Security News
/Research
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.
