Hi PH! I'm Danil, Payments Engineering leader by day, solo builder by night
by•
I’m building Kale Your Day solo - an auto-scheduler that turns your tasks and calendar into a realistic plan and shows you when it breaks within a 30-day horizon.
By day I’m an engineering leader with ~20 years in software, most of it in payments and billing. Building has always been the part I love most - and Kale is where I get to do it end to end, from the first idea to the first user.
Looking forward to being part of this community!
25 views
Replies
Welcome Danil! Showing when the plan breaks is the part I like most, most planners only show the happy version. One question from someone who schedules a much smaller thing: my app sends occasion reminders at 10:00 in the user's local time, and separately I have seen how little a phone's own clock can be trusted: one support case was an iPhone whose clock was 9 hours ahead. With a 30 day horizon and real calendars, how do you handle time zone changes, a trip or a calendar event created in another zone? That feels like where a realistic plan quietly drifts.
@gbasovv Thanks George! Great question 🙂
In Kale, schedules aren't tied to a time zone. If you work 9-5 in PST and fly to Europe for a business trip, your schedule there is still 9-5, just local time.
The planner itself does use your time zone every time it runs (on any change, plus an hourly refresh). Kale is a web app, not a mobile app (yet), so there are two ways to keep the zone right:
You set it yourself in settings.
Kale reads your browser's time zone and warns you if it doesn't match your setting. It never switches without asking.
Time zones are always one of the trickiest parts, though. The daylight saving rule changes of the last few years showed that even big enterprises get them wrong 😅
@danil_razzhivin That is a clean answer, a schedule that means "9 to 5 wherever I am" is what people actually want. Warning instead of switching is the same instinct I ended up with for my app's daily bonus: the zone is held, and a new one is only accepted once the last claim is a full day old. Silent switching is where the surprises live. And yes, daylight saving changes are the reminder that time zone rules are data, not constants. Good luck with Kale!
@gbasovv Love the "full day since the last claim" rule, that's a neat way to make a zone change a non-event 🙂 Thanks George, and good luck with your app too!
Welcome, Danil! Showing where the plan breaks within 30 days is the part I'd actually use. I was a Fantastical user and ended up building my own calendar because I wasn't happy with it. For a calendar, being easy to read matters more to me than any feature. How do you show a break without making the whole week look red?
@hisashispace Thanks! Good question, and honestly that’s the exact thing I didn’t want to happen.
The way I see it, your day/week/month isn’t broken. Some specific tasks are, usually because of meetings, other priorities, or just not enough hours. So instead of painting the calendar red, Kale flags only those tasks, in two buckets:
Overdue: the deadline already passed and the task isn’t done
At risk: the deadline is still ahead, but in the current 30-day plan the task lands after it
The calendar stays clean, and you get a small banner like “2 overdue · 3 at risk”. The week itself doesn’t need your attention, just those few tasks do.
Then it’s your call what to do about it. You can extend working hours, bump the task’s priority (or lower another one), move the deadline, or start it outside your planned schedule. The goal is to let the plan match your real life.
And it keeps replanning as things change. If you finish a 4h task in 1h, the whole 30 days gets reshuffled, and a task that was at risk might fit fine now.
Curious how you handled this in your own calendar?