Blog
Notes on how Kyndium is made and why: engineering, design and the thinking behind the product.
Inside Timeline Studio's scene compiler
How a table of rows becomes a slide with real PowerPoint shapes, and why the renderer never touches React.
Why Kyndium keeps one record per task
Most tools that offer a board and a timeline keep two copies and sync them. Kyndium keeps one row and treats every view as a lens. Here is what that costs and what it buys.
Importing from Trello, Asana and Jira without losing the plan
What each export format contains, what Kyndium does with it, and the three rules that keep an import from leaving a mess.
Live updates that never move the floor
How Kyndium shows a teammate's change within seconds in every view, and why it deliberately waits while you are dragging, typing or reading a menu.
Why Slack posts come from the database
Kyndium's Slack notifications are sent by Postgres triggers, not by the app. Here is why that is the only way to cover every path, and what it took to make it safe.
How Workload counts a week
The small decisions behind the Workload grid: which week a task belongs to, how points spread across days, and why over-capacity is a color and not an alarm.
Undo instead of "Are you sure?"
Why Kyndium removed every confirmation dialog for deletes, what replaced them, and the one place that still asks.
One hue, two modes
How Kyndium's color system generates every neutral from a single hue in OKLCH, keeps text readable in light and dark, and why the nav band is the same color in both.