Ember
This day planner app treats schedules as dynamic instead of fixed: when a task is moved or its duration changes, everything after it shifts later and flows around fixed items like meetings, avoiding manual replanning. It is currently web + Capacitor and is being rebuilt as a native Kotlin app, with full-duplex voice models being explored so tasks can be added or moved by conversing with an agent.
What it addresses
Most planners treat your schedule as fixed, so the moment a meeting runs long or a task takes twice as long, the plan is wrong and you either fix it by hand or give up on it.
Shared over time
Each entry reflects what was shared on that date. Details may have changed since then.
Ember
This day planner app treats schedules as dynamic instead of fixed: when a task is moved or its duration changes, everything after it shifts later and flows around fixed items like meetings, avoiding manual replanning. It is currently web + Capacitor and is being rebuilt as a native Kotlin app, with full-duplex voice models being explored so tasks can be added or moved by conversing with an agent.
Problem: Most planners treat your schedule as fixed, so the moment a meeting runs long or a task takes twice as long, the plan is wrong and you either fix it by hand or give up on it.
Posted by @hhhkm · Original comment ↗
“For the past two years I've been working on my day planner app Ember. Most planners treat your schedule as fixed, so the moment a meeting runs long or a task takes twice as long, the plan is wrong and you either fix it by hand or give up on it. In Ember, if you move a task or change how long it takes, everything after it shifts later, and it flows around fixed things like meetings.”