I scheduled a client event a full day wrong
Last Tuesday night, I was confirming a demo time with a client in San Francisco from Hangzhou. I had picked the same date, but the time zones were off. After sending the meeting link, the client noticed it was 12 hours early. I panicked too: the client wasn't difficult to work with—the tool had made something as simple as “time” unreliable. I've also been stuck in that loop, filling in every field and still leaving a client waiting unnecessarily.
Jiff is a date-time library for developers
Jiff 1.0 is a date-time library in the Rust ecosystem. It helps developers handle date arithmetic, time-zone conversion, daylight saving time, and time formats. Its users aren't everyday office workers; they're the people building scheduling into their products. My friend Lin Zhe, an indie developer, was debugging his own booking tool in Hangzhou last November. He was about to put Beijing and London clients on the same schedule, so he used Jiff to let the program apply the time-zone rules and reduce manual-conversion errors. It suits teams with development needs, not people who just want a drag-and-drop calendar.
The cost of recreating it today
First, money: the open-source version usually has no software fee, but I can't call integration with an existing product free. Labor costs depend on the project's complexity. On time, a developer familiar with Rust can get basic date calculations running in roughly half a day; connecting it to bookings, billing, or calendar sync usually takes 1–3 days. The technical barrier is knowing a little programming and identifying the cities, time zones, and daylight saving rules in your business. The first step isn't installing complicated software. It's opening the project docs, creating a test file, and writing runnable code that converts “3 p.m. Beijing time” to London time. If you don't understand code at all, that step may be a dealbreaker. There's no pressure to try it now.
Choose by your stage—don't copy this blindly
If you're just starting: I'd use the calendar's built-in time-zone conversion and always include the city when arranging times. I wouldn't develop a custom tool for one small feature yet.
If you already have 1–2 clients: I'd make a manual checklist for the most common cross-time-zone bookings, then ask a developer whether integrating Jiff is worthwhile. At this stage, mistakes are starting to hit the client experience directly.
If you're scaling up: I'd have the engineering side use Jiff to standardize scheduling, logs, and billing times, then add daylight saving time tests. The larger the operation, the more manual conversion looks like hidden operational debt.
Simply put, Jiff solves “getting the program's time math right,” not “organizing all your work.” If you don't have development needs right now, a mature calendar tool is perfectly fine.